Menu

Capstone check

Building a Test Strategy — capstone check

Scenario-based, not trivia — 10 questions, 70% to pass. Retake as often as you like. No account needed.

Question 01A team wants to automate a check for every manual test case that currently exists. What should actually decide whether a given check gets automated?
Question 02A team keeps writing end-to-end browser tests for logic that a unit test could verify in milliseconds. What is the right response?
Question 03A stakeholder says "we have 500 automated checks, so quality must be good." What is the flaw here?
Question 04Ten automation candidates are proposed but there is only enough engineering time for three this quarter. What ranking approach fits the strategy this track teaches?
Question 05After four weeks instrumenting a suite, a team finds it does catch regressions — but the failure signal arrives 45 minutes after the responsible engineer has already moved on to other work. Is this suite "helping"?
Question 06A product manager asks the team to automate "exploratory testing of new features" so regressions get found faster. Why is this request confused?
Question 07A proposed check guards behaviour whose "correct" answer changed twice last sprint, and when it fails nobody is named to investigate. It is technically easy to automate. Should it enter the suite?
Question 08Every API change on a team is discovered by a forty-minute end-to-end journey test, then takes a day to diagnose. Which level is the team missing?
Question 09A suite has a 23% false-alarm rate and engineers routinely retry runs until they go green. Leadership proposes buying faster CI hardware as the fix. What does the field note suggest instead?
Question 10A team wants to reduce its defect escape rate, so it plans to add two hundred new checks directly targeting escapes. According to the field note, why is this the wrong lever?

Printed exactly as you type it (2–60 characters). We do not check identity, and nothing is stored unless you pass.