Here are the answers from Product Marketing Manager at Seapine Software to the queries on Defect Scribe posted by ToolsJournal.
ToolsJournal: Why do you think there is a need for a QA tool for Manual and Exploratory Testing to augment Seapine's QA Wizard Suite of tools for Automated, Load and Stress Testing?
Matt: Even in the best of cases, teams are rarely able to automate more than 30-40% of their testing effort. Manual testing still makes up the bulk of the testing effort, and it’s a time-intensive process. Meanwhile the lifespan of a product is shrinking fast (meaning more frequent releases), as are testing budgets. Testers are being pressed to continually improve their contributions to the product release cycle with fewer resources and in tighter time frames. To meet these demands, testers are looking for tools and methods that simplify their job and save them time. Defect Scribe does just that.
ToolsJournal: How important is Exploratory Testing in today’s world and how is Defect Scribe helpful in doing Exploratory Testing?
Matt: Exploratory testing is really the difference-maker when it comes to releasing a great product. Test automation (when done right) covers regression testing and manual test case execution is important in ensuring the application meets basic quality expectations. What’s missing is making sure the application usage experience is really top-notch, and that’s where exploratory testing can help. With exploratory testing you’re utilizing a tester or business analyst with knowledge of the application domain and product requirements to go out and really use the application to see what happens. It’s a really powerful way to engage your testers to utilize their skills and abilities to test the application outside of scripted use case scenarios.
ToolsJournal: How is Defect Scribe helpful in making Manual Testing more efficient and productive?
Matt: Defect Scribe takes care of the “housekeeping” for a manual or exploratory test session, and lets the tester focus on their primary job; looking for defects. While their testing, Defect Scribe is sitting in the background recording their actions and capturing application screens. When the tester runs into an issue, they simply stop the recording process and Defect Scribe presents them with a visual history of their test steps. They can add comments, clean up or annotate screenshots, and then with a click of the mouse send that defect report to a developer. With those detailed steps, the developer should have no problem reproducing the issue and making a fix. The tester saved time in not having to take manual notes on their test session, didn’t have to spend 20 minutes typing up a bug report, and didn't have to spend another 20 minutes helping the developer reproduce the issue. It’s a huge time saver for the tester, and also helped the developer to find and fix the issue much faster.
ToolsJournal: Which third party tools are supported by Defect Scribe in addition to Seapine’s Test Track Pro for defect tracking?
Matt: Defect Scribe comes with TestTrack Pro integration out of the box and has a built-in API that enables custom integrations with a variety of other tools. Moving forward, we’re looking to publish integrations with other well-known defect tracking and test tools.
ToolsJournal: Can the test steps recorded with Defect Scribe be converted into test scripts for performing automated testing of the same AUT with QA Wizard Pro?
Matt: Not currently with Defect Scribe, but we do have that capability built into TestTrack. I’m not sure what the plans are with that in Defect Scribe.
ToolsJournal: Thank You Matt for your time!
[Image Credits: Defect Scribe]