Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create integration tests and trigger them on remote push events with GitHub Actions. #25

Closed
HeavyMedl opened this issue May 2, 2024 · 0 comments · Fixed by #26
Closed

Comments

@HeavyMedl
Copy link
Collaborator

We experience a lot of fallout from changes to the NPM initializer. Occasionally when consumers scaffold a template with the initializer, their project template will break from some minor change. For example, we recently bumped @rei/cedar to 15. This major change renamed an asset we referenced in one of the templates, resulting in a build time error.

At a minimum, we should write an integration test that scaffolds and builds each template type. This will ensure changes to the initializer don't break downstream.

Once written, we should trigger these integration tests on remote push events with GitHub Actions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant