미션 크리티컬 시스템을 테스트할 때는 높은 적용 범위를 달성해야 합니다. 다음 중 가장 높은 커버리지를 달성하기 위해 구조 기반 커버리지 기술로 구현해야 하는 기술은 무엇입니까?
정답: A
Explanation Multiple condition coverage is a structure-based test technique that aims to achieve a high level of coverage by testing all possible combinations of conditions and outcomes in each decision point of the code or design of the system under test. Multiple condition coverage verifies that each condition in a decision point has an effect on the outcome and that there are no hidden defects or logical errors in the code or design. Multiple condition coverage requires some knowledge of the internal structure or implementation of the system under test; it focuses on how the system does what it does rather than what it does. Multiple condition coverage is one of the most rigorous and complex structure-based test techniques because it can generate a large number of test cases for each decision point, especially if there are many conditions involved. You can find more information about multiple condition coverage in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], Chapter 4, Section 4.3.
CTFL_Syll2018-KR 문제 7
다음 중 유지보수 테스트를 가장 잘 설명하는 설명은 무엇입니까? [K2]
정답: A
Explanation The statement that best characterizes maintenance testing is A. Maintenance testing is triggered by changes to delivered software and uses impact analysis to minimize the amount of regression testing needed. Maintenance testing is a type of testing that is performed on a software product after it has been delivered to the customer or user, and aims to ensure that the software product still meets its requirements and expectations after any changes or modifications. Maintenance testing is triggered by changes to delivered software, such as bug fixes, enhancements, patches, updates, etc., and uses impact analysis to determine the scope and extent of regression testing needed. Impact analysis is a technique that analyzes the potential effects of changes on the existing software product and its components, dependencies, interfaces, etc., and identifies which parts of the software product need to be retested or modified. Impact analysis helps to minimize the amount of regression testing needed by focusing on the most affected or critical parts of the software product. A detailed explanation of maintenance testing can be found in [A Study Guide to the ISTQB Foundation Level 2018 Syllabus], pages 81-82.
CTFL_Syll2018-KR 문제 8
피어 리뷰란 무엇입니까?
정답: D
Explanation A peer review is a review done by colleagues at the same organizational level, such as developers, testers, or managers. An informal review without moderator is called a walkthrough. A review done by developers and testers together is called an inspection. A review done by developers only is not a specific type of review. References: Certified Tester Foundation Level (CTFL) Syllabus - ASTQB, Section 3.1.1, Page 18
CTFL_Syll2018-KR 문제 9
다음 목록 중 기본 테스트 프로세스의 주요 활동의 올바른 순서를 나타내는 것은 무엇입니까(다른 모든 활동과 동시에 발생해야 하는 제어 활동은 제외)?
정답: A
CTFL_Syll2018-KR 문제 10
전시물을 참고하세요 다음 테스트 사례를 실행해야 하지만 시간이 제한되어 있으며 테스트 기간이 끝나기 전에 모든 테스트 사례가 완료되지 않을 수도 있습니다. 첫 번째 활동은 재테스트를 실행한 후 회귀 테스트 스크립트를 실행하는 것입니다. 사용자는 테스트에 우선순위를 제공했습니다. 다음 중 우선순위 및 기타 제약사항을 고려하여 적절한 테스트 실행 일정을 제공하는 것은 무엇입니까? [K3]
정답: C
Explanation The test execution schedule should take into account the prioritization and other constraints given in the question. The first activity is to run any re-tests, followed by the regression test script. Users have supplied their priority order to tests. Therefore, the test execution schedule should start with the re-test defect no 52, which is shown in the image as a table with 9 rows and 4 columns. The table is titled "Re-test defect no 52". The columns are labeled: "#", "Description", "Priority", "Note", "Re-test". The table is populated with data about different tasks and their priority and notes. The tasks are related to sales figures and account administration. The table is in black and white. The re-test defect no 52 has three tasks: c, a, and d, which have priority 1, 2, and 3 respectively. Therefore, the test execution schedule should start with c, followed by a, and then d. After that, the regression test script should be run, which is task e. Then, the remaining tasks should be run according to the user priority order: b, g, i, h, and f. Therefore, the test execution schedule is c, a, d, e, b, g, i, h, and f.
