Software QA/Testing/Tester FAQs: Execute Tests? Test Strategy?

Software QA/Testing

Glossary and Technical FAQs

Q: How do you execute tests? (Cont'd...)

Outputs for this process:

Log and summary of the test results. Usually this is part of the Test Report. This needs to be approved and signed-off with revised testing deliverables.
Changes to the code, also known as test fixes.
Test document problems uncovered as a result of testing. Examples are Requirements document and Design Document problems.
Reports on software design issues, given to software developers for correction. Examples are bug reports on code issues.
Formal record of test incidents, usually part of problem tracking.
Base-lined package, also known as tested source and object code, ready for migration to the next level.

Q: How do you create a test strategy?

A: The test strategy is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment.

[Continued on next page...]

Click on a link!