Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Should `suite.run()` return a promise for the test results?

See original GitHub issue

So I am bundling my test suite using rollup to run it in the browser and since v0.3.1 that works lik a treat.

However, I don’t know how to read back the test results (which tests passed, which tests failed etc). I’m trying to read all of that back via pptr. It would make sense (to me, at least) that test.run() returns a promise for some sort of result data structure.

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

2reactions

lukeedcommented, Aug 2, 2020

Hey Surma, sorry for the delay – recently I’ve been taking weekends away from the desk. Tomorrow morning I’ll publish my WIP browser layer on npm for you.

The TLDR is that suite.run used to do exactly that, but it made it near-impossible/super-unreliable to execute single-file tests (node test.js) since there’s no top-level await. You can call uvu.exec to process the queue youve built, but it writes results immediately.

Update tomorrow morning, hopefully

1reaction

hugomrdiascommented, Dec 8, 2020

Added support for uvu in playwright-test https://github.com/hugomrdias/playwright-test/releases/tag/v1.1.0 but I’m relying on the console.log output, having exec available and throwing on errors would make the integration more reliable and future proof.

Btw what’s the run entry point for? There’s a UVU_DEFER var there that could be used to manually stop the auto start for non cli runners.