We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I would like to be able to see why a test triggers a retry attempt. Specifically what error triggered it.
So I know what the issue in my code is and to rule out flaky tests.
I want to be able to see this error when testing the code in Github via Github actions. Running component tests
The text was updated successfully, but these errors were encountered:
I see that the label E2E has been added, I encounter this using component testing
Sorry, something went wrong.
No branches or pull requests
What would you like?
I would like to be able to see why a test triggers a retry attempt. Specifically what error triggered it.
Why is this needed?
So I know what the issue in my code is and to rule out flaky tests.
Other
I want to be able to see this error when testing the code in Github via Github actions.
Running component tests
The text was updated successfully, but these errors were encountered: