Creation of jest testing framework, along with basic integration/unit tests #509
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
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.
This pull request adds a framework for testing using Jest and Playwright for CRACO. It also includes an example integration test and several basic unit tests to demonstrate how to use the framework. While basic, these tests will fail if basic CRACO functionality fails to execute.
The Jest and Playwright combination provides a powerful testing solution for CRACO, allowing us to test our code from end-to-end and catch any potential issues early on. Additionally, the example unit tests showcase how to write effective unit tests and integrate them into our testing suite.
I have designed the framework around making it painless to add additional tests or modify/run existing ones. For example, setup.js and teardown.js handle individual test installation, package/file management, and compilation, significantly reducing the amount of boilerplate required for additional integration tests.