← All documents
Work sample · Manual QA

QA test documentation
sample

Type Test cases, execution log, bug report Tooling Jira, Azure DevOps Context Release cycle
What this is: an anonymised sample based on the kind of work I've done across telecom, banking and streaming projects: functional testing of purchase and subscription flows on web and mobile, across Windows, iOS and Linux. The feature below (a mobile subscription order flow) is representative; names and data are invented, the method is real.

1. Test case design

Test cases are written so anyone on the team can execute them and get the same result: precise preconditions, unambiguous steps, one clear expected outcome per case. Feature under test: mobile subscription purchase in a telecom self-service app.

TC-SUB-001 · Priority: High · Type: Functional

New subscription is purchased and activated end to end

Precondition
Logged-in customer, valid payment method on file, no active subscription of this type.
Steps
  1. Open Plans, select the "Mobile M" subscription
  2. Confirm the plan details and add it to the order
  3. Proceed through checkout, confirm payment
  4. Return to the account overview
Expected result
Order confirmation is shown with the correct plan and price; the subscription appears as active in the account; exactly one charge is created.
Status
PASSED
TC-SUB-004 · Priority: High · Type: Negative

Expired payment method is rejected before the order completes

Precondition
Logged-in customer whose stored card has expired.
Steps
  1. Select any plan and proceed to checkout
  2. Confirm payment with the expired card on file
Expected result
Checkout is blocked with a clear message; no subscription is activated and no charge is created.
Status
FAILED → BUG-2317

2. Execution log

Every run is recorded per cycle and per platform, so the release decision rests on evidence, not memory. This feature ships on web and mobile, so coverage spans several environments.

IDTest casePlatformCycle 1Cycle 2Notes
TC-SUB-001Subscription purchased end to endWeb (Win)PassPass
TC-SUB-001Subscription purchased end to endiOS appPassPass
TC-SUB-002Plan change keeps billing consistentWeb (Win)BlockedPassTest env billing stub fixed after C1
TC-SUB-003Companion app login (password manager autofill)iOS + LinuxPassPassAutofill verified on both
TC-SUB-004Expired payment method rejectedWeb (Win)FailFailBUG-2317 open
TC-SUB-005Order confirmation email receivedCross-platformPassPass

3. Bug report

A bug report has one job: let the developer reproduce the problem on the first attempt. Exact data, exact steps, expected versus actual, and evidence.

BUG-2317 · Component: Checkout / Payment validation · Found in: Release 4.2.0-RC1

Expired card is accepted when the order is submitted quickly

Severity
High
Environment
UAT · build 4.2.0-RC1 · web checkout · reproducible on Windows (Chrome, Firefox)
Steps to reproduce
  1. Log in as a customer whose stored card has expired
  2. Select a plan and proceed to checkout
  3. Click "Confirm payment", then immediately click it a second time before the validation response returns
Expected
Payment validation rejects the expired card and blocks the order.
Actual
The second click submits the order before the validation response is processed; the subscription is activated with an expired card, and a failed charge is created downstream.
Impact
Active subscriptions backed by no valid payment; downstream billing failures, manual clean-up and customer support load.
Evidence
Screen recording and network log attached to the ticket. Not reproducible when the confirm button is clicked once and allowed to respond, which points at a missing disabled state on submit.

4. Why this format works

In regulated environments the documentation is part of the deliverable. This structure gives a project three things: repeatability (anyone can re-run any test), traceability (every requirement maps to cases, every failure to a bug), and a defensible release decision backed by an execution record across every platform the product ships on.

Questions about the method? contact@borsux.com ← All documents