kubernetes-sigs / testgrid

Kubernetes-related TestGrid projects. Currently hosts the new frontend code for TestGrid.

Testgrid

Kubernetes-related TestGrid projects. Currently hosts the new frontend code for TestGrid.

Backend code for the main TestGrid components lives in https://github.com/GoogleCloudPlatform/testgrid. See https://github.com/GoogleCloudPlatform/testgrid and https://github.com/kubernetes/test-infra/tree/master/testgrid#testgrid for additional documentation.

Community, discussion, contribution, and support

Learn how to engage with the Kubernetes community on the community page.

You can reach the maintainers of this project at:

• Slack
• Mailing List

Code of conduct

Participation in the Kubernetes community is governed by the Kubernetes Code of Conduct.

testgrid's Issues

Get the TestGrid UI deployed with equivalent functionality

tl;dr: Listing the work remaining to get the TestGrid UI MVP (this repo) to have equivalent functionality to the existing closed-source UI (at https://testgrid.k8s.io/).

(Needs the import to be done first, ref #2).

The UI is basically a collection of web components that read data from the TestGrid API and handle specific functions within the UI. The main ones are navigation (to move between pages), the index (list of dashboard groups and dashboards), summary (display recorded summary data), and the grid component (the main logic; displays recorded test history in an interactive grid).

Most of this should require some familiarity with (or willingness to learn) frontend tech (TypeScript, web components, Lit, CSS, etc.). This is not currently deployed anywhere, but once the import is complete you should be able to run it locally.

It may help to have familiarity with (or willingness to learn) Golang as well so you can work with the API.

Note: This list is a work-in-progress and is expected to update with missing items as we come across them.
All the work below should come with sufficient testing (unit and manual tests).

• Navigation component
  • (Is there any remaining work?)
• Index page
  • (Is there any remaining work?)
• Summary component
  • (Is there any remaining work?)
• Grid component
  • Update component for performance (should handle 1 million elements easily)
  • Ensure all statuses (color, icon, message) are handled
  • Properly handle grouped/nested rows
  • Properly handle all column and row headers (e.g. frozen to top and left sides, and scroll appropriately)
  • Handle right-click context menu on cells (e.g. can file a bug and open test results)
  • Add code-search link on failing rows
  • Add tooltips (on cells and column headers)
• Accessibility: Verify that components are accessible
• Style: Unify styles across all components / pages
• Documentation: Update documentation for all components
• Deploy
  • Deploy UI in a community-owned project (coordinate with K8s Infra)
  • Hook UI up to existing TestGrid API endpoint
  • Add link for new UI (separate from testgrid.k8s.io)
  • If all is well, switch testgrid.k8s.io to point to the new UI

Add TestGrid UI MVP code to this repo

Let's set this up as the canonical place for TestGrid UI development!

This should be pretty straightforward, hopefully. I think it needs:

• Import the web/ directory contents from https://github.com/GoogleCloudPlatform/testgrid.
• Update dependencies (if any) to reference https://github.com/GoogleCloudPlatform/testgrid rather than assuming it's in the same repo. (If anything, this is probably references in the UI to our protos and the API).
• Ensure we have documentation for running and testing the frontend.
• Update the documentation in https://github.com/GoogleCloudPlatform/testgrid to point here for any frontend work.
• Add a TODO issue with all the work items that are planned (or would be good) for the UI, to make it equivalent to or better than the existing UI.