Coverage For Stable Endpoints, Over Time

Updated on 21 May, 2020

Below shows the testing coverage for stable Kubernetes endpoints (where coverage is defined as the percentage of kubernetes endpoints hit by at least one test during an e2e test suite run). We show coverage for both standard and conformance tests. The data includes the last 4 releases, from 1.15 to 1.18, along with the latest test run for 1.19.

The current goal, as reflected in the y-axis, is to have at least 50% of kubernetes endpoints hit by tests.

We make a distinction in conformance coverage for eligible endpoints, where eligible is defined as any endpoint that wouldn't break the guidelines in Writing Good Conformance Tests.

Click on any data point to see that release's coverage in depth
0 5 10 15 20 25 30 35 40 45 50 percent 19 Jun, 19 29 Sep, 19 29 Jan, 20 29 Mar, 20 05 Jun, 20 1.15 1.16 1.17 1.18 1.19 +32 +5.17% +32 +6.44% +1 -0.5% +13 +2.64% +8 +1.17% +9 +1.64% +9 +2.03% +7 +1.7%

% of all stable endpoints covered by tests

% of eligible stable endpoints covered by conformance tests

% of all stable endpoints covered by conformance tests

1.19.0 In Depth

Data from an e2e test suite run, from 2020-05-21
stable beta alpha core apis admissionregistration apiextensions apiregistration apps auditregistration authentication authorization autoscaling batch certificates coordination discovery events extensions flowcontrolApiserver networking node policy rbacAuthorization scheduling settings storage logs version admissionregistration apiextensions apiregistration authentication authorization autoscaling batch certificates coordination discovery events extensions networking node policy rbacAuthorization scheduling storage auditregistration batch flowcontrolApiserver node rbacAuthorization scheduling settings storage

Coverage

  • 795 total endpoints
  • 29.94% tested (238 endpoints)
  • 21.51% conformance tested (171 endpoints)