I'm curious about how different teams approach Quality Assurance before launching a product. Do you utilize specific tools, take screenshots, or create PDF documents? I've been developing a system that allows for pin-based comments directly on the live page, and I would love to hear how others are tackling this issue to inform my next steps.
1 Answer
One major improvement for our team was integrating QA thinking earlier in the development process. Every new feature has acceptance criteria, edge cases, and a quick manual test checklist before development even begins. This really helps prevent those "oops, we forgot this" moments later on. We also do a fast PR preview review before merging, where both the product and QA teams can click through the feature. As for tools, we use Notion and Linear for our QA checklists. I also tried Runable to generate test scenarios from feature descriptions, which helped us when specifications were a bit messy. It's not perfect, but saves time during setup.
How do you collect visual feedback at that stage? Do designers comment directly on the PR, or do you still rely on screenshots via Slack?