-
-
Notifications
You must be signed in to change notification settings - Fork 836
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
feat(jest): mithril component testing #3679
Conversation
Signed-off-by: Sami Mazouz <[email protected]>
Signed-off-by: Sami Mazouz <[email protected]>
Signed-off-by: Sami Mazouz <[email protected]>
7783ea2
to
f043035
Compare
baf54c3
to
c229fa6
Compare
Signed-off-by: Sami Mazouz <[email protected]>
Signed-off-by: Sami Mazouz <[email protected]>
c229fa6
to
a6bdb2a
Compare
Signed-off-by: Sami Mazouz <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is awesome!!!
Is testing supported in CI? I'm not seeing corresponding jobs in https://github.com/flarum/framework/actions/runs/3456520912/jobs/5769312494 |
We can look into it after it's merged (flarum/action-build#12) I don't remember if I tested the CI changes or not. |
# Conflicts: # js-packages/jest-config/README.md # js-packages/jest-config/package.json # js-packages/jest-config/setup-env.js # yarn.lock
Changes proposed in this pull request:
This is part two of adding jest testing. It makes the necessary changes to be able to test component behavior.
Reviewers should focus on:
Part one is here: #3678
Necessity
Confirmed
composer test
).Required changes: