Fundamental test process hazahara
- 2. The idea of a fundamental test process for all levels Of test has developed over the years. Whatever the level Of testing, we see the same type of main activities happening, although there may be a different amount of formality at the different levels, for example, component tests might be carried out less formally than system Tests in most organizations with a less documented test process.
- 3. During test planning, we make sure we Understand the goals and objectives of the customers, stakeholders, and the project, and the risks which testing is intended to address. This will give us what is sometimes called the mission of testing or the test assignment. Based on this understanding, we set the goals and objectives for the testing itself, and derive an approach and plan for the tests, including specification of test activities.
- 4. Test control has the following major tasks: Measure and analyze the results of reviews and testing. Monitor and document progress, test coverage and exit criteria. Provide information on testing. Initiate corrective actions. Make decisions
- 5. Test analysis and design has the following major tasks, in approximately the following order: Review the test basis (such as the product risk analysis, requirements, architecture, design specifications, and interfaces), examining the specifications for the software we are testing. Identify test conditions based on analysis of test items,their specifications, and what we know about theirbehavior and structure.
- 6. During test implementation and execution, we take The test conditions and make them into test cases and testware and set up the test environment. This mean that, having put together a high-level design for our tests, we now start to build them. We transform our test conditions into test cases and procedures, other Testware such as scripts for automation.
- 7. Test implementation and execution have the following majortasks, in approximately the following order: Implementation: Develop and prioritize our test cases Create test suites from the test cases for efficient test execution Implement and verify the environment. Execution: Execute the test suites and individual test cases, following our test proce dures. Log the outcome of test execution and record the identities and versions of the software under test, test tools and testware. Compare actual results (what happened when we ran the tests) with expected results (what we anticipated would happen). Where there are differences between actual and expected results, report discrepancies as incidents. Repeat test activities as a result of action taken for each discrepancy.
- 8. Evaluating exit criteria is the activity where Test execution is assessed against the defined objectives. This should be done for each test level, as for each we need to know whether we have Done enough testing. Based on our risk assess ment, we'll have set criteria against which we'll Measure enough'.
- 9. Evaluating exit criteria has the following major tasks: Check test logs against the exit criteria specified in test planning: We look to see what evidence we have for which tests have been executed and checked, and what defects have been raised, fixed, confirmation tested, or are out standing. Assess if more tests are needed or if the exit criteria specified should be changed: We may need to run more tests if we have not run all the tests we designed, or if we realize we have not reached the coverage we expected, or if the risks have increased for the project. We may need to change the exit criteria to lower them, if the business and project risks rise in impor tance and the product or technical risks drop in importance. Note that this is not easy to do and must be agreed with stakeholders. The test manage ment tools and test coverage tools that we'll discuss in Chapter 6 help us with this assessment.
- 10. Test closure activities include the following major tasks: Check which planned deliverables we actually delivered and ensure all incident reports have been resolved through defect repair or deferral. Finalize and archive testware, such as scripts, the test environment, and any other test infrastructure, for later reuse. Hand over testware to the maintenance organization who will support the software and make any bug fixes or maintenance changes, for use in con firmation testing and regression testing. Evaluate how the testing went and analyze lessons learned for future releases and projects.
- 11. Graham et.al. (2011). ISTQB-Fondation of Software Testing. London: Cengage Learning EMEA.