-
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
Reporting Async Test Fails #1060
Comments
What happens if you run the async test via jest CLI directly (without wallaby)? |
Just tried your test with the plain jest CLI without wallaby, it("Not Reporting Async Fails", (done) => {
setTimeout(() => {
expect(true).toBe(false);
done();
}, 100);
}); and I'm getting the same results:
So it looks like it's just the way jest works. |
Thanks Artem - Jest is just taking an age to run via the CLI for me, otherwise I'd have posted the result. That's a bit of a pain, guess a bug that needs raising with Jest. Is that something you want me to do? |
Looks like there's an opened issue for it the Jest repo: jestjs/jest#2059. There seem to be some promise/wrapper based workarounds suggested. |
Also this one jestjs/jest#2685 |
Issue description or question
When running an async test, it seems that Wallaby isn't correctly reporting the failure. I don't know if this is a jest/jasmine specific issue or not. Looking at the cases below:
This correctly reports the error as
If I wrap this up as an Async test however:
then I get a much less helpful error, which makes tracking the actual problem down more difficult. I'm currently having to
console.log
my actual results to diagnose faults.Wallaby.js configuration file
Code editor or IDE name and version
Sublime Text v3
OS name and version
Windows 10 x64
The text was updated successfully, but these errors were encountered: