Dmitry Baev
Dmitry Baev
The more generic solution would be to supply `process.env` in some sort of envelope that notifies about run start (and triggered once per worker)
> And I still do not understand why this could not be part of the formatter itself BTW what exactly do you mean by saying that?
as far as I know, formatter is executed in parent process, and have no access worker id which is only passed to child process. That's the reason we raised this...
Sounds good to me
> Would this suit your needs as well? Depends on implementation. The current issue we have is that report entries are published to system out in case you run tests...
closed via #838
All the issues will be addressed in the new Allure Cypress integration, please follow https://github.com/allure-framework/allure-js/pull/815
Usually, the reason is that test parameters aren't specified correctly to Allure. See https://allurereport.org/docs/history-and-retries/ for the details. If you struggle to get it done, please create a support request in...
Please provide additional details on the setup. Graphs work fine for [demo report](https://allure-framework.github.io/allure-demo/8/#graph)
fixed by #2229