Fundamental test process
•Download as PPTX, PDF•
0 likes•12 views
The document discusses the fundamental test process for software testing at different levels. It describes the main activities that occur during testing, including test planning and control, test analysis and design, test implementation and execution, evaluating exit criteria and reporting, and test closure activities. Test planning involves understanding requirements, risks, objectives, and deriving a test plan and approach. Test control involves measuring results, monitoring progress, and making decisions. Test analysis and design identifies test conditions and designs test cases. Test implementation and execution builds testware and sets up environments to run test cases. Evaluating exit criteria assesses when enough testing has been done. Test closure includes delivering results and archiving test materials.
Report
Share
Recommended for you
Recommended for you
More Related Content
What's hot
What's hot (20)
Similar to Fundamental test process
Similar to Fundamental test process (17)
Recently uploaded
Recently uploaded (20)
Fundamental test process
- 2. INTRODUCTION 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. The decision about the level of formality of the processes will depend on the system and software context and the level of risk associated with the software.
- 3. TEST PLANNING ANDCONTROL 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.
- 4. CONTINUE.. Test planning has the following major tasks, given approximately in order, which help us build a test plan: Determine the scope and risks and identify the objectives of testing. Determine the test approach (techniques, test items, coverage, identifying and interfacing with the teams involved in testing, testware) Implement the test policy and/or the test strategy Determine the required test resources (e.g. people, test environment, PCs) Schedule test analysis and design tasks, test implementation, execution and evaluation Determine the exit criteria
- 5. CONTINUE.. 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.
- 6. TESTANALYSIS ANDSYSTEM 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 tests Evaluate testability of the requirements and system.
- 7. TEST IMPLEMENTATIO NAND 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 ourtest data. Setting up environ- ments and data often involves significant time and effort, so you should plan and monitor this work carefully
- 8. EVALUATING EXITCRITERIA AND 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.
- 9. TESTCLOSURE 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 laterreuse. 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.
- 10. REFERENCE Graham et.al. (2011). ISTQB-Fondation of SoftwareTesting. London: Cengage LearningEMEA