Run project tests on test project rebuild #105
Closed
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
jtoar
force-pushed
the
main
branch
22 times, most recently
from
59d1ee7
to
d0554e0
Compare
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.
When working on redwoodjs/redwood#6221 I added a few tests to the crwa template. When doing that I figured it would be nice to know that that we don't break them in the future when updating the template code.
The tests are already run as part of CI. But I wanted an easier way to run them locally, so I added it as a step when regenerating the test project fixture. I think it makes sense because it's something you have to do anyway when you update the template.
Technically one can run the e2e tests locally, but it's just not something I regularly do.