Andrey Meshkov
Andrey Meshkov
Well, you can't set a breakpoint inside the test because it's being run in a separate process. You may try adding some console.log's in the test, but don't forget to...
Could it be a bug in QUint itself? Try adding QUint callbacks manually on your test page and check it in the browser.
https://api.qunitjs.com/callbacks/QUnit.testDone/
Try reproducing this by running tests in the browser without using node-qunit-puppeteer at all
There's one more thing you can try -- set `QUnit.config.testTimeout` to a smaller value - at least you'll easily figure out which test times out.
Well, I don't say it will solve the issue, but at least this test should be printed as failed in the node-qunit-puppeteer output. So far, I am out of ideas...
@afridlund85 wouldn't it be better to have it solved in the QUnit test suite with something like [this](https://api.qunitjs.com/config/testTimeout/)?
We're working on it. There are some issues with the API at the moment though, it just does not work, but at some point in the future Apple will fix...
Why can't we simply mock it as noop function using existing scriptlets?
This is super strange, in theory sendBeacon is supposed to be "call & forget" type of function