You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First at all, thank you for your contribution, Typescript & Playwright is very new with me, but with your project is very helpful for newbie like me.
In the current logic, the console log displays all actions invoked through logger.info. However, when running tests in parallel mode, it becomes challenging to identify which test (or test suite) a specific log entry corresponds to.
Additionally, have you tested the case with data-driven scenarios? It seems that if tests are run in data-driven mode, the logger only logs for the first run, but does not log correctly for subsequent iterations.
The text was updated successfully, but these errors were encountered:
First at all, thank you for your contribution, Typescript & Playwright is very new with me, but with your project is very helpful for newbie like me.
In the current logic, the console log displays all actions invoked through logger.info. However, when running tests in parallel mode, it becomes challenging to identify which test (or test suite) a specific log entry corresponds to.
Additionally, have you tested the case with data-driven scenarios? It seems that if tests are run in data-driven mode, the logger only logs for the first run, but does not log correctly for subsequent iterations.
The text was updated successfully, but these errors were encountered: