See how easy it is with this step by step process, without any need for script editing or complex coding.
Before you start with any automation creation, you need to decide what tests should form part of the pack.
What parts of the application are
a) critical to the business
b) most likely to be impacted by changes.
These are the scenarios you are looking to include.
You can now increase the scale of the tests by dragging in data sets to execute multiple scenarios. Remember when using TestDrive there is no need for any script editing.
You will also want to add in some validations/assertions.
Select which additional tests you would like e.g.spell checks, performance monitoring and highlighting of any application changes. Choose whether to apply to :
These will be crucial when you come to running the Test Pack and analysing the results.
Change in the application is inevitable and, from time-to-time, you may find it necessary to update a script. As TestDrive separates the data and validations from the scripts, this is a very simple process.
Scripts can be recreated from an execution result, they can be edited manually, or you can ask TestDrive to automatically incorporate changes into the script, using its Self-Healing mode.
Either way, updating a Test Pack to incorporate application change is a quick and easy process.
Marc Croquette, IT Director presents his approach and the ensuing benefits