Certified Tester ISTOB Advanced Level Syllabus-Test Analyst Qualifications Board ris.It is imp g。 indicate that additional testing effort is needed in that area. Requirements and risk covera a06 be used to prioritize remaining work and accurate.the ect can be controlled and accurate status information can be reported to the stakeholders. io to ensure 1.4 Test Analysis Analyze the test basis Identify the test conditions emrarteTesAnastopocaedeiecneywihtesanaystheoiowngsmiyoieashoda t nas passed revew win reaso as been updated as needed There is a reasonable budget and schedule available to accomplish the remaining testing work for this test object Test conditions are typically identified by analysis of the test basis and the test obiectives.In some situations,where doc umentation may be old or non-existent,the test conditions may be identified by h hedorthetestpan. the co are to the item being lested,there are som stadard .It is usually advisable to define test conditions at differing levels of detail.Initially.high-level alty of screen uch as "screen r eiects an account number that is one digit short of the comrect length Using this ty suf of hie to defining test conditions can help to esure the nigh each product risk must be identified and traced back to that risk item will be necessary to address the ne Tes areas of the test p hat specific tests must 1.5 Test Design Still adher etheieeeenmhetm3eeeniaankeelproeec8oesesaesteee a to the includes the following activities: Version 2012 Page 12 of 64 19 October 2012Certified Tester Advanced Level Syllabus - Test Analyst International Software Testing Qualifications Board Version 2012 Page 12 of 64 19 October 2012 © International Software Testing Qualifications Board that is achieved will roll up into the overall project metrics. It is important that the information entered into the various tracking tools be as accurate as possible so the metrics reflect reality. Accurate metrics allow managers to manage a project (monitor) and to initiate changes as needed (control). For example, a high number of defects being reported from one area of the software may indicate that additional testing effort is needed in that area. Requirements and risk coverage information (traceability) may be used to prioritize remaining work and to allocate resources. Root cause information is used to determine areas for process improvement. If the data that is recorded is accurate, the project can be controlled and accurate status information can be reported to the stakeholders. Future projects can be planned more effectively when the planning considers data gathered from past projects. There are myriad uses for accurate data. It is part of the Test Analyst’s job to ensure that the data is accurate, timely and objective. 1.4 Test Analysis During test planning, the scope of the testing project is defined. The Test Analyst uses this scope definition to: Analyze the test basis Identify the test conditions In order for the Test Analyst to proceed effectively with test analysis, the following entry criteria should be met: There is a document describing the test object that can serve as the test basis This document has passed review with reasonable results and has been updated as needed after the review There is a reasonable budget and schedule available to accomplish the remaining testing work for this test object Test conditions are typically identified by analysis of the test basis and the test objectives. In some situations, where documentation may be old or non-existent, the test conditions may be identified by talking to relevant stakeholders (e.g., in workshops or during sprint planning). These conditions are then used to determine what to test, using test design techniques identified within the test strategy and/or the test plan. While test conditions are usually specific to the item being tested, there are some standard considerations for the Test Analyst. It is usually advisable to define test conditions at differing levels of detail. Initially, high-level conditions are identified to define general targets for testing, such as “functionality of screen x”. Subsequently, more detailed conditions are identified as the basis of specific test cases, such as “screen x rejects an account number that is one digit short of the correct length”. Using this type of hierarchical approach to defining test conditions can help to ensure the coverage is sufficient for the high-level items. If product risks have been defined, then the test conditions that will be necessary to address each product risk must be identified and traced back to that risk item. At the conclusion of the test analysis activities, the Test Analyst should know what specific tests must be designed in order to meet the needs of the assigned areas of the test project. 1.5 Test Design Still adhering to the scope determined during test planning, the test process continues as the Test Analyst designs the tests which will be implemented and executed. The process of test design includes the following activities: