lecture 16 of 180 completed

Reports and reading a run you did not watch

The HTML report plus traces means a failure on the build server is usually diagnosable without reproducing it.

What you'll learn

What a failed CI run leaves behind
Why the flaky count matters more than the pass count
Why artifacts must be uploaded, not just written

A failure on your machine is easy: you watched it. A failure on the build server is a line in a log nobody read, on a machine that no longer exists. What you collect automatically is all you will ever have.

Playwright's reporting is unusually good, and combined with traces it usually removes the need to reproduce anything.

The HTML report is the default and the one you will use daily:

members only

Keep reading with the full course

The Foundations track and the first 5 lectures of each framework are free. This lecture is part of the paid course, which unlocks every lecture, all three frameworks, and downloads.

See the options →