Weekly QA Challenges

Practical testing scenarios from real projects. Write how you would approach it, then read how other testers solved the same problem.

Interactive practice challenges

Short, free exercises with instant feedback and explanations. Try any as a guest; sign in to save your progress.

Weekly QA Challenge #03

Open

List the key scenarios for a forgot-password feature.

Weekly QA Challenge #02

Closed

Track down an intermittent automation failure without guessing.

Weekly QA Challenge #01

Closed

Design a practical test approach for a checkout API handling carts, payments and stock.

Read the scenario. Each challenge describes a situation testers meet at work, such as a flaky login test or a checkout API that has to handle carts, payments and stock.
Write your approach. Explain what you would check first, which test cases you would design, what data you need and how you would report the result. There is no single right answer; the reasoning is what matters.
Compare with other testers. Once a challenge closes, read how other members approached the same problem and note the cases you missed.

It starts with the risk: what could go wrong for a real user or the business.
It covers positive, negative and boundary cases, not only the happy path.
It says how you would confirm a fix, for example by re-running a test many times for an intermittent failure.
It stays short enough that a teammate could follow it in a few minutes.

Want to build the skills first? Try the QA roadmaps, check yourself with a skill assessment, or ask a question in QA Discussions.