First, I absolutely LOVE that we can test Fin before implementing changes in Production. This feature has been incredibly valuable and has made us much more confident in the quality of what we're deploying.
One enhancement that would make the testing workflow even better would be the ability to lock completed test results.
We've gone from training one or two people to training multiple support teams across two products. As a multi-brand company, we frequently update audiences and rerun answers during testing. The challenge is that if a batch has already been graded and comments have been added, rerunning the answers wipes out all of that work.
A simple Lock/Unlock option for completed batches would help preserve grading and comments while still allowing teams to intentionally unlock a batch if they need to rerun or regrade it. I think this would be especially valuable for organizations that have multiple teams collaborating on testing.
I also wanted to mention what appears to be a performance issue with the testing workspace.
Even when working by myself, I noticed the server struggling to keep up after uploading eight batches. Yesterday, we had six team members testing simultaneously, and the grading functionality stopped working altogether—we could no longer mark responses as Good, Acceptable, or Poor, nor could we add comments. By this morning, everything was working normally again.
For now, I'm planning to have our team stagger their testing sessions, but it may be worth investigating whether there are concurrency or capacity limitations in the testing environment. As more customers begin using the testing feature with larger teams, I could see this becoming a common challenge.
Overall, we're really excited about this feature. These are just a couple of improvements that I think would make an already great testing experience even better.