AlessandroM92

The exact test it gets stuck I already identified via debugging node-qunit-puppeteer. Can you tell me how to debug the test itself via node-qunit-puppeteer. I did not manage to do...

Thanks to your advice I could identify the exact line after the problem occurs. The callback "TEST_START_CB" is executed for the problematic test (https://github.com/ameshkov/node-qunit-puppeteer/blob/master/index.js#L122). In my test I use the...

JFYI: I've tried different versions (2.7.1 - 2.10.1) of qunit. The problem remains. > Try adding QUint callbacks manually on your test page and check it in the browser. What...

Now it gets strange. If I log as the example suggests, ``` QUnit.testDone( function( details ) { var result = { "Module name": details.module, "Test name": details.name, "Assertions": { "Total":...

In the browser (Chrome version 84) I cannot reproduce this at all. What I can observe is that QUnit takes some seconds to finish the execution of some async tests....

The recorded execution time of the problematic test is only about 40ms. I've got other fine running tests which consume 100ms or more. Setting the testTimeout to 200ms does not...

No, I got a few async tests that fail on node-qunit-puppeteer execution from time to time. They all function similar with the `assert.async()` feature. One thing that still occurs is...

I rewrote the tests so that I do not use `assert.async()`. Instead tried to solve it with and async test callback, basic promises and await. However, the sporadic timeouts still...