lecture 14 of 160 completed

Reports, screenshots and logs

Selenium collects nothing on its own. Every piece of evidence from a failed run is something you set up deliberately.

What you'll learn

Why Selenium records nothing unless you write it
The cheapest evidence worth adding to any suite
Why artifacts must be uploaded, not just written

Playwright records a trace of everything. Cypress saves a screenshot and video automatically. Selenium saves nothing at all, ever, unless you write the code.

That is the trade-off for a library rather than a framework, and it means a failed run on a build server tells you only what you arranged to be told. Here is the minimum worth arranging.

A screenshot on failure. This is the highest-value thing you can add, and it is a few lines in an afterEach:

full course

Keep reading with the full course

The Foundations track and the first lessons in each framework are free. This lesson needs full course access. A course plan includes all lessons for Playwright, Cypress and Selenium.

See course plans →