<p dir="auto">It's really hard to see what tests failed across different runs, especially if you don't have access to Jenkins (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="117637019" data-permission-text="Title is private" data-url="https://github.com/kubernetes/kubernetes/issues/17443" data-hovercard-type="issue" data-hovercard-url="/kubernetes/kubernetes/issues/17443/hovercard" href="https://github.com/kubernetes/kubernetes/issues/17443">#17443</a>).</p>
<p dir="auto">Right now visibility is the biggest problem we have with e2e tests. We have too many jenkins jobs to keep track of test history for each one manually, and with test filters becoming increasingly targeted, there is no easy way to know what job a particular test is running in. Moreover, because test filters are shared across jobs, changing them can result in a set of tests that <em>should</em> be running on a particular provider/branch/job becoming silently disabled and no one is the wiser, as the test still looks green.</p>
<p dir="auto">Case in point, filter updates caused reboot tests to be skipped on <a href="http://kubekins.dls.corp.google.com/view/GKE/job/kubernetes-e2e-gke-ci-reboot/" rel="nofollow">gke-ci-reboot</a>. So the job is green but it isn't even testing what it's meant to.</p>
<p dir="auto">In order to avoid this kind of confusion and get proper visibility into what tests are running, it would be immensely helpful to have a single test dashboard that aggregates latest test results across all jobs for every defined e2e test in one big grid. Ideally it would also make results viewable by provider (GCE, GKE) and release name.</p>