Use "eject" as baseline in generator tests #900
Assignees
Milestone
Comments
lars-reimann
added a commit
that referenced
this issue
Feb 21, 2024
Closes #900 ### Summary of Changes * We now have only a few targeted generator tests for the runner integration, instead of having this scattered across almost all tests. * Use vitest's `toMatchFileSnapshot` to easily be able to update the expected output after changes to the code generator. Run `vitest --update` to do so.
|
🎉 This issue has been resolved in version 0.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, we include runner integration in the generator tests by default and have a few tests for the "eject" functionality. This means, changes to the runner integration code affects multiple (unrelated) test files.
It would be preferable, if we would use the "eject" functionality by default and then add a few tests targeting the generation of code for the runner integration.
The text was updated successfully, but these errors were encountered: