From a Playwright test to test evidence.
Test Case 12 checks cart arithmetic for two products. Test Case 13 checks quantity 4 in the cart. Test Cases 14–16 reach checkout through different account paths. Use those artifacts to practice test design.
Try an explicitly proposed 1–10 quantity rule; confirm the real product limit first.
Vary positive quantity and correct line-total arithmetic.
Trace Test Case 14 and try an action out of sequence.
Choose where to go next.
Chapter notes
Read notes on test principles, test levels, reviews, test design techniques, and managing test activities.
Flashcards
Work through 115 cards on testing terms and techniques. Mark each one for review or as understood.
Question bank
Answer 100 practice questions and read the explanation for each choice. Filter by chapter or knowledge level.
Timed practice session
Try a 40-question, 60-minute practice session with a timer, flags, and a chapter breakdown. These are study questions, not an official exam.
Test Design Lab
Use the Playwright shopping and checkout tests to practice boundaries, decision rules, path coverage, and release review.
Glossary
Look up 71 testing terms, including prioritization, reporting, and testing quadrants, with plain-language explanations.
Syllabus Standard
ISTQB® CTFL v4.0.1
Exam Question Count
40 Multiple Choice
Time Allocated
60 Minutes (75 mins non-native)
Passing Score
65% (26 out of 40 points)
Cognitive Levels
K1 (Remember), K2 (Understand), K3 (Apply)
Chapter notes / CTFL v4.0.1
Detailed notes, 7 principles, test levels, review types, test techniques, risk management, and exam pitfalls for all 6 chapters.
Flashcards (115 Cards)
Select the card or press Space to reveal the answer. Use the arrow keys to move between cards.
Practice questions with explanations
Answer 100 independent study questions. Filter by chapter or knowledge level, then review the reasoning behind each option.
Timed practice questions
Choose a practice mode. The full session has 40 questions and a 60-minute timer; these are independent study questions, not an official ISTQB exam.
Selected Mode
Full session
Question Count
40 Questions
Time Allocated
60 Minutes
Practice Target
65% (26/40 points)
Before you begin
- Each question has exactly 1 correct answer out of 4 options.
- You can flag questions to review before final submission.
- There is no negative marking; answer every question.
- After submission, review your score and results by chapter.
SAMUEL ABOYE / TEST DESIGN LAB
From requirement
to evidence.
Use the Playwright Automation Exercise repository to examine cart checks, a register-during-checkout path, a small coverage model, and release risk. Proposed rules are identified as practice assumptions.
Automation Exercise shopping flow
Samuel Aboye's Playwright repository ↗ tests product quantity, cart totals, and three checkout account paths. The lab uses those specific artifacts as its study case.
- TC 13 · Product quantity. The test file ↗ sets quantity to 4 and checks that the cart displays 4. The 1–10 boundary rule below is a proposed practice rule, not a documented app limit.
- TC 12 / CartPage · Arithmetic. The test calls a page-object method ↗ asserting positive cart quantity and line total equal to price × quantity. Four hypothetical cart rows exercise those assertions.
- TC 14 · Checkout path. A guest proceeds from cart to register or log in, creates an account, returns to checkout, and pays. Tests 15 and 16 cover other account paths.
How to use this lab: The boundary limit, synthetic cart rows, out-of-sequence actions, and risk scores are teaching fixtures. The repository provides test code, not a complete product specification; verify untested behaviors against requirements or the application.
Explore product quantity.
Test Case 13 checks quantity 4. To practice boundary analysis, propose a 1–10 whole-number quantity rule, then check 0, 1, 10, and 11. Confirm the application's actual limits before asserting a rejection.
Proposed product quantity · whole numbers 1–10
Why these cases?
For each limit, 2-value BVA uses the value on the limit and its neighbor in the adjacent partition. 3-value BVA also uses the neighbor inside the accepted partition. If the range is narrow, a value can serve two purposes; it appears once with both reasons.
Boundary values 0, 1, 10, 11
| Case | Input | Expected behavior | Why? |
|---|
EP check: try 5 as an ordinary value inside the proposed range. It does not establish the real product limit.
Questions beyond the quantity boundary exercise
- Blank: Does the product form reject an empty quantity?
- 1.5: Is a fractional quantity permitted? The exercise assumes whole items.
- “ 10 ” pasted: Does the app trim whitespace or reject it?
- Cart and server: Is quantity checked again after submission?
Inspect cart assertions.
Two yes/no conditions yield four hypothetical cart rows. Test Case 12 calls CartPage's check for positive quantity and correct price × quantity total. Mark a row only after you have exercised its assertions.
The page object first requires quantity > 0, then requires the displayed total to equal unit price × quantity. The example rows use a hypothetical $20 unit price.
| Row | Quantity positive? | Total correct? | Expected assertion | Tested? |
|---|
The zero-quantity rows are proposed test fixtures, not claims that the shopping UI permits quantity zero. If the app prevents them, test the validation at the appropriate layer.
Trace checkout.
Follow the register-during-checkout test path from the repository. The buttons simulate its steps; an out-of-order action is rejected by this teaching model only.
Simulated stage: Cart
Try Proceed as guest.
Out-of-sequence attempts 0
- Start with a product in the cart. No action attempted yet.
Try Proceed as guest → Create account → Resume checkout → Pay and confirm. Then reset and try Pay and confirm from Cart. The repository test also deletes its temporary account after the order.
View the modeled test path
| From | Test action | Next stage |
|---|
These stages summarize Test Case 14. The simulator's out-of-order rejection is a teaching constraint, not a claim about the live store.
Inspect the cart checks.
A short teaching helper models CartPage's quantity and line-total assertions. Select example rows to trace statements and true/false outcomes. This snippet is an exercise model, not copied repository source.
1 function cartLineValid(qty, price, total) {2 let valid = false;3 if (qty > 0) {4 valid = true; }5 if (total !== price * qty) {6 valid = false; }7 return valid; }The real CartPage uses assertions. This separate helper lets you compare statement and decision outcome coverage without claiming these exact lines exist in the repository.
All statements ran, but two outcomes remain untested.
EX01 traces every counted statement but misses both false outcomes. This is a hand-mapped exercise, not an instrumented Playwright run or a coverage report from the repository.
Discuss the evidence.
Use historical defects and a concrete failure mode to decide where to test next. Neither number proves the product is defect free.
When did we find them?
Practice data for a shopping release: 11 issues found before release, 2 first reported after. These are invented numbers, not the repository's test results.
11 of 13 known defects were found before release.
Before ÷ (before + after). Keep the release and observation window consistent. This measure cannot include defects nobody has found, or show their severity.
Which failure matters?
Choose a concrete shopping failure mode, then review suggested checks. The 1–5 scores and bands are practice planning choices.
Try more than one quantity and unit price. Compare the cart line total with price × quantity, then check the order summary.
Reason for concern: CartPage contains a quantity and line-total assertion; a wrong total could affect the amount presented at checkout.
↑ Likelihood · Impact →
Likelihood × impact. Example bands: low 1–9, medium 10–15, high 16–25. Document why you chose the scores; use previous defects, recent code changes, and user impact.
Method reference: ISTQB CTFL v4.0.1, sections 4.2 (black-box design), 4.3 (white-box coverage), and 5.2 (risk management). The scenario comes from Samuel Aboye's Playwright repository ↗; proposed quantity limits, synthetic rows, coverage helper, and risk numbers are teaching examples. Read the syllabus ↗
END OF WORKED EXAMPLE SA / QA NOTES
CTFL Glossary
Plain-language explanations of testing terms used in these study notes. Refer to the ISTQB glossary for canonical wording.