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

QE-147 Include error message with failed (flaky?) tests #149

Closed
Dan-DeAraujo opened this issue Mar 11, 2024 · 3 comments
Closed

QE-147 Include error message with failed (flaky?) tests #149

Dan-DeAraujo opened this issue Mar 11, 2024 · 3 comments
Assignees

Comments

@Dan-DeAraujo
Copy link

Dan-DeAraujo commented Mar 11, 2024

Would help understand test failure reason trends, and we can focus de-flaking efforts on areas of higher impact.

EG: This run failed with Error: locator.fill: Target page, context or browser has been closed; which is clearly not something we can resolve directly, but if we notice an uptick post-Playwright update, we can complain to them about it

OTOH, if we notice alot of tests failing to find locators or whatever, maybe we need better training on how to pick good ones

Not sure if we can get it for flaky tests (ie: the first run of a retried set) too, but if we can that'd be even better

@devpow112 devpow112 self-assigned this Mar 11, 2024
@devpow112 devpow112 transferred this issue from Brightspace/test-reporting-action Mar 11, 2024
@devpow112
Copy link
Contributor

Duplicate of #87.

@devpow112
Copy link
Contributor

Gonna try and send error message, file, line and column values for each test when an error occurs. For retired tests I'm just gonna send the last error for now. If we find we need all error information or something else we can explore that separately.

@devpow112 devpow112 removed their assignment May 16, 2024
@waikilee waikilee assigned waikilee and devpow112 and unassigned waikilee Jun 4, 2024
@waikilee waikilee changed the title Include error message with failed (flaky?) tests QE-147 Include error message with failed (flaky?) tests Jun 10, 2024
@devpow112
Copy link
Contributor

Moved to Jira

@devpow112 devpow112 closed this as not planned Won't fix, can't repro, duplicate, stale Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants