Markdown Editor
Відкрити редактор

Test Case Specification Template (ISO/IEC/IEEE 29119-3)

Test cases with ID, objective, priority, traceability, preconditions, data, steps, expected and actual results; four worked cases

Тестування та якістьСтандартISO/IEC/IEEE 29119-3testcasespecification
Відкрити в редакторіЗавантажити .md

Як використовувати: Use it to write reviewable test cases for one feature set. Define the ID scheme and shared test data first, then write one case per coverage item. The main pitfall is vague expected results such as 'works correctly' that can never fail.

Перегляд

Test Case Specification: [Feature set or test item]

Test case specification for one feature set. The structure follows the test case concepts of ISO/IEC/IEEE 29119-3: each test case has an identifier, objective, priority, traceability, preconditions, inputs and expected results. Replace every [bracketed] value and every test case marked Example.

FieldValue
Document ID[TCS-FEATURE-001]
Test plan[TP-PROJECT-001]
Test design specification[TDS-FEATURE-001]
Test item and version[Orders API 2.8.0, web storefront 5.1.0]
Version[0.1]
Status[Draft / In review / Approved]
Author[@tester]
Reviewer[@reviewer]
Last updatedYYYY-MM-DD

1. Conventions

  • ID format: TC-<AREA>-<NNN>, for example TC-ORD-005. IDs are never reused.
  • Priority: P1 (must run every cycle, high risk), P2 (run every release), P3 (run when time allows).
  • Status values: Not run, Passed, Failed, Blocked, Not applicable.
  • Severity of failures follows the defect scale in the test strategy.

2. Test case summary

IDTitlePriorityTraces toAutomatedStatus
TC-ORD-005Quantity 0 is rejectedP1SRS-FR-022, TCI-05Yes[Not run]
TC-ORD-006Quantity 1 is acceptedP1SRS-FR-021, TCI-05Yes[Not run]
TC-ORD-010Gold member over 100 gets 15% and free shippingP1SRS-FR-024, TCI-06Yes[Not run]
TC-ORD-026Unpaid order cannot be dispatchedP1SRS-FR-031, TCI-07No[Not run]
[TC-AREA-nnn][Title][P1-P3][Requirement, TCI][Yes / No][Status]

3. Shared test data

Data IDDescriptionValuesSetup
TD-01Gold-tier customer[email protected], tier Gold, country DESeed script seed/customers.ts
TD-02Standard customer[email protected], tier Standard, country DESeed script
TD-03Product with stockSKU MUG-RED-01, price 25.00 EUR, stock 500Seed script
[TD-nn][Description][Values][Setup]

4. Test cases

TC-ORD-005: Quantity 0 is rejected

FieldValue
ObjectiveVerify that the lower invalid boundary of the quantity field is refused
PriorityP1
TraceabilitySRS-FR-022; TCOND-02; TCI-05; risk PR-01
TechniqueBoundary value analysis
PreconditionsLogged in as TD-02; cart is empty; product TD-03 page is open
Test dataTD-02, TD-03
StepInput / actionExpected result
1Enter 0 in the quantity fieldField shows error "Enter a quantity from 1 to 99"
2Select "Add to cart"Button is disabled; cart count stays at 0
3Send POST /cart/items with {"sku":"MUG-RED-01","qty":0}HTTP 422 with error code QTY_OUT_OF_RANGE
Execution fieldValue
Actual result[What happened]
Status[Passed / Failed / Blocked]
Defect[BUG-ID if failed]
Executed by / date / build[@name] / YYYY-MM-DD / [build]

TC-ORD-006: Quantity 1 is accepted

FieldValue
ObjectiveVerify that the lower valid boundary is accepted
PriorityP1
TraceabilitySRS-FR-021; TCOND-01; TCI-05
TechniqueBoundary value analysis
PreconditionsLogged in as TD-02; cart is empty
Test dataTD-02, TD-03
StepInput / actionExpected result
1Enter 1 in the quantity field and select "Add to cart"Cart count shows 1; confirmation toast "Added to cart"
2Open the cartOne line: MUG-RED-01, quantity 1, line total 25.00 EUR
Execution fieldValue
Actual result[What happened]
Status[Passed / Failed / Blocked]
Defect[BUG-ID if failed]
Executed by / date / build[@name] / YYYY-MM-DD / [build]

