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

[kathiresan-r-19912]

🚀 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.