playwright icon indicating copy to clipboard operation
playwright copied to clipboard

[Feature]: Separate "Aborted" Tests from "Skipped" in Playwright HTML Report

Open kathiresan-r-19912 opened this issue 10 months ago • 3 comments

🚀 Feature Request

When a test suite reaches its globalTimeout during execution, any remaining unexecuted test cases are marked as Skipped in the Playwright HTML report. However, this does not accurately represent why these tests were not executed.

  • Modify Playwright’s test result processing to track tests that were aborted due to globalTimeout.
  • Update the HTML reporter to display a separate Aborted tab for such tests.

This enhancement would provide better visibility into test execution and help teams understand execution interruptions more clearly.

Example

Use Case

Consider a test suite with 1500 test cases.

  • I have manually skipped 50 cases using a @skip tag.
  • I have set a globalTimeout of 3 hours for the suite.
  • The suite execution reaches the timeout after running 1250 tests, leaving 250 tests unexecuted.
  • Currently, these 250 tests are reported as "Skipped", even though they were not explicitly skipped but rather aborted due to the global timeout.

Motivation

Feature Request

It would be beneficial to introduce a separate "Aborted" tab or status in the Playwright HTML report.

  • This will differentiate tests that were explicitly skipped from those that were aborted due to globalTimeout or other interruptions.
  • This enhancement would improve reporting clarity and help teams analyze test results more effectively.

Expected Behavior

  • When a test case is explicitly skipped (test.skip() or @skip tag in BDD), it should still appear under Skipped.
  • When a test case is not executed due to global timeout, it should be categorized under a new "Aborted" section instead of Skipped.

kathiresan-r-19912 avatar Feb 05 '25 06:02 kathiresan-r-19912

Why was this issue closed?

Thank you for your involvement. This issue was closed due to limited engagement (upvotes/activity), lack of recent activity, and insufficient actionability. To maintain a manageable database, we prioritize issues based on these factors.

If you disagree with this closure, please open a new issue and reference this one. More support or clarity on its necessity may prompt a review. Your understanding and cooperation are appreciated.

pavelfeldman avatar Sep 04 '25 01:09 pavelfeldman

@dgozman, I'm curious to know the purpose of adding the tags and closing this.

kathiresan-r-19912 avatar Oct 28 '25 12:10 kathiresan-r-19912

Consider annotations and adding a HTML report filter for "Interrupted".

agg23 avatar Nov 11 '25 17:11 agg23