Repository navigation
Add optional Test attemptId in CTRF 0.2.0 - #73
Merged
Merged
Conversation
Ma11hewThomas
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Adds optional
attemptIdto the Test object, identifying its final attempt (including an initial attempt when no retry occurred). Uses the same schema definition and requirements as the existing retry-historyattemptId: a non-empty string, UUID recommended, unique within the enclosing execution. The existing retry-history definition is unchanged.Extends the existing comprehensive examples and existing valid-document, string-constraint and type-validation suites. Prepares specification 0.2.0 metadata and changelog. Related to #66.
Validation: schema format/lint, all standalone examples and the inline comprehensive example pass; 18 reference and 156 normative cases pass. Embedded schema matches the authoritative file byte-for-byte, and Test/history identifier schema definitions are identical. The informative test directory is absent, as on main.