Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't figure out how to see why a test failed #42

Closed
jongio opened this issue Aug 28, 2021 · 4 comments
Closed

Can't figure out how to see why a test failed #42

jongio opened this issue Aug 28, 2021 · 4 comments
Labels

Comments

@jongio
Copy link

jongio commented Aug 28, 2021

I have a failing test.

I only see the red X

I do not see the details as to why it failed.

I right clicked on all the places I could find.

I checked the outputs...

I was expecting it in the Playwright Test output window.

azsdke2e
azsdke2e2

@mxschmitt
Copy link
Member

mxschmitt commented Aug 30, 2021

Do you have a reproducible test case?

There are multiple ways to get the information from when an error gets thrown.

image

Or via the test terminal, there all the output gets shown:

image

For timeout errors, it seems currently not shown correctly - will try to find out if it's a VSC or our bug.

Linking microsoft/vscode#131898

mxschmitt added a commit that referenced this issue Aug 30, 2021
@mxschmitt mxschmitt reopened this Aug 30, 2021
@mxschmitt
Copy link
Member

Keeping it open until it was acknowledged that it got fixed.

@mxschmitt
Copy link
Member

Had a offline discussion, outcome bugs were:

  • test were retried -> fixed in ddf2054
  • debugging console was not shown after debugging tests -> fixed in 987c7e1
  • test status does not change when debugging tests -> To be discussed, probably keep it like that since we can't obtain the execution results of a test so far when debugging
  • test was shown multiple times -> waiting for a repro

@mxschmitt
Copy link
Member

Closing since the bugs were addressed. We'll create new issues for other bugs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants