3 ms·
How is this your biggest problem? Emailing an annotated screenshot or attaching to a JIRA seems better because it's more consistent and blends with other proce
by metadat 4y ago
How is this your biggest problem?
Emailing an annotated screenshot or attaching to a JIRA seems better because it's more consistent and blends with other processes. What should happen when webpages content changes or goes defunct? Now you're also creating an archive.org... and on and on.
Don't get stuck and sink your time into a local maxima.
Maybe you'll find a market [of fools] willing to invest time into this exact locally optimal solution, but I predict it will be disappointingly small. The problem it solves isn't broadly substantial enough to warrant a specialized solution.
Only one way to know for sure, though ;)
- solardev 4y agoActually, this an ecosystem of visual bug reporting tools that already exists and it's very useful when your other testers/stakeholders are time constrained. These days people talk about user experience, well, this is the equivalent of that for tester experience. It makes it a lot easier to submit useful big reports. When you mandate jira (which is slow even on its fastest day) you then a big report from a 2 second click in an on page tool to like a 10 minute process, filling out all the fields, cropping the screenshot, copying over the url and console log and any network errors and all that. It takes forever and people eventually just learn to slack you a sentence instead, or just don't even report things anymore because it's such a hassle. Jira is the absolute worst tool for user facing interactions. It's designed for management, not devs, testers, or users. There are much better tools to make your life easier if you fall into the latter groups.