-
Notifications
You must be signed in to change notification settings - Fork 72
chore: refactor testing infrastructure #463
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
Conversation
I was glad I could use a vim macro to do this 😅 |
Up for discussion: running the tests pre-commit and pre-push seems a little bit too much. Shall we remove pre-push? |
@czosel agree with you, we can remove pre-push |
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.
not sure, but seems to have some problems with the coverage + need to fix automatically files on each commit
* extract jest config into jest.config.js * run eslint using jest-runner-eslint * rename "lint" script to "fix" because it includes --fix * remove "cover" script, coverage can still be tested locally with `COVERAGE=1 npm test` * add eslint-plugin-jest * remove some redundant tests * refactor some tests using it.each * remove pre-push test run
@ichiriac The pre-push script is now removed 👍 |
@ichiriac let me know if there are any more open questions - would be nice if we can get this merged before we get merge conflicts. |
@czosel you're right, it's ok for me |
COVERAGE=1 npm test