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
{{ message }}
This repository has been archived by the owner on May 6, 2024. It is now read-only.
Right now when there's a selenium failure, we sometimes get a failing unit test, but we always get a resulting artifact.
It would be useful, at the very least, to show artifacts bundled as part of each job (maybe click to expand) on the overview. We could replace the artifact list with this (not on the dedicated tab).
On the dedicated tab we should annotate with which job its from.
Additionally, it probably makes sense at this stage to pull out a dedicated test details page, both per build and per project.
Per project should include test history (e.g. flakiness)
Per build should additionally include relevant artifacts to that job, since they could be related to the failure
The text was updated successfully, but these errors were encountered:
dcramer
changed the title
Pull in artifact links on failures
Improve failures user experience
Dec 8, 2017
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Right now when there's a selenium failure, we sometimes get a failing unit test, but we always get a resulting artifact.
It would be useful, at the very least, to show artifacts bundled as part of each job (maybe click to expand) on the overview. We could replace the artifact list with this (not on the dedicated tab).
On the dedicated tab we should annotate with which job its from.
Additionally, it probably makes sense at this stage to pull out a dedicated test details page, both per build and per project.
The text was updated successfully, but these errors were encountered: