QUESTION 72 What test process is included as part of TPI Next? [1]
According to TPI Next, the test process consists of four main phases: Test Strategy, Test Preparation, Test Execution and Test Completion. Each phase has several key areas that describe the activities and tasks involved in the phase. One of the key areas in the Test Preparation phase is Test Environment, which covers the identification, specification, realization and maintenance of the test environment. The test environment includes the hardware, software, network, data and tools that are required to perform the testing activities. The test environment should be aligned with the test objectives and the system under test, and should be managed throughout the test process. TPI NextTPI Next book References: Test Process Improvement (TPI) | TMap TPI NEXT | TMap
QUESTION 78 You are the Test Manager on a new project. The schedule is aggressive and will require the team to work at peak efficiency. The requirements are not well defined yet, but it is clear that the project will be using new technologies. To help the developers meet the development schedule, an offshore group will be added to the development team. At this time there is not enough budget to add more testing resources. The project stakeholders are very concerned about the quality of delivered product and will be watching the project closely, particularly during the testing cycles. The exit criteria from the system test level require no open high priority/severity defects, 100% pass rate for all test cases covering risks that are classified as “high” or “very high”, 90% pass rate for all “medium” risks and 50% pass rate for all “low” and “very low” risks. Given this information, which lifecycle model should you recommend?[3]
An iterative/incremental lifecycle model is a type of software development lifecycle that divides the project into smaller iterations or increments, each delivering a part of the functionality and undergoing its own planning, analysis, design, implementation, and testing phases1. This model is suitable for projects that have aggressive schedules, unclear requirements, new technologies, distributed teams, and high quality expectations, as it allows for early feedback, risk reduction, parallel development, frequent delivery, and continuous improvement2. Therefore, option B is the correct answer. Option A is incorrect because a spiral model is a type of iterative/incremental model that adds risk analysis and prototyping activities to each iteration3. While this model can also handle unclear requirements, new technologies, and high quality expectations, it may not be the best choice for projects that have aggressive schedules and distributed teams, as it requires more time and communication for risk assessment and prototyping4. Option C is incorrect because a V-model is a type of sequential model that maps each development phase to a corresponding testing phase in a V-shaped diagram5. This model is suitable for projects that have clear and stable requirements, well-known technologies, co-located teams, and moderate quality expectations, as it allows for early verification, traceability, and defect prevention. However, this model may not be the best choice for projects that have aggressive schedules, unclear requirements, new technologies, distributed teams, and high quality expectations, as it does not allow for early feedback, risk reduction, parallel development, frequent delivery, and continuous improvement. Option D is incorrect because a waterfall model is a type of sequential model that follows a linear sequence of phases from requirements to deployment. This model is suitable for projects that have simple and fixed requirements, well-known technologies, co-located teams, and low quality expectations, as it allows for easy planning, management, and documentation. However, this model may not be the best choice for projects that have aggressive schedules, unclear requirements, new technologies, distributed teams, and high quality expectations, as it does not allow for early feedback, risk reduction, parallel development, frequent delivery, and continuous improvement. References: 1: ISTQB Glossary, Iterative/incremental lifecycle model 2: ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 3: ISTQB Glossary, Spiral model 4: ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 5: ISTQB Glossary, V-model : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 : ISTQB Glossary, Waterfall model : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1 : ISTQB Advanced Level Test Manager Syllabus, Section 1.2.1
QUESTION 81 You are not confident with the assessment of the risk level and you suspect that it will be possible to find high- priority bugs in low-risk areas. Furthermore the period for test execution is very short. Your goal is to test all the product risks in a risk-based way, while assuring that each product risk gets at least some amount of testing. Which of the following answers describes the best test execution schedule in this scenario?
T1, T2, T3, T4, T5, T6, T7, T8, T9, T10
T1, T3, T5, T7, T9, T2, T4, T6, T8, T10
T10, T9, T8, T7, T6, T5, T4, T3, T2, T1
T10, T8, T6, T4, T2, T9, T7, T5, T3, T1
Section: Testing Process
QUESTION 88 Which classification information would be most useful to capture for newly identified defects? [2]
Capturing the system build information for newly identified defects is crucial as it helps in tracking the defect back to a specific state of the software. This information is essential for developers to understand the context of the defect and for testers to manage regression testing effectively. It allows for precise identification of when the defect was introduced, aiding in quicker resolution and ensuring that similar issues can be prevented in future builds. References: ISTQB Glossary, Distributed Testing1 Defect Report in ISTQB: Software Engineering – The Knowledge Academy ISTQB Advanced Level Test Manager Syllabus, Section 3.2.1 Defect classification and prioritisation: ISTQB offers a standardised defect classification scheme The most useful classification information to capture for newly identified defects is the system build that the defect was found in. This is because the system build is the version of the software that is compiled, integrated, and tested together. By capturing the system build for each defect, the test team can track and manage the defects more effectively, and identify the root causes and impacts of the defects. The system build can also help to reproduce and verify the defects, and to measure the quality and progress of the software development. Defect Management – ISTQB not-for-profit association References: Certified Tester Advanced Level Test Manager (CTAL-TM) – ISTQB not-for-profit association, ISTQB Test Manager Certification – ISTQB Exams Worldwide – ISTQB Official Registration, Defect Management – ISTQB not-for-profit association
Be the first to reply