You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.
Is it possible to test code that is written using es6 module import statements?
For now, I'm generating a compiled version of my code under test, putting it all into one file, and testing that, however, it would be great if I could test the original code directly.
The text was updated successfully, but these errors were encountered:
Good question. I'm just used to using Buster for all my testing and ran across that obstacle while trying to test a library I was working on. Admittedly, I still haven't fully wrapped my head around the issue of testing es6 modules.
I find that I end up doing what you said - generating a bundle, sometimes even one for tests, and testing that regardless if I'm using ES6 or not, browserify or webpack, etc.
Perhaps it would be worthwhile to look into StealJS. It imports and transpiles ES6 modules natively. There's a steal-qunit package that supports testing with qunit, perhaps there could be one built for busterjs.
Is it possible to test code that is written using es6 module import statements?
For now, I'm generating a compiled version of my code under test, putting it all into one file, and testing that, however, it would be great if I could test the original code directly.
The text was updated successfully, but these errors were encountered: