For anyone who has ever manually tested a web application, you know how much of a pain it can be to retrace your exact steps to reproduce a tricky bug. But that’s no longer the case when combining LogDigger and Jira to do your testing.
For anyone who has ever manually tested a web application, you know how much of a pain it can be to retrace your exact steps to reproduce a tricky bug. But that’s no longer the case when combining LogDigger and Jira to do your testing.
- Tracking usage
- Filing bugs [in Jira]
- Capturing logs
LogDigger works like this..
Testing a web application
You (or your tester) add the plugin to your browser and a simple XML file to your web application (no code necessary). Then you enable and consent to tracking for the application or website you wish to test.
Then just start testing and LogDigger does the rest by tracing your steps for you.
Filing comprehensive bugs
This is the sexy bit… once you spot that tricky issue, just submit it via the browser plugin.
LogDigger automatically takes a screenshot of the page which you can crop and annotate.
For some Java, PHP and Python applications, LogDigger can even collect server logs for you.
Get back to it!
Using LogDigger with Jira lets you file bugs quickly and get back to more testing.. a tester’s dream!
Learn more
LogDigger offers a free 30 day eval and community licensing (like we do for Jira) with prices ranging from $320 to $1250. Definitely worth checking out!