1 of 4

Gerrit Contributor Summit - November 16, 2020

UXD @Google: Delphine Carlson

UXR @Google: Marian Harbach

SWE @Google: Ben Rohlfs

Link to Data model of checks

2 of 4

Checks one line summary

3 of 4

Checks tab runs

and results

Checks tab

The checks tab is displaying check runs and check results from the latest patchset, we can select another patchset to view previous check runs and check results

RUNS

Show runs in a collapsible side panel to better use screen estate and act upon have an overview at a glance of both runs and results
Runs panel is divided in check run states

Completed
Running
Available

If we look at Check.Runs completed we can see completed runs and a colored icon of the most critical result of the run
If there are many Check runs, we can search for a specific Check.run so that we can run a specific check we are looking for
Select buttons provides a way to act upon the Check.Runs to run or stop them.

RESULTS

A check.run can produce multiple results
One run can produce multiple results and they are displayed by result category: Error, Warning and Info.

INFO: The user will typically not bother to look into this category, only for looking up

something that they are searching for. Can be used for reporting secondary metrics and analysis, or a wider range of artifacts produced by the CI system.

WARNING: A warning is something that should be read before submitting the change. The user should not ignore it, but it is also not blocking submit. It has a similar level of importance as an unresolved comment.
ERROR: An error indicates that the change must not or cannot be submitted without fixing the problem. Errors will be visualized very prominently to the user.

What users will be mostly interested in are the summary and having a quick link to see the test logs in an external tool.

Each result can be expanded and show more of the summary.

Some results may be attached to a Submit requirement, if we don’t take care of this error, this could prevent us from submitting the change.
Each result can also have a tag to provide users with categorization of results.

BUTTONS

Each result has a default button to view test logs in an external tool.

On hover, more buttons are available, for example, see an image or screenshot or download a ZIP or APK file.

4 of 4

Checks tab runs

and results