feat: CLI to test extension implementations #435
Merged
Conversation
This file contains 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
OrKoN
force-pushed
the
orkon/test-spec
branch
3 times, most recently
from
3a2bed9
to
f6c1a02
Compare
OrKoN
changed the title
OrKoN
force-pushed
the
orkon/test-spec
branch
from
f6c1a02
to
cb496a2
Compare
Lightning00Blade
approved these changes
Jan 24, 2023
OrKoN
force-pushed
the
orkon/test-spec
branch
from
cb496a2
to
87147c0
Compare
This was referenced Jan 3, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR renames the benchmark test to the "spec" test and adds a new CLI command that allows running the spec test against any stringify or runner extension:
Closes #275
I moved the spec test content into a JS file because I could not find good rollup plugins to bundle test resources with the CLI.