Presentation on theme: "Performing Test Best Practices By Gabriel Rodriguez."— Presentation transcript:
Performing Test Best Practices By Gabriel Rodriguez
Copyright MSQAA Federation Chapter. Agenda Test Execution Recording Test Results Q&A Reference
Copyright MSQAA Federation Chapter. Test Execution
Copyright MSQAA Federation Chapter. Test Execution In a lifecycle approach to testing, test execution can occur throughout the project lifecycle from testing requirements through to conducting user acceptance testing. The more detailed the test plan, the easier this task becomes for the individuals responsible for executing the test. The roles and responsibilities for each single stage of testing should also have been documented in the test plan. Test team is responsible for system testing.
Copyright MSQAA Federation Chapter. Test Execution Executing the System Test Plan System test should begin as soon as the integration testing has been successfully completed. System test ends when the test team has measured system capabilities and correct the problems to have confidence that the system will operate successfully in production.
Copyright MSQAA Federation Chapter. Test Execution Executing the System Test Plan The major steps during System testing are: – Set up system environment. – Establish the test data bed. – Identify test cases that will be including in the system test. – Assign the test cases to test cycles. – Assign test scripts to testers for execution.
Copyright MSQAA Federation Chapter. Test Execution Executing the System Test Plan – Review test result and determine if the problems identified are actually defects. – Record defects in tracking system. – Re-test and validate the fix, once the defect is fixed and migrated to the test environment. Close the defect log if the defect is fixed.
Copyright MSQAA Federation Chapter. Recording Test Results
Copyright MSQAA Federation Chapter. Recording Test Results All Test executed should be logged on a Test Execution Log, or in a tool such as Mercurys Test Director. The Test Log is a simple worksheet (or spreadsheet) that records test activities in order to maintain control over the test. The Test Log includes: – Test ID – Test Activities – Who executed the test – Start and stop times – Pass or Fail criteria – Comments Make sure actual result are documented. Incidents are logged into the defect tracking system once a review determines it is actually a defect.
Copyright MSQAA Federation Chapter. Recording Test Results Recording Test Results caveats: – Not all the testing projects use a Test Execution Log, nevertheless the use of this Log has turned out to be an effective testing practice. – Some projects store their test execution results in the same test case documents. – The bottom line is that testers need to abide by the processes and standards established in the organization. – The next slides show one example of a Test Execution Log and a Test Case document storing the results of the test execution.
Copyright MSQAA Federation Chapter. Recording Test Results Test Execution Log Example
Copyright MSQAA Federation Chapter. Recording Test Results Test Case showing test results Example
Copyright MSQAA Federation Chapter. Q&A Any questions…
Copyright MSQAA Federation Chapter. Reference CSTE Study Guide 2002 by QAI CSTE Study Guide 2006 by QAI