The Bug Catcher - Tips and Tricks from QA Experts

Tip #1: Using external help to tackle your test backlog.

Frequently the majority of testing for a piece of high-tech equipment must be done by someone with expert knowledge of the device under test (DUT). This may make it difficult to bring in consultants or other outside help in a testing pinch. However, one of the perfect candidates for consulting help is automating the testing backlog. Since these test cases are already documented, a consultant can help you get your test automation plans off the drawing board, allowing you to focus on testing the current release.

Tip #2: Saving time by automating testbed and DUT configuration.

It's not just the test cases that are repetitive and time consuming. Setting up the testbed — including configuring the device under test, getting test equipment into the correct starting state, and organizing supporting infrastructure in the testbed — all require significant time every time you run a test case. And if you make a mistake, you often have to start the whole thing from scratch. This type of tedious and error-prone task is a perfect candidate for automation. You can develop pre-defined configurations as a stand alone "module" that can be automatically run before a suite of test cases.

Trick #1: Cleaning up your edits and typos.

FanfareSVT will automatically capture the steps of your test case as you execute them in a command line or Web interface. Don't worry about "being perfect" at this point. Just test manually as you normally would. FanfareSVT cleans up your edits and typos as you go so you can focus on the flow of the test. Later, you can remove unnecessary commands, add new ones, or make any other changes.

At any time, you have the option to pause the FanfareSVT capture process by simply click Capture -> Pause. This enables you to perform offline steps that should not appear in the test, go consult with a coworker, or finish off your game of foosball. Any commands that you send while paused are not included in the captured data. When you are ready to continue capturing steps, just click Capture -> Resume and take up where you left off.

Trick #2: Making a developer's day — without any extra effort.

If you encounter a bug when running a FanfareSVT test, you can attach the Fanfare test and test results to the bug report that is sent to development. The results file will document the incorrect DUT response and the test will show the exact steps that the developer should use to reproduce the bug — all with no additional effort on your part.

Tips and Tricks from QA Experts

Fanfare is pleased to offer the latest "insider" product usage tips and techniques based on our most frequent customer requests. In this issue:

Tip #1: Using external help to tackle your test backlog.

Tip #2: Saving time by automating testbed and DUT configuration.

Trick #1: Cleaning up your edits and typos.

Trick #2: Making a developer's day — without any extra effort.