Step 3 - Execute Tests

Inputs for this process:

• Approved test documents (Test Plan, Cases, Procedures)

• Automated testware, if applicable and developed scripts (Test Tools)

• Changes to the design (Change Requests)

• Test data

• Availability of the test and project teams (Project Staff, Test Team)

• General and Detailed Design Documents (Requirements, Software Design)

• A complete development environment that has been migrated to the test environment (Unit Tested Code) via the Configuration/Build Manager

• Test Readiness Document

• Update documents.

Outputs for this process:

• Changes to the code (Test Fixes)

• Test document problems uncovered as a result of testing (Test Document Problems)

• Problems with the design fed back to the developers and clients (Requirements, Design, Code Issues)

• Formal record of test incidents (Problem Tracking - PT)

• Baselined package ready for migration to the next level (Tested Source and Object Code)

• Log and summary of the test results (Test Report)

• Approved and signed-off revised testing deliverables (Updated Deliverables)

Process:

• Checkpoint meetings will be held throughout the Execution phase. The Checkpoint meeting will be held daily (if required) to address and discuss testing issues, status, and activities.

• Execution of tests is completed by following the test documents in a methodical manner. As each package of test procedures is performed, an entry is recorded in a test execution log to note the execution of the procedure and whether the test procedures uncovered any defects. The

output from the execution of test procedures is referred to as test results.

• Test results will be evaluated by the appropriate project members, applicable to the level of test, to determine whether the expected results were obtained. All discrepancy/anomalies will be logged and discussed with the Software Development Manager/Programmer and documented for

further investigation and resolution. Each client may have a different process for logging and reporting bugs/defects uncovered during testing, verify the process through the Configuration Management (CM) group. Pass/Fail criteria will be used to determine the severity of the problem.

Results will be recorded in a test summary report.

• The severity of a problem found during system testing will be defined in accordance to the customer’s risk assessment and recorded in their selected tracking tool. (Point is a Quality Channel Partner with Mercury Interactive. Mercury offers a test tool for each level of testing).

• Proposed fixes will be delivered to the testing environment based on the severity of the problem. Fixes will be regression tested and flawless fixes will be migrated to the new baseline. Following completion of the test, members of the Test Team will prepare a summary report. The summary

report will be reviewed by the Project Manager, Clients, Software Quality Assurance (SQA) and/or Test Team Lead.

• After a particular level of testing has been certified, it will be the responsibility of Configuration Manager to coordinate the migration of the release software components to the next test level as documented in the Configuration Management Plan. The software will only be migrated to the

production environment after the client has formally accepted it.

• The Test Team will review test document problems identified during the testing and update documents where appropriate. Some problems may be the result of inconsistencies or modifications between the Technical and Functional

Дата добавления: 2015-08-27