ISTQB-CTFL-KR 문제 136
ISTQB-CTFL-KR 문제 137
Maintenance testing can be triggered by various reasons, such as corrective maintenance (fixing defects), adaptive maintenance (adapting to new environments), perfective maintenance (improving performance), preventive maintenance (avoiding future problems), etc. Impact analysis is a technique that is used to assess the extent and nature of changes introduced by maintenance activities on the software product or project.
Impact analysis helps to identify which parts of the software product are affected by the changes, which parts need to be modified or updated accordingly, which parts need to be retested or verified for correctness or compatibility, etc. Regression testing is a type of testing that verifies that previously tested software still performs correctly after a change or a modification. Regression testing helps to detect any side effects or unintended consequences of maintenance activities on the software product's functionality or quality.
Regression testing can be performed at various levels and scopes depending on the impact analysis results.
Therefore, in maintenance testing, impact analysis is used to evaluate the amount of regression testing to be performed. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 20.
ISTQB-CTFL-KR 문제 138
The Agile Testing Quadrants framework categorizes tests based on their purpose and audience:
* Quadrant 1 (Q1): Technology-facing tests (unit and component tests).
* Quadrant 2 (Q2): Business-facing tests supporting development (e.g., BDD tests).
* Quadrant 3 (Q3): Business-facing tests that critique the system (B).
* Includes usability testing, exploratory testing, and UAT to ensure software meets user expectations.
* Quadrant 4 (Q4): Technology-facing tests that critique the system (e.g., performance, security testing).
Option B correctly defines Q3 since it focuses on evaluating the user experience, exploring the system, and validating business expectations.
Reference: ISTQB CTFL v4.0 Syllabus, Section 5.1.7 - Agile Testing Quadrants
ISTQB-CTFL-KR 문제 139
ISTQB-CTFL-KR 문제 140
* The minimum number of test cases needed to achieve full branch coverage, is usually higher than that needed to achieve full statement coverage, which is a test coverage criterion that requires that all executable statements in the code are executed at least once by the test cases. This is because branch coverage is a stronger criterion than statement coverage, as it implies statement coverage, but not vice versa. For example, a single test case can achieve full statement coverage for an if-then-else statement, but two test cases are needed to achieve full branch coverage, as both the then branch and the else branch need to be exercised.
* If full branch coverage has been achieved, then all unconditional branches within the code have not necessarily been exercised, as unconditional branches are branches that do not depend on any decision, and are always executed, such as a goto statement, a break statement, a return statement, etc.
Unconditional branches are not part of the branch coverage criterion, as they do not represent different paths in the control flow of the code. However, they are part of the statement coverage criterion, as they are executable statements in the code.
* If full branch coverage has been achieved, then all combinations of conditions in a decision table have not necessarily been exercised, as a decision table is a test design technique that represents the logical relationships between multiple conditions and their corresponding actions, in a tabular format. A decision table can have more combinations of conditions than the number of decision outcomes in the code, as each condition can have two or more possible values, such as true or false, yes or no, etc. For example, a decision table with four conditions can have 16 combinations of conditions, but the corresponding code may have only two decision outcomes, such as pass or fail. To exercise all combinations of conditions in a decision table, a stronger test coverage criterion is needed, such as condition combination coverage, which requires that all possible combinations of condition outcomes in the code are executed at least once by the test cases. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
* ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.3.1, Test Coverage Criteria Based on the Structure of the Software
* ISTQB Glossary of Testing Terms v4.0, Branch Coverage, Statement Coverage, Branch, Decision, Decision Outcome, Unconditional Branch, Decision Table, Condition Combination Coverage
- 다른 버전
- 1240ISTQB.ISTQB-CTFL-KR.v2026-01-22.q147
- 1295ISTQB.ISTQB-CTFL-KR.v2026-01-17.q183
- 977ISTQB.ISTQB-CTFL-KR.v2025-04-09.q132
- 1090ISTQB.ISTQB-CTFL-KR.v2025-03-01.q124
- 최근 업로드
- 118TheBerylInstitute.CPXP.v2026-06-06.q56
- 154ACAMS.CAMS7-KR.v2026-06-05.q213
- 173PaloAltoNetworks.XSIAM-Analyst.v2026-06-04.q72
- 150NLN.NEX.v2026-06-04.q54
- 191Microsoft.AZ-500-KR.v2026-06-04.q213
- 179Microsoft.DP-600-KR.v2026-06-04.q98
- 194Microsoft.AZ-204-KR.v2026-06-04.q237
- 180Microsoft.PL-600-KR.v2026-06-04.q112
- 238Microsoft.SC-300-KR.v2026-06-03.q151
- 208Microsoft.DP-600-KR.v2026-06-03.q70
PDF 파일 다운로드
메일 주소를 입력하시고 다운로드 하세요. ISTQB.ISTQB-CTFL-KR.v2026-03-16.q188 모의시험 시험자료를 다운 받으세요.