"WARNING: done not called!" masking real errors
See original GitHub issueI’m not getting error messages / stack traces of problems my tests may have. Instead I’m presented with the utterly useless (and easy to miss) message “WARNING: done not called!”.
I need to see what I did wrong here. Tests need to halt. This is a JavaScript error. I tried to invoke a function that doesn’t exist. My test is flawed - stop and yell!
{
foo: function(test) {
test
// Note that this should be .assert.doesntExist()
.doesntExist('.selector')
// this isn't called
.done();
}
}
Issue Analytics
- State:
- Created 10 years ago
- Comments:16 (6 by maintainers)
Top Results From Across the Web
Errors when using imgaug's augmentation. #2018 - GitHub
The solution is to ignore the warning and double-check if the augmentation method works for the masks.
Read more >Error handling - Apollo GraphQL Docs
Masking and logging errors. You can edit Apollo Server error details before they're passed to a client or reported to Apollo Studio. This...
Read more >The following objects are masked... - RStudio Community
The following objects are masked from 'package:base': intersect, setdiff, setequal, union). that is my error how to solve it , i will try...
Read more >PHP unlink() handling the exception - Stack Overflow
The proper way to do this is check that the file exists before trying to call unlink on it. If you are merely...
Read more >restore_error_handler does not restore previous errors mask
If I set 2 error handlers with differents masks, and trying to restore back my first handler by calling restore_error_handler(), ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Also having the same issue as @bowsersenior.
I’m using the following versions: DalekJS CLI Tools Version: 0.0.5 DalekJS local install: 0.0.9
Syntax errors do not entail an error in command line - see the mistake
.assert.text.to.contain('#i_am_a_textbox', 'TEXT')
in the code block below. After changing this syntax mistake to.assert.text('#i_am_a_textbox').to.contain('TEXT')
, a real error did show up in console.@SarahPAV , I solved this error by checking the correct commands. In my case I typed “screenshot” wrong so it never continues the flow until the .done()
I holpe it helps you.