[Example] 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)

This PR is a demo - it marks a few tests with @Skip so the Travis log will have something to show.

It gives the example that you can put some other tag after @Skip that is like an explanation of why it is skipped. People can see that in the output, and if you are testing in future while fixing the bug you could run behat specifying just that tag to run that particular test.

Related Issue

Motivation and Context

Help people see what tests exist that need bugs fixed.

How Has This Been Tested?

We are about to see.

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.

[phil-davis]

See #28202 for the proposed actual code to configure, without the example skipped tests.

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