Shift-Left Testing

Correct Answer: Running unit tests as code is being developed

The Shift-Left Testing approach in Disciplined Agile emphasizes early testing in the development lifecycle. Running unit tests as code is being developed represents this principle perfectly because: - It integrates testing into the earliest stages of development - It helps catch defects at their source - It reduces the cost of fixing defects - It promotes continuous quality assurance The other options are incorrect because they all represent traditional or 'right-sided' testing approaches where testing occurs later in the development cycle. Testing after sprint completion, during final stages, or at the end of iterations contradicts the core principle of Shift-Left Testing, which aims to find and prevent defects as early as possible in the development process. Early testing reduces technical debt and improves overall product quality.

Correct Answer: They become technical advisors who guide developers on testability patterns

In a Shift-Left Testing strategy within Disciplined Agile, test automation engineers transform into technical advisors who guide developers on testability patterns. This is the correct approach because: Shift-Left testing emphasizes moving testing activities earlier in the development cycle, where test automation engineers collaborate closely with developers from the start. They help establish testing practices, guide architectural decisions for testability, and enable developers to create more testable code. The other options are incorrect because: - Maintaining existing test suites is too narrow a focus and doesn't align with the proactive nature of Shift-Left testing - Creating end-to-end test cases in final development contradicts the early testing principle of Shift-Left - Specializing only in performance testing at milestones misses the broader scope of Shift-Left testing, which involves continuous testing throughout development

Correct Answer: It helps detect defects earlier in the development cycle when they are less costly to fix

The key advantage of Shift-Left Testing in agile development is detecting and fixing defects early in the development cycle, which significantly reduces the cost and effort of fixes. This approach aligns with agile principles by integrating testing activities from the beginning of development, improving quality throughout the process. The other options are incorrect because: - Performing all testing at the end of sprints contradicts the continuous testing principle of agile and defeats the purpose of shift-left testing. - Moving testing responsibilities away from developers to QA teams opposes the collaborative nature of agile and the concept of shared responsibility. - Postponing testing until code is stable represents a waterfall approach, which contradicts both agile principles and shift-left testing philosophy.