Skip to content
Back to curriculum

Final release assessment

Pick the strongest next step in each scenario. After submitting, compare your reasoning with the explanation.

12 decisions · 10 correct to pass

1. The owner says “Make publishing faster.” What makes the request independently checkable?
2. The agent proposes the right test name but it does not exist in package.json. Which action improves team instructions?
3. The vendor shows an API newer than the locked package. What is the best default?
4. The agent needs an internal helper checklist for a repeatable form review. Which configuration is the smallest fit?
5. A new agent tool asks for network permission to complete a layout experiment. What should the reviewer check first?
6. A global design change turns warning text unreadable in one theme. What evidence resolves it?
7. An operator presses Escape to close the incident form and loses focus. What belongs in the test?
8. A clean install passes and older published rows now look like drafts. What is the next release decision?
9. A viewer failed to publish in the test, but the fixture used an admin client for data operations. What should happen?
10. An interface shows that a notification was delivered when the server only accepted it into a queue. Which fix is sound?
11. A source review finds an unclear filter and a browser check is green. What fact should the reviewer seek?
12. Pilot tests pass, but a confirmed access boundary then fails in the pilot. What is the strongest release call?