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

TestGrid Use Cases! #51

Closed
michelle192837 opened this issue Nov 15, 2019 · 3 comments
Closed

TestGrid Use Cases! #51

michelle192837 opened this issue Nov 15, 2019 · 3 comments

Comments

@michelle192837
Copy link
Collaborator

Continuing from good old kubernetes/test-infra#10409, this issue is open for anyone who wants to use TestGrid but is blocked on doing so while we're open-sourcing.

Add your requests/use cases here for how you'd like to use TestGrid! We'll use this to help determine how to prioritize work as we continue open-sourcing. ^^ (Feel free to look at the previous issue for inspiration, or file a separate issue with more details in addition to here!)

@RobertKielty
Copy link

RobertKielty commented Jun 22, 2020

  1. As a TestGrid user I would like to be able to group jobs that I am interested in so that I can create a dashboard of those jobs displaying cards in a responsive grid that present the following (suggested) data about each job that I am interested in.

Job Name
Job Description
Last Run

  • Test Stats
  • Actual Duration

Next Run

  • Scheduled Time

Overall Trends Color
Present the following as stacked horizontal bars of green, yellow, red

  • Last 5 runs
  • Last 10 runs
  • Last 30 runs
  1. As a Test Grid User when working with multiple jobs I would like to see the Title of the Job Page be the Job Name instead of the name of the Test Grid tab to which the Job belongs. When I am covering multiple jobs and have them open in multiple tabs at present the titles are all same which has a negative impact on the UX.

  2. As a Test Grid user I would like to be able to quickly view and compare errors when groups of tests fail on a Job, here are suggestions that could deliver on that

  • allow me to open all failed tests in Prow for a particular Job Run multiple tabs, automatically take me to the error on Prow
  • On a test grid result cell, onMouseOverEvent - popup the test error in a tool-tip, this would allow me to quickly compare error messages across a range of jobs. I want to know if the errors are the same or different.
  1. As a Test Grid User I would like to be able to easily navigate back to the source of the test that reported a test failure

  2. As a Test Grid User I would like to be able to navigate back to a status page that reported on infrastructural status at the time of the test run.

@RobertKielty
Copy link

RobertKielty commented Jun 22, 2020

There's an interesting amount of overlap between TG, Prow and Build Status the more I use these applications the better I can navigate results. The Build Status app (accessible from top right hand corner of a Prow Job result page) is very useful and probably satisfies a lot of the use cases that I specified above.

@fejta
Copy link
Contributor

fejta commented Apr 22, 2021

I'm sure we can still improve the experience but you can follow https://github.com/GoogleCloudPlatform/testgrid/tree/master/cluster/prod and https://github.com/GoogleCloudPlatform/testgrid/blob/master/standalone.md to deploy and use your own public testgrid data.

@fejta fejta closed this as completed Apr 22, 2021
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