Tweak template test scripts #290
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
I've been umming and ahhing on the right approach here, as I like a fairly unopinionated `test` script into which the user can pass their desired flags. Practically speaking, we have some other tooling like our package publishing pipeline which presumes that the `test` script is suitable for exhaustive CI testing. `test:watch` should be a reasonable compromise for local testing, and already has some SEEK precedence with ~46 `package.json` results returned from a GitHub search.
🦋 Changeset detectedLatest commit: ab1c5d4 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
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.
I've been umming and ahhing on the right approach here, as I like a fairly unopinionated
testscript into which the user can pass their desired flags.Practically speaking, we have some other tooling like our package publishing pipeline which presumes that the
testscript is suitable for exhaustive CI testing.test:watchshould be a reasonable compromise for local testing, and already has some SEEK precedence with ~46package.jsonresults returned from a GitHub search.