The tests that you need to run at any given point in a development or maintenance cycle will depend on many factors - the development work that has been done, whether you are running an initial short series of tests to determine if a full regression test is justified, whether you are testing on a different platform and so on. These different test needs will mean that the same test procedures will be used in different combinations and perhaps run in slightly different ways. Test Lead supports this need, and automatically logs everything that you do during test execution, by using "Run Lists".
A Run List contains a list of procedures to be run and expands each procedure to show the individual Test Cases and test steps, and the expected result of each step. The Run List is basically a list of instructions displayed on the screen that defines what must be done and in what sequence. When you begin a test run, you click on a "Start Run" button on the run list. This creates a new test log and automatically records the date and time, the ID of the user who is performing the testing, and information about the Run List and the Transmittal Report that initiated the test need.
As each test step is completed, the completion state (passed, failed, suspended etc) is selected from a drop down list and once again the test log is automatically updated to log the test step end execution time and the test result. The next test step is started (and automatically logged) and testing continues in this way until all the tasks on the run list have been completed, or the test run is abandoned.
If a test step fails, the user is asked if an Incident (Error) Report is to be created. If the response is "Yes", then Test Lead begins the Incident Reporting process by requesting the user to provide a name (Reference) for the Incident, and then enter all the required details.
Back to Test Lead Index