Test Strategy Quiz
Test your knowledge of test strategy fundamentals.
What is the primary difference between a test strategy and a test plan?
Strategy defines “what and why”, plan defines “how and when”
Strategy is short-term, plan is long-term
Strategy is created by developers, plan by QA
There is no difference, they are the same
In the testing pyramid, which type of tests should make up the largest portion?
A feature has HIGH business impact and MEDIUM probability of defects. What is the appropriate risk level and testing approach?
Minor risk - minimal testing needed
Critical risk - extensive testing required
Trivial risk - can skip testing
Which of the following is a valid “exit criteria” for testing?
Development team has started coding
Test environment is available
All P0/P1 bugs are fixed and verified
Requirements document is created
What is the correct severity for a bug that causes complete system shutdown?
When should you prefer manual testing over automation?
For exploratory and usability testing
What is the recommended percentage of test coverage for unit tests in a healthy testing pyramid?
Which environment should most closely mirror production configuration?
How should you calculate automation ROI?
Initial development cost only
Number of test cases automated
(Manual effort saved - Automation cost) / Automation cost
Time to market improvement
What should be the primary driver for test strategy decisions?
Latest testing tools and technologies
Business objectives and risk analysis
Industry best practices only
Quiz Results Interpretation
9-10 correct: Excellent! You have strong grasp of test strategy fundamentals.
7-8 correct: Good understanding. Review the areas you missed.
5-6 correct: Fair knowledge. Revisit the lesson material.
Below 5: Review the lesson thoroughly and retake the quiz.
Key Concepts to Remember
-
Strategy vs Plan: Strategy is the “what and why”, plan is the “how and when”
-
Testing Pyramid: 80% unit tests, 15% integration tests, 5% E2E tests
-
Risk-Based Testing: Prioritize based on impact and probability
-
Exit Criteria: Define clear quality gates before release
-
Automation ROI: Calculate return on investment for automation decisions
-
Business Alignment: Always connect testing to business objectives