TC-ORD-010: Gold member over 100 gets 15% and free shipping

FieldValue
ObjectiveVerify decision table rule R1 for discounts
PriorityP1
TraceabilitySRS-FR-024; TCOND-03; TCI-06 rule R1; risk PR-01
TechniqueDecision table testing
PreconditionsLogged in as TD-01 (Gold); cart is empty
Test dataTD-01, TD-03
StepInput / actionExpected result
1Add MUG-RED-01 with quantity 4Subtotal 100.00 EUR
2Proceed to checkout summaryDiscount line "-15.00 EUR (Gold 15%)"; shipping 0.00 EUR; total 85.00 EUR
3Change quantity to 3 and return to summaryDiscount "-10% Gold" = -7.50 EUR; shipping 0.00 EUR (rule R2)
Execution fieldValue
Actual result[What happened]
Status[Passed / Failed / Blocked]
Defect[BUG-ID if failed]
Executed by / date / build[@name] / YYYY-MM-DD / [build]

TC-ORD-026: Unpaid order cannot be dispatched

FieldValue
ObjectiveVerify that the invalid transition Created to Shipped is refused
PriorityP1
TraceabilitySRS-FR-031; TCOND-04; TCI-07 transition T7
TechniqueState transition testing (invalid transition)
PreconditionsOrder ORD-TEST-7001 exists in state Created; tester has warehouse role
Test dataOrder created by seed script with no payment
StepInput / actionExpected result
1In the warehouse console, open ORD-TEST-7001"Mark as dispatched" button is not shown
2Send POST /orders/ORD-TEST-7001/dispatchHTTP 409 with error INVALID_STATE_TRANSITION
3Read GET /orders/ORD-TEST-7001State is still Created; audit log has a rejected-transition entry
Execution fieldValue
Actual result[What happened]
Status[Passed / Failed / Blocked]
Defect[BUG-ID if failed]
Executed by / date / build[@name] / YYYY-MM-DD / [build]

[TC-AREA-nnn]: [Title]

FieldValue
Objective[What this case proves]
Priority[P1 / P2 / P3]
Traceability[Requirement; condition; coverage item; risk]
Technique[Technique]
Preconditions[State before step 1]
Test data[Data IDs]
StepInput / actionExpected result
1[Action][Observable result]

5. Review checklist

  • Every coverage item in the test design specification is covered by at least one case.
  • Every expected result is specific and observable.
  • Preconditions and data are reproducible by another tester.
  • No case depends on another case having run first (or the dependency is stated).
  • P1 cases cover every high-risk condition.

6. Approval

RoleNameDecisionDate
Test lead[@name][Approved / Changes requested]YYYY-MM-DD
Requirement owner[@name][Decision]YYYY-MM-DD

Standard and licence note

Structure aligned with ISO/IEC/IEEE 29119-3, Software testing, Part 3: Test documentation, test case specification concepts. This template is original text written for this collection and reproduces no text from the standard; obtain the standard for its normative requirements. Template licence: MIT.

Схожі шаблони

Тестування та якість

Test Design Specification Template (ISO/IEC/IEEE 29119-3)

Feature sets, test conditions, coverage items and worked technique tables (partitions, boundaries, decision table, state transitions)

Тестування та якість

Performance Test Plan and Report Template

Performance plan and report: SLAs, workload mix, Little's law sizing, load, stress, soak and spike tests, percentiles, bottlenecks

Тестування та якість

Test Completion Report Template (ISO/IEC/IEEE 29119-3)

Test completion report: criteria evaluation, deviations, metrics with defect density, outstanding defects, residual risks, sign-off