1. Introduction
The shift-left approach means moving testing activities earlier in the software development lifecycle. This can include early reviews, early test design, and even early non-functional testing. This question asks which option is NOT an example of shift-left.
[한국어 요약]
Shift-left는 테스트 활동을 개발 생명주기의 앞 단계로 당기는 개념입니다.
이 문제는 제시된 보기 중 어떤 것이 Shift-left 예시가 아닌지를 묻습니다.
2. Sample Question
Which of the following is NOT an example of the shift-left approach?
- a) Reviewing the user requirements before they are formally accepted by the stakeholders
- b) Writing a component test before the corresponding code is written
- c) Executing a performance efficiency test for a component during component testing
- d) Writing a test script before setting up the configuration management process
3. Correct Answer
✔ Correct Answer: d)
Option d) is not an example of shift-left. Test scripts should be managed under configuration management (CM). Creating test scripts before the CM process is set up is not sensible and not what shift-left means.
[한국어 요약]
정답은 d)입니다.
테스트 스크립트는 형상관리 하에 관리되어야 하므로, CM 프로세스 전에 만드는 것은 Shift-left의 올바른 예가 아닙니다.
4. Analysis of Each Option
a) Reviewing user requirements early — ✖ NOT the correct choice
This is an example of shift-left. Reviewing user requirements before stakeholders formally accept them allows early detection of defects in requirements.
[한국어 요약]
a는 요구사항을 공식 승인 전에 미리 리뷰하는 것으로, 전형적인 초기 리뷰 = Shift-left 예시입니다.
b) Writing a component test before coding — ✖ NOT the correct choice
This describes Test-Driven Development (TDD), which is a test-first (and therefore shift-left) practice. Tests are written before the component code.
[한국어 요약]
b는 TDD를 의미하며, 코드를 작성하기 전에 테스트를 만드는 Test-first → Shift-left 기법입니다.
c) Early non-functional testing at component level — ✖ NOT the correct choice
Executing a performance efficiency test already at component testing is another example of shift-left. Non-functional tests are being performed earlier than usual (not only at system or acceptance level).
[한국어 요약]
c는 성능 효율 테스트를 컴포넌트 단계에서 미리 수행하는 것으로, 비기능 테스트를 앞당기는 Shift-left 예입니다.
d) Writing test scripts before CM process — ✔ NOT an example of shift-left
This is not a good practice and not what shift-left means. Test scripts themselves should be under configuration management. Creating them before the CM process is ready leads to unmanaged and inconsistent test assets.
[한국어 요약]
d는 형상관리 프로세스가 준비되기 전에 테스트 스크립트를 만드는 것으로,
관리되지 않은 스크립트를 양산할 수 있어 바람직하지 않고 Shift-left 개념과도 맞지 않습니다.
5. Summary
Shift-left is about performing valid testing activities earlier, such as early reviews, early test design, or early non-functional tests. However, creating unmanaged test scripts before configuration management is in place is not a valid example of shift-left, which is why option d) is the correct answer. refer to FL-2.1.5
[한국어 요약]
Shift-left는 “유효한 테스트 활동”을 앞당기는 것이지,
형상관리 없이 테스트 스크립트를 먼저 만들어서 관리 혼란을 일으키는 것이 아닙니다.
따라서 Shift-left가 아닌 예시는 d)입니다.
Related: More ISTQB posts