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

Upgrade tests to use Babel 7 #2094

Merged
merged 2 commits into from Nov 6, 2019
Merged

Conversation

andrewiggins
Copy link
Member

@andrewiggins andrewiggins commented Nov 6, 2019

I'm exploring writing a babel plugin to convert property names to enable our tests to run against the minified builds. In the process of doing that I realized that our tests still used Babel 6. This PR upgrades them to Babel 7.

@@ -0,0 +1,24 @@
module.exports = function(api) {
Copy link
Member Author

Choose a reason for hiding this comment

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

babel-loader in the karma.config.js wasn't picking up the configuration in .babelrc but did work when I changed it to a babel.config.js. 🤷‍♂

spyAll(Receiver);
spyAll(Receiver.prototype);
Copy link
Member Author

Choose a reason for hiding this comment

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

This tests failed unless I swapped the order here. Perhaps some new class transform broke the old form? 🤷‍♂

@coveralls
Copy link

Coverage Status

Coverage increased (+0.1%) to 99.892% when pulling b1fe2d8 on feat/upgrade-test-babel into f91e500 on master.

}
]
]
? [['istanbul', { include: '**/src/**/*.js' }]]
Copy link
Member

Choose a reason for hiding this comment

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

That's much better 👍

Copy link
Member

@marvinhagemeister marvinhagemeister left a comment

Choose a reason for hiding this comment

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

Really happy to see this PR 🎉 I attempted to switch to babel7 when it just came out and ran into many problems. Glad to see that they've been resolved 💯

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

3 participants