tests: centralize running of recipe tests #13150
Merged
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.
kind of a prerequisite to #13148, but useful on its own.
The recipes each need their own
yarn install
run (and it turns outintegration-test
didn't have itsinstall
run, it was just falling back to the rootjest
and (I believe) theyarn link
edlighthouse
).As a result it doesn't really make sense to include
docs/recipes/integration-test/example-lh-auth.test.js
in the default jest tests, which ideally should work with just agit clone ... && yarn && yarn build-all && yarn test
.This PR breaks it out into its own separate
jest
call, and centralizes the running of the recipe tests to their ownpackage.json
.