Agile Testing and Quality Flashcards
6 cards from real SAFe® 5 DevOps Certification practice questions. Tap to flip, then mark Knew It or Still Learning — missed cards come back until you master them.
Read the first 6 Agile Testing and Quality flashcards as text
What does 'shift-left testing' mean in the context of SAFe DevOps?
Answer: Moving testing activities earlier in the development process
Shift-left testing means performing testing activities as early as possible in the development lifecycle to catch defects sooner when they are cheapest to fix.
In SAFe DevOps, which practice most directly implements shift-left testing?
Answer: Writing tests before or alongside code development using TDD or BDD
TDD and BDD are the primary practices implementing shift-left testing by integrating automated test creation as early as possible in development.
What is the primary business benefit of shift-left testing in a SAFe DevOps environment?
Answer: It reduces the cost of fixing defects by finding them much earlier in development
Defects found earlier in development are significantly cheaper to fix than those found in production, making shift-left testing highly cost-effective.
Which SAFe built-in quality practice best aligns with shift-left testing by making quality everyone's responsibility from the start?
Answer: 'Build quality in' — embedding quality practices throughout all development activities
SAFe's 'build quality in' principle means every team member is responsible for quality throughout development, not just QA at the end.
In SAFe DevOps, who holds responsibility for shift-left testing activities?
Answer: The entire Agile team, with developers writing automated tests as part of development
Shift-left testing is a whole-team responsibility in SAFe — developers, testers, and product owners all contribute to quality from the beginning of work.
What does the 'test pyramid' model recommend about the distribution of test types in a SAFe DevOps pipeline?
Answer: A large base of fast unit tests, fewer integration tests, and minimal end-to-end tests
The test pyramid recommends many fast, cheap unit tests at the base, fewer integration tests in the middle, and minimal slow end-to-end tests at the top.