Ease Into Test Automation With QA Wizard Pro + TestTrack

talks about QA Wizard Pro on April 20, 2012

Creating repeatable and tester-independent test cases is a challenge for every team. Making sure steps are accurate and descriptions are detailed enough for any tester that might run the test case are important in building a usable and effective test case. In many cases the tester knows exactly what needs to be done to test a specific piece of functionality, but translating that knowledge into text and screenshots is both challenging and tedious.

With the release of Seapine ALM 2012, the test case creation process became a whole lot easier! What we’ve done is united the screen recording capabilities of QA Wizard Pro with the test case management prowess of TestTrack.¬†Without even considering test automation, you can now create good test cases faster by combining QA Wizard Pro and TestTrack.

Here’s a quick example of a test case I created simply by clicking Record in the TestTrack test case list window. Notice that each step clearly outlines what action to take, and is accompanied by a screenshot that highlights exactly what should be done and what the tester should expect to see. To see the whole process in detail, watch the video on recording test cases from QA Wizard Pro.

New test case with steps and screenshots

Screenshot of application under test

With this set of well-defined steps and associated screenshots, you end up with a library of standardized test cases that can be run by anyone on the team. You eliminate ambiguity in the test case, and you greatly reduce the tedious parts of typing out and capturing screenshots that slow down even the best tester.

And, of course, there’s no requirement that you turn these test cases into automated tests. That can come later, as the team has bandwidth to spend time on automation. When that time does come though, you already have the test scripts so it’s just a matter of scheduling them into the existing test plan.

Have you used this new functionality? Leave a comment, and any improvements or suggestions you may have, to let us know how it’s working for your team.

Comments are closed.