Software & Web App Testing

Real portfolio pieces built during the course, not a certificate for its own sake. Each one is work you can show.

• Test planA one page plan for the checkout feature: scope in and out, approach, environments and browsers, entry and exit criteria, risks and who does what.
• Test case suiteFifteen or more structured cases across the three sprint stories, guest checkout, discount codes and the order summary, with preconditions, data, numbered steps and one numeric expected result each.
• Bug report packEight defect reports, drawn from the nine distinct defects the simulation week plants, with reproduction steps, expected against actual, environment, evidence and a defensible severity. The centrepiece of the portfolio.
• Test run reportWhat was executed, what passed and failed, what was blocked, what was not covered, and what that means for shipping.
• Retest and impact checkWhat the fix was retested against, which areas it could reach and why, what each of them did, and whether the defect can be closed.
• Cross-browser and responsive matrixBrowsers and rendering engines against breakpoints, with a result in every cell and defect references where they failed.
• Regression checklistThe re-runnable pre-release list: core paths, recently changed areas and the neighbours of every fix in this release, timed so it fits the release window.
• First automated testOne readable browser automation script against a public practice application, with an assertion you have proved fails when the behaviour changes.
• Release sign-off noteThe note the delivery lead needs before the 4pm deploy: what was tested, what was not covered, every known issue with its reference, and a recommendation you are prepared to put your name to.