Report skipped scenarios

[phil-davis]

Description

The behat UI tests will do a dry-run report of skipped scenarios after doing the real scenarios.
That will help people to be able to see skipped tests, and thus be annoyed enough by it to do something
about fixing the bugs.

The dry-run report is only done if the default set of tests are run (i.e. the @Skip tags have been skipped by default)

You can add a "description" of why a scenario is skipped, by simply adding an extra tag that effectively contains the reason, for example:

@Skip @special-file-upload-broken-due-to-issue-1234
Scenario: Upload a special sort of file in a special way

See #28195 for an example test run with some scenarios skipped.

Related Issue

Issue #27858

Motivation and Context

Help people see what tests exist that are waiting for bugs to be fixed.

How Has This Been Tested?

Local runs of UI tests with and without @Skip scenarios

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.

It will need some developer doc enhancement to explain what it does, as well as how best to use @Skip tags.

[phil-davis]

Backport in #28610

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.