-
-
Notifications
You must be signed in to change notification settings - Fork 80
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
sbt not running tests #49
Comments
Have you tried this? https://github.com/lihaoyi/utest#scalajs-and-sbt You need to add some magic settings to make it work with Scala.js, which are all stuffed into a one-line bundle in the utest-js-plugin. This won't be necessary for 0.6.x, but for now you'll have to do this song & dance ^_^ |
yes, I tried all of that. I'm looking at jasmine now. |
I don't see it in your repo, but sure. Let me know if i can be of any help |
argh, I went to jasmine, which worked, but I got a stack trace during the test https://github.com/fommil/kerbal-calculator/tree/11620af869db57e1309d09097b1852a24f7e1035 Does this mean my code is pushing the limits of the scalajs compiler, or do I need to do something else? (I'm going to give utest one more try, because it would be nice to have all this code in a shared module, with all the JS stuff in a separate one... although it would be good to be able to run the tests of the shared code in the JVM and the JS if possible)
|
Looks like you're using bits of code ( |
I was able to get utest to work, finally. I'll push to my repo shortly. The confusing thing for me, which might be worth documenting, was appreciating that a single module project will be treated as a JS project which absolutely requires that one use the utest sbt plugin: there is no cross-compilation for a single module project. Now that I have a shared/js/jvm project in place I can see that the shared tests run in both the jvm module and the js module. It's a bit of a hack the way this is set up as it is effectively explicitly adding directories to the module's source directory list instead of setting up a transitive dependency structure. I'm guessing this is going to cause havoc with our ENSIME sbt plugin. I suspect the required symbolic links will bring their own problems with ENSIME. |
I've followed the tutorial and the utest README but sbt seems to ignore the tests in my (really simple) project https://github.com/fommil/kerbal-calculator/
Can you please take a look and see what I'm doing wrong? It might lead to a change to the docs.
The text was updated successfully, but these errors were encountered: