ISTQB Agile Tester Principles Quiz

1. How should test cases be structured in agile projects?

Very detailed with 50+ steps each

Short, focused, and reusable with clear acceptance criteria

Documented in waterfall format

Created after coding is complete

2. In agile, what is the purpose of a retrospective regarding testing?

Document all defects found

Reflect on testing processes and identify improvements

Finalize test documentation

Assign blame for test failures

3. How does agile testing handle non-functional requirements like performance?

Deferred until post-release testing

Integrated into sprint testing activities and automated checks

Tested separately after functional testing completes

Not a priority in agile

4. What is a key characteristic of agile testing metrics?

Focus on test case count and documentation volume

Emphasis on actionable insights for continuous improvement

Detailed tracking of every test execution

Comparison against waterfall baselines

5. In agile, acceptance test-driven development (ATDD) involves:

Writing tests after code is completed

Collaboratively writing acceptance tests before development

Testing exclusively by QA team

Formal test case documentation

6. What does 'shift-left' testing in agile mean?

Testing moved earlier in the development cycle

Testing after deployment to production

Reducing the number of test phases

Testing only critical features

7. How should agile teams handle changing requirements during a sprint?

Reject all changes to maintain sprint stability

Evaluate impact and adjust testing strategy accordingly

Ignore requirements and continue original plan

Delay testing until all changes are final

8. What is the primary advantage of test automation in agile?

Eliminates the need for manual testing

Enables rapid feedback and supports frequent releases

Reduces the number of testers needed

Guarantees zero defects

9. In agile, risk-based testing means prioritizing tests based on:

Alphabetical order of features

Likelihood and impact of potential failures

Number of available test cases

Sprint sequence

10. What is the role of a tester in pair programming scenarios?

Observer only, no participation

Active participant providing real-time feedback and test ideas

Separate from development activity

Testing only after pair programming ends

11. In agile testing, what does 'definition of done' refer to?

Project completion date

Agreed criteria a user story must meet before considered complete

End of sprint ceremony

Final deployment to production

12. Which practice helps agile teams maintain quality while releasing frequently?

Delaying testing until the final phase

Automated regression testing in the CI/CD pipeline

Manual testing by external auditors

Comprehensive documentation reviews

13. What is exploratory testing in agile?

Scripted testing with predefined test cases

Simultaneous learning, test design, and execution without detailed plans

Testing in production environment only

Testing after sprint completion

14. In agile, who is primarily responsible for testing during development?

Only the dedicated QA team

The entire cross-functional team including developers

Project manager exclusively

External testing vendors

15. What is the agile testing quadrant used for?

Categorizing test types by technology and business focus

Measuring team velocity

Allocating budget across sprints

Prioritizing feature development

16. What does TDD (Test-Driven Development) require developers to do first?

Write production code

Write failing unit tests before writing code

Complete system design documentation

Perform integration testing

17. Which principle emphasizes that testers should work closely with developers and business stakeholders?

Test isolation principle

Team collaboration principle

Risk-based principle

Automation-first principle

18. Which type of testing is most critical in agile to catch defects early?

User acceptance testing

Automated unit and integration testing

Manual exploratory testing only

Performance testing at project end

19. In agile testing, what is the primary focus compared to traditional waterfall testing?

Completing all documentation before testing begins

Continuous testing integrated throughout the development cycle

Testing only after development is fully complete

Focusing exclusively on system integration testing

20. In agile testing, continuous integration means code changes are merged and tested:

Once per month

At the end of each sprint

Multiple times per day

Only after user acceptance testing

ISTQB Agile Tester Agile Testing Principles Quiz