PLAYWRIGHT JAVA / EXECUTED EVIDENCE

A test result you
can investigate.

UI and API automation against a fictional banking application. Inspect the browser state, watch a transfer, open the actual Extent report, or step through a trace.

13 tests × 3 browsers passed in CI
Open passing Extent reportInspect intentional failureVerified CI run ↗

Watch the transfer workflow

Real Playwright recording with 200ms action slow motion. Synthetic credentials, recipient and balance.

Local Windows recording uses an existing cached Chromium executable. The matching Playwright 1.63 browser matrix was verified separately in CI.

UI + API consistency

Executed transfer test showing £2,374.50 balance and £125.50 payment to Jamie Lee

Assert the visible debit and REST transaction record. This screenshot is from the CI run.

Download transfer trace

An honest failing example

Failure demo shows actual balance £2,500.00, while an intentional assertion expects £9,999.00

The assertion deliberately expects £9,999.00. The command exits nonzero and preserves useful evidence. Excluded from normal CI.

Download failure trace

Inside the Extent report

A real passing test with its screenshot, exception/status details and links to trace, video and logs.

Actual Extent Spark report showing successful transfer test and evidence links

Open the Trace Viewer

Download a trace above and drop it into Microsoft Playwright Trace Viewer, or open it locally with mvn exec:java -Dexec.mainClass=com.microsoft.playwright.CLI -Dexec.args="show-trace path/to/trace.zip".

Explore action timeline, DOM snapshots, screenshots, network and console events. Java assertion failures are shown in Extent/TestNG; raw browser tracing is not a Java assertion recorder.