Edwin Takahashi

Bonus: other tools and reporters for Jest are noted here: https://github.com/jest-community/awesome-jest#reporters

After spending some time investigating this, I have made the following findings: **Jest Circus & Allure incompatibility** - Jest v27 uses `jest-circus` as the default test runner which is incompatible...

It looks like WooCommerce uses Jest 25 for their [core API tests](https://github.com/woocommerce/woocommerce/blob/5becf47d6023c6724839fae83900da1ef3c1b257/packages/js/api-core-tests/package.json) which still uses `jest-jasmine` for the default test runner and hence has no issues with Allure.

As noted in [this comment](pciE2j-1lQ-p2#comment-1140) I have spent about 5 hours exploring the first option **explore [allure-framework/allure-js](https://href.li/?https://github.com/allure-framework/allure-js) to see if it offers an out-of-the-box solution.**. The scope of the task...

Arose as part of Jetpack testing of https://github.com/Automattic/jetpack/pull/32769. p8oabR-1kS-p2

@jeherve Sorry for late response, it seems @cuemarie narrowed it down to Firefox only - which makes sense, as I only use Firefox. Apologies for not noting this fact.

> Starting sometime Sept 19th, the invite URL no longer has environment-specific base URLs and does not need to be adjusted Interesting. I wonder which backend team made this change...

@youbrokesomething I ran some manual checks and while the URL structure is different, I think we can still make this work - just might need to do some additional parsing...

📌 REPRODUCTION RESULTS Tested on Simple – reproduced Tested on Atomic – reproduced Replicable outside of Dotcom – not tested 📌 FINDINGS/SCREENSHOTS/VIDEO **AT** - video showing part of the reproduction...