Basic process of creating test... • Offers technology that records
the Testers actions into a list while the tester “creates” a test
that will run autonomously later on… • Ability to easily craft
verifications against specific objects. • Offers a list of
“quick-step” options for verifications against commonly used tasks.
• Verifications are very smart and can be crafted against MANY
different objects with very specific types criteria to check
against. • Once tests have been “recorded” in Test Studio… just
press start to watch the test execute again in the browser...
quickly repeating all the steps the tester previously assigned. •
Can reorder steps easily. • Switching browsers to test is very
easy. Just select from a drop-down list. • SPECIAL FEATURE –
Storyboard View – captures screenshots of every step automatically
(can export these reports to pdf) • Ability to create multiple
projects • Ability to create multiple tests per project • Test
Maintenance is easy: Shared Element Repository • Easy to update
elements, ID’s, and element logic • Offers Breakpoint feature for
debugging test creation (Similar to Visual Studio) • Errors in
testing are recorded within the screenshots… visual representation
of these errors will allow testers to understand problems much
easier than just reading error reports from a list. • Viewing
failures is easy. Test Studio provides lots of metadata about each
failure. Suggestions are also provided (based on error reports) to
resolve failure issues. This feature is important because it is
nice to be able to tell the difference between a legitimate bug and
a tester crafted automation hiccup. • From this point- the click of
a button should allow a QA tester to send the report straight to
the development team.
