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
This is fine when the installation succeeds and the exit code is 0. But when running under xUnit.net (which does not capture the console output) and the installation fails with exit code 1, then it becomes impossibly hard to diagnose the root cause of the failure.
It would be nice to have an exception instead of a non-zero exit code.
Example
No response
Motivation
Diagnosing such issues required me to reference Playwright from source rather than using the NuGet package, putting breakpoints to figure out the actual Node.js call and run it in a console to get the actual error messages.
It would be much better to have a built-in way to extract the root cause of the failure.
The text was updated successfully, but these errors were encountered:
0xced
linked a pull request
Apr 3, 2025
that will
close
this issue
🚀 Feature Request
Ensuring that playwright is properly installed can be done by running the following code:
This is fine when the installation succeeds and the exit code is 0. But when running under xUnit.net (which does not capture the console output) and the installation fails with exit code 1, then it becomes impossibly hard to diagnose the root cause of the failure.
It would be nice to have an exception instead of a non-zero exit code.
Example
No response
Motivation
Diagnosing such issues required me to reference Playwright from source rather than using the NuGet package, putting breakpoints to figure out the actual Node.js call and run it in a console to get the actual error messages.
It would be much better to have a built-in way to extract the root cause of the failure.
The text was updated successfully, but these errors were encountered: