Recommended
More Related Content
What's hot
What's hot (20)
Similar to Fundamental test process
Similar to Fundamental test process (19)
Recently uploaded
Recently uploaded (20)
Fundamental test process
- 1. FUNDAMENTAL TEST PROCESS by Graham et.al (2011) Yoga Pratama Putra Department of Information System Faculty of Science and Technology State Islamic University of Sultan Syarif Kasim Riau
- 2. INTRODUCTION In this section, we will describe the fundamental test process and activities. These start with test planning and continue through to test closure. For each part of the test process, we'll discuss the main tasks of each test activity. You'll also encounter the glossary terms confirmation testing, exit criteria, incident, regression testing, test basis, test condition, test coverage, test data, test execution, test log, test plan, test strategy, test summary report and testware.
- 3. NEXT.. We can divide the activities within the fundamental test process into the following basic steps: Test planning and control; Test analysis and design; Test implementation and execution; Test evaluating exit criteria and reporting; Test closure activities.
- 4. TEST PLANNIG & CONTROL 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. To help us we may have organization or program test policies and a test strategy.
- 5. NEXT.. Test planning has the follow major tasks, given approxi- mately in order, which help us build a test plan : 1. Determine the scope and risks and identify the objectives of testing 2. Determine the test approach (techniques, test items, coverage, identifying and interfacing with the teams involved in testing, testware) 3. Implement the test policy and/or the test strategy 4. Determine the required test resources (e.g. people, test environment, PCs) 5. Schedule test analysis and design tasks, test implementation, execution and evaluation 6. Determine the exit criteria
- 6. NEXT.. Test control has the following major tasks : 1. Measure and analyze the results of reviews and testing. 2. Monitor and document progress, test coverage and exit criteria. 3. Provide information actions. 4. Make decisions.
- 7. TEST ANALYSIS & DESIGN 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 their behavior and structure. Design the test. Evaluate testability of the requirements and system.
- 8. TEST IMPLEMENTATIO N & EXECUTION 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 means 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. We also need to set up an envi-ronment where we will run the tests and build our test data. Setting up environ- ments and data often involves significant time and effort, so you should plan and monitor this work carefully.
- 9. NEXT.. Test implementation and execution have the following major tasks, in approximately the following order : 1. implementation : Develop and prioritize our test cases. Create test suites from the test cases for efficient test execution. Implement and verify the environment. 2. 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.
- 10. TEST EVALUATING EXIT CRITERIA & REPORTING 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'. These criteria vary for each project and are known as exit criteria.
- 11. NEXT.. 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. Write a test summary report for stakeholders: It is not enough that the testers know the outcome of the test. All the stakeholders need to know what testing has been done and the outcome of the testing, in order to make informed decisions about the software.
- 12. TEST CLOSURE ACTIVITIES 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.