feat(execute): Use test spec names as markers for execute
#1367
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🗒️ Description
Adds labeled markers and names to all execute formats, derived from the test spec type names of the test where they came from.
Since we only have a single execute format that matches all specs we have, all execute test names contain "transaction_post" in the ID, and no reference or marker to the specification that was used to fill it:
With this change the test IDs now contain the name of the test spec that was used to produce the test:
Also we can now narrow execution to a specific type of test using markers.
E.g.
will run only transaction tests.
🔗 Related Issues
✅ Checklist
mkdocs serve
locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.