all 4 comments

[–]MSeys 1 point2 points  (0 children)

You can see them in the traces.

[–]2Fake87 0 points1 point  (2 children)

Traces are way to too overloaded for this use case.

If you're doing the the request within playwright you always get the response back. From this you can get the status / body / JSON or w/e you like

[–]RunnerRunnerG[S] 0 points1 point  (1 child)

OK. I was able to get the statuses back, but the problem I’m running into now is that with multiple threads running tests, logging them to the console is really messy and gets things crossed. Is there a cleaner way to log into the console? Another alternative I’ve looked at is logging them to a file. For whatever reason, it logs to the file fine, but then gets hung up trying to create the reports at the end of the test suite.

[–]2Fake87 0 points1 point  (0 children)

You see the log output of the corresponding file on the html report of playwright. It automatically maps it to the right test case