• Scenario 1
• Scenario 2
• Scenario 3     
  
• Scenario 4
• Scenario 5
• Scenario 6

Scenario 3: New project, new hope for test coverage

Your situation

Your success in spotting several potentially costly faults in the last software release before it got shipped to clients was noticed, so you have been given the chance to develop all your tests ahead of the next software release.

Solution

Such an offer is great! However, if you want to prepare automated test scripts in advance then you might already have hit another problem: Most automated test tools rely on the concept of record-playback, which means that you would usually need a version of the software to be available before you can start.

You have no such problem with SVaT because you can adapt the structure of the GUI elements very easily, and therefore be sure that your test scripts will be relevant whatever R&D eventually throw at you.

The steps you take, using SVaT, are outlined here:
Expand all, Collapse All

1. Preparation: Install SVaT
   
   Run the provided SVaT installer and make a few decisions about where to install SVaT.
   
   You need at least the Personal Edition for this.
   
   If you have not already installed Java you must install it before you can install SVaT. Java is included with SvaT, or you can use an existing installation if appropriate.
   
   Time: 5 minutes.
   
   
2. Template Creation: Create temporary GUI structure (more...less...)
   
   The next step is to create a set of templates. Each template describes a temporary GUI structure which reflects the way you

   think

    the AUT will be structured. At this point you may be able to get some pointers from R&D, but otherwise you will have to make your best guess (familiar territory for most QC people!).
   
   Time: 1-3 hours
   
   
   The next step is to create a set of templates. Each template describes a temporary GUI structure which reflects the way you

   think

    the AUT will be structured. At this point you may be able to get some pointers from R&D, but otherwise you will have to make your best guess (familiar territory for most QC people!).
   
   At this moment in time you will only have to make sure that you are giving each GUI element the right type. A GUI element's name and position in a template can always, and easily, be adapted to whatever R&D will give you in the test candidate (see also Scenario 2).
   
   Time: 1-3 hours
   
   
3. Test Creation: Create the test scripts
   
   You can now start defining the expected behaviours of the AUT in the same way as you would have done if the AUT had been available. Later SVaT will automatically translate these behaviours into an optimised set of test scripts that you can execute against the AUT.
   
   Time: at least 15 minutes
   
   
4. Await AUT: Wait for the test candidate to be available
   Once you have specified your test scripts you will have to wait until R&D gives you your first test candidate. When you receive it, you should proceed as described in Scenario 2 to adapt the test scripts and execute them.
   
   Time: 1-3 hours
   
   
5. Outcomes
   
   The benefits of this approach include:
   
   

   • You can use the time between the test phases efficiently to prepare new test scripts.
   • You do not have to rely on the availability of a test candidate to develop your test scripts.
   • Updating the test scripts when a test candidate becomes available is easy (and done in hours not days).
   • Your test scripts are automated, freeing your time to develop further test scripts.