Certified Tester ISTQB Internationa Advanced Level Syllabus-Test Analyst Qualifications Board t might require tests to be run in a particular The y the de dosseciatedeoepetyesrcoik。aonentmeeetesmemeot may b and tests sh licable standards such as the United States As specified above,test data is needed for testing.and in some cases these sets of data can be quite large. During implementation.Test Analysts create input and environment data to load into databases Analysts also create data to be used with data-driven automation environment is essential.i.e.the test environment should be capable of enabling the exposure of the testing operate normally wh nen failur tos are not occurring.and on anticin cha siderations. ent changes do occur during execution.it is ipont tohemct of the changes to tests that have aread een run During test implementation,testers must ensure that those responsible for the creation and and that all the testware and test defect mana nt and test logai esneagetoesenadodese0nAhgitonntnag ify the procedures that gather data for exit criteria evaluation and test results reporting. hala du case,some percenitage of the test impemem wnicn does not follow Unscripted testing should not be ad hoc or aimless as this can be unpredictable in duration and age unese a ng testing.Test analysis.test design,and test implementation still occur.but they occur primarily during test execution. at finding defects, there are s me drawbacks. ragecan1ednet6akerepeaomyee These techni oility can be 1.7 Test Execution egeoeexeeeedandheenyaernaetetetgxactoma implementation,but the Test Analyst should have adequate time to ensure coverage of additional ors t that are(any falure detecte y to roduce the failure) This in aration of scrinted and uns nted testing techniques helps to guard against test escapes due to gaps in scripted coverage and to it the pe ae par Version 2012 Page 16 of 64 19 October 2012Certified Tester Advanced Level Syllabus - Test Analyst International Software Testing Qualifications Board Version 2012 Page 16 of 64 19 October 2012 © International Software Testing Qualifications Board tests are to be run, carefully checking for constraints that might require tests to be run in a particular order. Dependencies must be documented and checked. The level of detail and associated complexity for work done during test implementation may be influenced by the detail of the test cases and test conditions. In some cases regulatory rules apply, and tests should provide evidence of compliance to applicable standards such as the United States Federal Aviation Administration’s DO-178B/ED 12B [RTCA DO-178B/ED-12B]. As specified above, test data is needed for testing, and in some cases these sets of data can be quite large. During implementation, Test Analysts create input and environment data to load into databases and other such repositories. Test Analysts also create data to be used with data-driven automation tests as well as for manual testing. Test implementation is also concerned with the test environment(s). During this stage the environment(s) should be fully set up and verified prior to test execution. A "fit for purpose" test environment is essential, i.e., the test environment should be capable of enabling the exposure of the defects present during controlled testing, operate normally when failures are not occurring, and adequately replicate, if required, the production or end-user environment for higher levels of testing. Test environment changes may be necessary during test execution depending on unanticipated changes, test results or other considerations. If environment changes do occur during execution, it is important to assess the impact of the changes to tests that have already been run. During test implementation, testers must ensure that those responsible for the creation and maintenance of the test environment are known and available, and that all the testware and test support tools and associated processes are ready for use. This includes configuration management, defect management, and test logging and management. In addition, Test Analysts must verify the procedures that gather data for exit criteria evaluation and test results reporting. It is wise to use a balanced approach to test implementation as determined during test planning. For example, risk-based analytical test strategies are often blended with dynamic test strategies. In this case, some percentage of the test implementation effort is allocated to testing which does not follow predetermined scripts (unscripted). Unscripted testing should not be ad hoc or aimless as this can be unpredictable in duration and coverage unless time boxed and chartered. Over the years, testers have developed a variety of experience-based techniques, such as attacks, error guessing [Myers79], and exploratory testing. Test analysis, test design, and test implementation still occur, but they occur primarily during test execution. When following such dynamic test strategies, the results of each test influence the analysis, design, and implementation of the subsequent tests. While these strategies are lightweight and often effective at finding defects, there are some drawbacks. These techniques require expertise from the Test Analyst, duration can be difficult to predict, coverage can be difficult to track and repeatability can be lost without good documentation or tool support. 1.7 Test Execution Test execution begins once the test object is delivered and the entry criteria to test execution are satisfied (or waived). Tests should be executed according to the plan determined during test implementation, but the Test Analyst should have adequate time to ensure coverage of additional interesting test scenarios and behaviors that are observed during testing (any failure detected during such deviations should be described including the variations from the scripted test case that are necessary to reproduce the failure). This integration of scripted and unscripted (e.g., exploratory) testing techniques helps to guard against test escapes due to gaps in scripted coverage and to circumvent the pesticide paradox