ISTQB-CTFL-KR 문제 176
다음 중 테스트 상태 보고서에 포함되어야 하는 내용은 무엇입니까?
I. 추정 세부 정보
II. 열린 결함과 닫힌 결함의 총 수
III 실제 소요된 노력
IV. 결함 보고서
V. 실행된 테스트, 실패한 테스트, 차단된 테스트의 수
I. 추정 세부 정보
II. 열린 결함과 닫힌 결함의 총 수
III 실제 소요된 노력
IV. 결함 보고서
V. 실행된 테스트, 실패한 테스트, 차단된 테스트의 수
정답: D
The following should be included in a test status report: total number of open and closed defects, actual effort spent, and number of executed, failed, and blocked tests. A test status report is a document that provides information on the results and status of testing activities for a given period or phase. A test status report should include information that is relevant, accurate, and timely for the intended audience and purpose. Some of the information that should be included in a test status report are: total number of open and closed defects, which can indicate the defect trend and defect density of the software product; actual effort spent, which can indicate the productivity and efficiency of the testing process; number of executed, failed, and blocked tests, which can indicate the test progress and test coverage of the software product. The following should not be included in a test status report: estimation details, defect reports, and impact analysis. Estimation details are not part of a test status report, but rather part of a test plan or a test estimation document. Estimation details provide information on the expected time, resources, and costs for testing activities, not on the actual results or status of testing activities. Defect reports are not part of a test status report, but rather separate documents that provide detailed information on individual defects found during testing. Defect reports include information such as defect description, defect severity, defect priority, defect status, defect resolution, etc.
Defect reports can be referenced or summarized in a test status report, but not included in full. Impact analysis is not part of a test status report, but rather part of a risk assessment or prioritization process. Impact analysis provides information on the potential effects or consequences of a change or a defect on the software product or project. Impact analysis can be used to evaluate the amount or scope of testing to be performed, but not to report the results or status of testing activities. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 141.
Defect reports can be referenced or summarized in a test status report, but not included in full. Impact analysis is not part of a test status report, but rather part of a risk assessment or prioritization process. Impact analysis provides information on the potential effects or consequences of a change or a defect on the software product or project. Impact analysis can be used to evaluate the amount or scope of testing to be performed, but not to report the results or status of testing activities. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 141.
ISTQB-CTFL-KR 문제 177
탐색적 테스트에 관한 다음 진술 중 어느 것이 사실입니까?
정답: B
Exploratory testing is an experience-based test technique in which testers dynamically design and execute tests based on their knowledge, intuition, and learning of the software system, without following predefined test scripts or test cases. Exploratory testing can be conducted following a session-based approach, which is a structured way of managing and measuring exploratory testing. In a session-based approach, the testers perform uninterrupted test sessions, usually lasting between 60 and 120 minutes, with a specific charter or goal, and document the issues detected, the test coverage achieved, and the time spent in session sheets.
Session sheets are records of the test activities, results, and observations during a test session, which can be used for reporting, debriefing, and learning purposes. The other statements are false, because:
* Exploratory testing is not a test technique in which testers explore the requirements specification to detect non testable requirements, but rather a test technique in which testers explore the software system to detect functional and non-functional defects, as well as to learn new information, risks, or opportunities. Non testable requirements are requirements that are ambiguous, incomplete, inconsistent, or not verifiable, which can affect the quality and effectiveness of the testing process. Non testable requirements can be detected by applying static testing techniques, such as reviews or inspections, to the requirements specification, before the software system is developed or tested.
* Exploratory testing is not a test technique used by testers during informal code reviews to find defects by exploring the source code, but rather a test technique used by testers during dynamic testing to find defects by exploring the behavior and performance of the software system, without examining the source code. Informal code reviews are static testing techniques, in which the source code is analyzed by one or more reviewers, without following a formal process or using a checklist, to identify defects, violations, or improvements. Informal code reviews are usually performed by developers or peers, not by testers.
* In exploratory testing, testers usually do not produce scripted tests and establish bidirectional traceability between these tests and the items of the test basis, but rather produce unscripted tests and adapt them based on the feedback and the findings of the testing process. Scripted tests are tests that are designed and documented in advance, with predefined inputs, outputs, and expected results, and are executed according to a test plan or a test procedure. Bidirectional traceability is the ability to trace both forward and backward the relationships between the items of the test basis, such as the requirements, the design, the risks, etc., and the test artifacts, such as the test cases, the test results, the defects, etc.
Scripted tests and bidirectional traceability are usually associated with more formal and structured testing approaches, such as specification-based or structure-based test techniques, not with exploratory testing. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
* ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.3, Experience-based Test Design Techniques1
* ISTQB Glossary of Testing Terms v4.0, Exploratory Testing, Session-based Testing, Session Sheet, Non Testable Requirement, Static Testing, Informal Review, Dynamic Testing, Scripted Testing, Bidirectional Traceability2
Session sheets are records of the test activities, results, and observations during a test session, which can be used for reporting, debriefing, and learning purposes. The other statements are false, because:
* Exploratory testing is not a test technique in which testers explore the requirements specification to detect non testable requirements, but rather a test technique in which testers explore the software system to detect functional and non-functional defects, as well as to learn new information, risks, or opportunities. Non testable requirements are requirements that are ambiguous, incomplete, inconsistent, or not verifiable, which can affect the quality and effectiveness of the testing process. Non testable requirements can be detected by applying static testing techniques, such as reviews or inspections, to the requirements specification, before the software system is developed or tested.
* Exploratory testing is not a test technique used by testers during informal code reviews to find defects by exploring the source code, but rather a test technique used by testers during dynamic testing to find defects by exploring the behavior and performance of the software system, without examining the source code. Informal code reviews are static testing techniques, in which the source code is analyzed by one or more reviewers, without following a formal process or using a checklist, to identify defects, violations, or improvements. Informal code reviews are usually performed by developers or peers, not by testers.
* In exploratory testing, testers usually do not produce scripted tests and establish bidirectional traceability between these tests and the items of the test basis, but rather produce unscripted tests and adapt them based on the feedback and the findings of the testing process. Scripted tests are tests that are designed and documented in advance, with predefined inputs, outputs, and expected results, and are executed according to a test plan or a test procedure. Bidirectional traceability is the ability to trace both forward and backward the relationships between the items of the test basis, such as the requirements, the design, the risks, etc., and the test artifacts, such as the test cases, the test results, the defects, etc.
Scripted tests and bidirectional traceability are usually associated with more formal and structured testing approaches, such as specification-based or structure-based test techniques, not with exploratory testing. References: ISTQB Certified Tester Foundation Level (CTFL) v4.0 sources and documents:
* ISTQB Certified Tester Foundation Level Syllabus v4.0, Chapter 2.2.3, Experience-based Test Design Techniques1
* ISTQB Glossary of Testing Terms v4.0, Exploratory Testing, Session-based Testing, Session Sheet, Non Testable Requirement, Static Testing, Informal Review, Dynamic Testing, Scripted Testing, Bidirectional Traceability2
ISTQB-CTFL-KR 문제 178
소프트웨어는 세 가지 입력을 사용하여 연간 자동차 세금을 계산합니다.
- E; 차량의 배출 수준
- P : 차량의 힘
-T 차량의 종류
P의 입력 값은 15와 350 사이의 정수 양수 값이 될 수 있습니다.
다음 답변 중 P 입력에 대한 경계 값의 올바른 목록은 무엇입니까?
- E; 차량의 배출 수준
- P : 차량의 힘
-T 차량의 종류
P의 입력 값은 15와 350 사이의 정수 양수 값이 될 수 있습니다.
다음 답변 중 P 입력에 대한 경계 값의 올바른 목록은 무엇입니까?
정답: B
A correct list of boundary values for the P input should include the minimum and maximum values of the valid range (15 and 350), as well as the values just below and above the boundaries (14 and 351). Boundary value analysis is a test design technique that involves testing the values at or near the boundaries of an input domain or output range, as these values are more likely to cause errors than values in the middle. Option B satisfies this condition, as it has all four boundary values (14, 15, 350, 351). Option A has only two boundary values (14 and 351), option C has only two boundary values (15 and 350), and option D has no boundary values at all. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 34.
ISTQB-CTFL-KR 문제 179
회고에 관한 다음 진술 중 어느 것이 사실입니까?
정답: D
Retrospectives are a crucial part of Agile practices, aiming to identify process improvements and determine how to implement them effectively. They should involve participants discussing not only what improvements could be made but also how to integrate and sustain those improvements within the project context, including the software development lifecycle. This makes statement D accurate according to the ISTQB CTFL syllabus.
ISTQB-CTFL-KR 문제 180
테스트 엔지니어가 테스트하는 동안 결함을 발견했습니다. 개발자가 결함을 수정한 후 테스트 엔지니어는 테스트의 전체 섹션을 다시 실행하기로 결정했습니다. 다음 중 어느 것이 맞습니까?
정답: C
The test engineer should re-run the tests, in order to ensure that new defects have not been introduced by the fix. This is also known as regression testing, which is a type of testing that verifies that previously tested software still performs correctly after a change. Regression testing helps to detect any side effects or unintended consequences of a fix or a modification. The other options are incorrect reasons for re-running the tests. The test engineer should not re-run the tests, as they have already been run, and results recorded, because this ignores the possibility of new defects caused by the fix. The test engineer should not re-run the tests, they should be part of the developer tests, because this assumes that developer tests are sufficient and reliable, which may not be true. The test engineer should not re-run the tests, because the defect shows that the test cases need to be updated, because this does not address the impact of the fix on other test cases or functionalities. Verified References: A Study Guide to the ISTQB Foundation Level 2018 Syllabus - Springer, page 41.
- 다른 버전
- 1241ISTQB.ISTQB-CTFL-KR.v2026-01-22.q147
- 1297ISTQB.ISTQB-CTFL-KR.v2026-01-17.q183
- 978ISTQB.ISTQB-CTFL-KR.v2025-04-09.q132
- 1090ISTQB.ISTQB-CTFL-KR.v2025-03-01.q124
- 최근 업로드
- 109Snowflake.ADA-C02.v2026-06-08.q23
- 123Microsoft.SC-300-KR.v2026-06-08.q173
- 111Microsoft.DP-300-KR.v2026-06-08.q157
- 115Microsoft.MS-102-KR.v2026-06-08.q240
- 111Microsoft.DP-300-KR.v2026-06-08.q176
- 114Microsoft.SC-100-KR.v2026-06-08.q115
- 120TheBerylInstitute.CPXP.v2026-06-06.q56
- 179ACAMS.CAMS7-KR.v2026-06-05.q213
- 181PaloAltoNetworks.XSIAM-Analyst.v2026-06-04.q72
- 152NLN.NEX.v2026-06-04.q54
[×]
PDF 파일 다운로드
메일 주소를 입력하시고 다운로드 하세요. ISTQB.ISTQB-CTFL-KR.v2026-03-16.q188 모의시험 시험자료를 다운 받으세요.