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

Switch all client tests to jest #1168

Merged
merged 1 commit into from Jan 8, 2020
Merged

Switch all client tests to jest #1168

merged 1 commit into from Jan 8, 2020

Conversation

nicksellen
Copy link
Contributor

Proposed Changes

Now we have jest for frontend tests, we can remove karma. This makes the minimal changes needed to get the existing client tests to run under jest.

Built on top of #1167 so that should be merged first.

Testing Instructions

  • run the tests

Copy link
Contributor

@mrkvon mrkvon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Impressive configuration changes! That must have been challenging to make it run smoothly.

Tests work and test count matches the previous version perfectly!

What I understand, looks good to me.
Disclaimer: I don't understand a majority of changes. 🙂

So let's wait for the merge of #1167 and then i support merge.

@@ -1,9 +1,24 @@
module.exports = {
moduleNameMapper: {
'@/(.*)$': '<rootDir>/$1',
'^@/(.*)$': '<rootDir>/$1',
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😲 Whatever the stuff in this config is doing, it works!

@nicksellen nicksellen changed the base branch from webpack-client-resources to master January 8, 2020 21:52
@nicksellen nicksellen merged commit 81065ef into master Jan 8, 2020
@nicksellen nicksellen deleted the remove-karma branch January 8, 2020 22:08
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 this pull request may close these issues.

None yet

2 participants