Ilya

@costa-collibra yes, you can try your previous solution. The issue will be reproduced only for case described in [Issues troubleshooting](https://github.com/reportportal/agent-js-playwright#issues-troubleshooting) section.

@sumit-gupta91 The page you shared is no longer available. Could you please provide more details?

Hi @viktor-maksymenko ! Please check [this](https://github.com/reportportal/agent-js-playwright/issues/147#issuecomment-2133777457) comment. At the moment attachments and logs are already available through the native [Playwright API](https://github.com/reportportal/agent-js-playwright?tab=readme-ov-file#attachments). We are going to implement attaching the rest of...

Hello @itz4blitz ! Since there are independent runs on different machines, Playwright does not provide an orchestration mechanism for their results to external reporters. From our side, I can offer...

Hi @Lazar-Adrian ! Thanks for your comment. I checked the Playwright feature you mentioned and it is not applicable in our case. The CLI tool [merge-reports](https://playwright.dev/docs/test-sharding#merge-reports-cli) is designed to merge...

Hello @NeginMn ! Thanks for the contribution! I'll dedicate time for that in the next sprint (next two weeks).

Hi @Invictum ! Currently, `agent-js-mocha` does not support reporting for parallel mode. We are already planning this feature for the next minor version of the agent `5.1`. Keep up to...

Hello @dnlstpnv ! We are currently working on a new mechanism for combining several launches into one, which will be used in all JS agents. ETA at the moment is...

Hello @dnlstpnv ! Sorry for the news that is not as good as you expected, but our plans are constantly changing, we need more time to prepare this huge update...

Hello @grib9544! You can fork this repo and create a PR to the `develop` branch. Update the tests if needed. Also please add a note describing your feature/fix to the...