FIELD GUIDE / CTAL-TAE v2.0

Make automation observable.
Make every check count.

Study eight test automation topics alongside Samuel Aboye's Playwright suite ↗. Follow real cart assertions, reusable page objects and CI reports from test intent to evidence. Then use the flashcards, questions and practice timer to check your understanding.

26 tests
in the source project
8 chapters
with project field notes
0 / 128
flashcards mastered
0 / 100
questions answered
Not taken
best practice score
PROJECT WALKTHROUGHTEST CASES 12 + 13

From a shopping-cart rule to a test result.

The spec adds products to a cart. A page object reads the displayed unit price, quantity and total, then checks the arithmetic. Another test asks for four units and verifies the quantity shown in the cart.

01 / INTENTCart rule

Line total should equal unit price × quantity.

02 / IMPLEMENTATIONPage object

CartPage reads the row and checks the relation.

03 / EVIDENCEAssertion

The test passes or shows exactly which check failed.

Read test cases 12 and 13 in GitHub ↗

Syllabus Study Guide

Eight chapters with concrete field notes connecting syllabus ideas to the Playwright project.

Interactive Flashcards

Review key ideas about architecture, metrics, testability and maintenance in a focused card deck.

Practice Question Bank

Work through 100 independent practice questions with immediate explanations and chapter filters.

Timed Practice

Try a 40-question, 90-minute exercise with flags and chapter feedback. This practice set uses equal-weight scoring.

Engineering Tools

Walk through source code, explore example ROI and detection calculations, and compare architecture layers.

Automation Glossary

Searchable database of 26 independent study definitions and automation concepts.

Syllabus Standard

ISTQB® CTAL-TAE v2.0

Exam Question Count

40 Multiple Choice

Time Allocated

90 Minutes (113 mins non-native)

Passing Score

43 of 66 weighted points

Cognitive Levels

K2 (Understand), K3 (Apply), K4 (Analyze)

Official CTAL-TAE v2.0: 40 questions, 66 possible points, 43 to pass, 90 minutes. The practice timer on this page gives each question one point and uses a 65% learning target, so its result is not an official exam score. Check ISTQB exam details ↗

Syllabus Study Guide & Notes (v2.0)

Eight syllabus chapters with practical notes drawn from a real Playwright repository.

Interactive Flashcards (128 Cards)

Click the card (or press Spacebar) to flip. Use arrow keys to navigate.

Card 1 of 128 Space = Flip | = Next | ⬅ = Prev
Ch 1: Objectives Click to Flip
Category: Concept Front
Answer & Explanation Click to Flip Back
Study explanation Back

Practice Question Bank with Explanations

100 questions with immediate feedback. Every question includes syllabus rationale and distractor justifications.

100 Questions

CTAL-TAE Timed Practice

Use a timed question set to check your understanding. This independent practice tool uses equal-weight questions.

40-question practice
40 questions • 90 minutes • equal-weight practice target: 26 correct. Not an official exam simulation.
Quick Sprint
10 Questions • 15 Minutes. Perfect for rapid daily review.
Hard Mode (K3/K4)
25 Advanced scenario & analysis questions • 50 Minutes.

Selected Mode

40-question practice set

Question Count

40 Questions

Time Allocated

90 Minutes

Practice Target

65% correct

Practice rules

  • 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 in this practice tool; answer every question.
  • After submission, see your score against the practice target and a chapter breakdown. The official exam requires 43 of 66 weighted points.

Engineering Tools & Calculators

A source-backed test walkthrough, example calculations and an illustrative architecture explorer.

PLAYWRIGHT / SOURCE WALKTHROUGH

What the test checks, and what it cannot claim.

Look at Test Cases 12 and 13 in the public playwright-automation-exercise repository ↗. The application under test is an e-commerce site. This walkthrough follows its actual test code.

01 / CONDITION

Two cart lines

Test Case 12 adds product IDs 1 and 2, opens the cart and calls the same total calculation check for each. The rule is price × quantity = displayed total.

Open the spec ↗
02 / ORACLE

Assertion in CartPage

The page object reads the displayed price, quantity and total, converts them to numbers, and asserts that the quantity is positive and the total matches the calculation.

Open the assertion ↗
03 / VARIATION

Quantity four

Test Case 13 sets quantity to four before adding a product, then checks the cart shows 4. It checks persistence of quantity; it does not independently assert the total for that case.

Open the second case ↗
04 / SIGNAL

CI evidence

The workflow uploads the HTML report and test results on every run. The configuration also asks for a trace on first retry and screenshots and video on failure.

Open the pipeline ↗
CHECKPOINT / REAL REPOSITORY METHODView CartPage.js ↗
const price = Number(priceText.replace(/[^0-9.]/g, ''));
const quantity = Number(quantityText.trim());
const total = Number(totalText.replace(/[^0-9.]/g, ''));
expect(quantity).toBeGreaterThan(0);
expect(total).toBe(price * quantity);
CHECK YOUR REASONING
What will Test Case 12 miss if the displayed unit price itself is wrong?

It will miss the incorrect price if the displayed total is still consistent with that incorrect price. Compare against an independent expected price if this matters.

Does Test Case 13 also check the line total for quantity four?

No. That test asserts that the cart shows the quantity 4. Test Case 12 checks total calculations for two separate products.

Does a Chromium CI run prove Firefox and WebKit pass?

No. The configuration defines those browsers, but the current test:ci script selects Chromium and the workflow only installs Chromium.

Automation ROI Calculator

Explore the economics with your own estimates. The model assumes automation saves all listed manual hours on each cycle and spreads annual maintenance evenly; defaults are illustrative, not project data.

1-Year ROI: +61%
3-Year ROI: +207%
3-Year Net Savings: $136,800
Break-Even Threshold: Cycle 15 (~6.9 months)

Defect Detection Efficiency (DDE)

Compare recorded detections with post-release escapes. Use data from one period and comparable defect definitions; the result does not measure overall product quality.

Automation share of known defects: 55.8%
Detected before release: 93.0%
Post-release escape share: 7.0%
Detection share: 90%+ detected before release

Repository code explorer

Trace a browser check through the actual JavaScript test, fixture, page object and CI workflow.

The page object reads a cart row and checks its arithmetic.

Loading repository excerpt...
Open this file in GitHub ↗

Test automation glossary

Study-friendly explanations written for this guide. Consult the official ISTQB Glossary for canonical wording.