feat: add --expected-failures baseline and composite GitHub Action #113
+697
−1
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.
Summary
Adds support for SDKs that don't yet pass all conformance tests to still run conformance in CI without failing, by specifying a YAML baseline file of known/expected failures.
Closes #99
Changes
--expected-failures <path>CLI flagAdded to both
serverandclientcommands. Points to a YAML file:Exit code logic:
Composite GitHub Action (
action.yml)SDKs can now reference the action directly instead of writing their own npx scripts:
Inputs:
mode,url,command,expected-failures,suite,scenario,timeout,verbose,version,node-versionFiles
src/expected-failures.ts— YAML loading, baseline evaluation, result printingsrc/expected-failures.test.ts— 16 unit testsaction.yml— composite GitHub Actionsrc/index.ts— added--expected-failuresoption to both commandspackage.json— addedyamldependency