Istqb Certified Tester Foundation Level CTFL · Free Practice Question Easy
Question 16
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
Writing a test script before setting up the configuration management process
-
D
Executing a performance efficiency test for a component during component testing
Reveal correct answer
Correct answer: C
Explanation
2.1.5. Shift-Left Approach
The principle of early testing is sometimes referred to as shift-left because it is an approach where testing is performed earlier in the SDLC. Shift-left normally suggests that testing should be done earlier (e.g., not waiting for code to be implemented or for components to be integrated), but it does not mean that testing later in the SDLC should be neglected.
There are some good practices that illustrate how to achieve a “shift-left” in testing, which include:
• Reviewing the specification from the perspective of testing. These review activities on specifications often find potential defects, such as ambiguities, incompleteness, and inconsistencies
• Writing test cases before the code is written and have the code run in a test harness during code implementation
• Using CI and even better CD as it comes with fast feedback and automated component tests to accompany source code when it is submitted to the code repository • Completing static analysis of source code prior to dynamic testing, or as part of an automated process
• Performing non-functional testing starting at the component test level, where possible. This is a form of shift-left as these non-functional test types tend to be performed later in the SDLC when a complete system and a representative test environment are available
A shift-left approach might result in extra training, effort and/or costs earlier in the process but is expected to save efforts and/or costs later in the process. For the shift-left approach it is important that stakeholders are convinced and bought into this concept
A. Reviewing user requirements before formal acceptance by stakeholders is an example of the shift left approach as it involves identifying issues early in the development process, which is a key principle of shifting left in software testing.
B. Writing a component test before the corresponding code is written aligns with the shift left approach by focusing on early testing to detect and fix defects at an early stage, reducing the cost and effort of fixing them later in the development cycle.
C. Writing a test script before setting up the configuration management process is NOT an example of the shift left approach. Configuration management is typically a foundational step that should precede test script creation to ensure a stable and controlled environment for testing.
D. Executing a performance efficiency test for a component during component testing is in line with the shift left approach as it involves testing for non-functional requirements early in the development cycle, helping to identify and address performance issues sooner rather than later.
Discussion
Think the marked answer is wrong, or have a better explanation? Share it below — comments appear after review.
