Playwright · Senior · Question 76 of 77

What makes a good E2E failure message for the team?

1It shows the full stack trace and nothing else
2It says what the user couldn't do and shows the evidence
3It's short, like "failed", so the report stays small

Show the answer

Correct answer: It says what the user couldn't do and shows the evidence

Explanation

Steps, custom assertion messages and attached traces turn "timeout 30000ms" into "couldn't add item to cart: button disabled".

Further reading

Test yourself

Take the Playwright · Senior quiz: questions and options are shuffled, and you get a review of your mistakes at the end.