Capstone project for Software Testing and QA

Test the new receiving flow before rollout

Mangrove is rolling out a new goods-received flow on the Store app's handheld scanners: receivers scan the supplier's delivery note, count cases, record short, over and damaged items with photos, and submit a goods received note (GRN) that updates stock, even when the stock room has no signal. Today receiving takes about 51 minutes per delivery and about 1 GRN in 12 is corrected later. Plan and run the testing for the release: a risk-based plan, designed test cases with the technique named, two exploratory sessions, API and data checks, accessibility and real-world checks, bug reports, and a go/no-go recommendation for the pilot. Use a test version of any app you can reach, or the flow as described in the lessons; say which in your write-up. Plan for 4 to 6 hours.

What you hand in

A one-page test plan: scope, risks ranked by likelihood and impact, what you will and will not test, and the approach for each risk
Designed test cases in a table, each naming its technique (partitions, boundaries, decision table or state transitions)
Charters, session notes and debriefs for two exploratory sessions
API and data check results, accessibility and real-world notes, and bug reports
A go/no-go summary with the evidence and conditions for rollout

Check your work

Tick each item when your project meets it. Be strict: this is the rubric the reviewer uses.

Risks are ranked by likelihood and impact, testing depth follows the ranking, and the plan says plainly what is out of scope and why
Test cases name their technique and use it correctly: one value per partition, both sides of each boundary, a decision table that covers every rule, and invalid as well as valid state transitions
Both exploratory sessions have a focused charter (target, resources, information), time-boxed notes with questions and findings, and a short debrief
API checks cover status codes, body and error format, at least one negative and one duplicate-submit test, and a SQL or data check that stock matches the GRN after submission
Accessibility and real-world checks were actually run: screen reader labels, contrast, target size, a cheap phone or scanner, and a dead-signal moment during submission
Bug reports have a specific title, environment, minimal steps, expected and actual results, evidence, and severity with its impact on stores
The go/no-go recommendation is backed by evidence (open bugs by severity, risks tested and not tested) and sets clear conditions, such as a pilot in a few stores

0 of 7 checked

Model answer

The model answer opens once your capstone passes the review, so you can compare your work with an outline of a strong submission.

Hand in your capstone

Your links are checked automatically, then the work is scored against the rubric above, item by item, with comments. A pass counts toward the course certificate and shows on your profile.

Loading…