-
Notifications
You must be signed in to change notification settings - Fork 45
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
How to run jasmine-node tests #323
Comments
Ok I was able to resolve the issue by using test-framework: jasmine and using jasmine-node@2.0.0. See also: mhevery/jasmine-node#282 Still though jasmine and jasmine-node are not the same and I might run into issues later on. |
I also run into this issue with mongoose models once the tests are run a second time:
That doesn't happen with jasmine-node --autotest |
Yep, I have only tested it with
Try setting |
Thanks for getting back to me so quickly. |
Interesting, could you please try |
That did the trick! Thank you very much. Are these options documented somewhere? You still need the repo? |
Ok, cool. Yes here is the documentation - http://wallabyjs.com/docs/config/workers.html. The issue is that by default wallaby tries to run your tests in parallel and mongoose doesn't seem to like it. |
One possible solution to still allow running your tests in parallel is perhaps using different DBs per worker. You may consider using wallaby.js bootstrap function to set up a DB for worker. |
Good suggestion and good documentation. Was not able to find that earlier somehow. I might try that at a later point. So far the tests are still running very fast in my current project. |
Awesome, then you probably don't need to bother trying to speed it up right now, but can just leave the option for later. |
No it doesn't. |
Cool, good to know, thanks for checking! |
When I try to run tests written with jasmine-node, all of jasmins core functions are not defind like spyOn or even expect.
Here is the config:
The text was updated successfully, but these errors were encountered: