handle retry in html formatter

[davidjgoss]

Details

• Teach fake-cucumber about retry
• Add a compatibility-kit feature for retry
• Give query the smarts to get results from the latest attempt only
• Move willBeRetried to TestCaseFinished
• Update test data for json-formatter?

No React components actually need updating.

Motivation and Context

Fixes #1533, #902.

Our Ruby and JavaScript implementations support retry, but the HTML formatter and related tooling don't handle retried test cases at the moment.

This changes query (and thus the React components) to treat the last attempt that ran for any given test case as the "canonical" result. This is consistent with the Cucumber implementations' own reporting with builtin formatters.

Also an opportunity to resolve #902 (and thus cucumber/cucumber-js#1409) before any consumers start using that misplaced field.

Types of changes

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (in messages only) (fix or feature that would cause existing functionality to not work as expected).

Checklist:

• The change has been ported to Java.
• The change has been ported to Ruby.
• The change has been ported to JavaScript.
• The change has been ported to Go.
• The change has been ported to .NET.
• I've added tests for my code.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have updated the CHANGELOG accordingly.

[aslakhellesoy]

This is a breaking change to messages, so don't forget a changelog entry there.

Great PR!!

[davidjgoss]

Would be great to get this out in a patch release of cucumber-js so folks don't have to wait for 8.0.0 (this will have to be a breaking change actually, we do have consuming projects relying on the position of willBeRetried.

[aurelien-reeves]

Looks good to me 👍

[davidjgoss]

@aslakhellesoy you okay with this one now?