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

Spike: Identify TestGrid Metrics/KPIs - Test Performance #76

Closed
1 task
MichaelClifford opened this issue Jan 8, 2021 · 1 comment
Closed
1 task

Comments

@MichaelClifford
Copy link
Member

MichaelClifford commented Jan 8, 2021

As Data Scientists our first task is to convert the raw data generated by the CI processes into some meaningful KPI's/Metrics/Features (numbers) that we can track and use to describe the state or behavior of the CI process over time. One of the key elements of the CI process are the tests. Understanding the health and behavior of these test suites is critical.

Test KPI's could be things like "Test Pass Rate", "Test Run Rate", "Number of Correlated Failures with Test", etc. Sippy is currently quantifying these types of metrics and might be a good place to start looking for examples. But, as data scientists, we must admit that we are not currently subject matter experts in CI monitoring and do not know the best metrics to track for monitoring CI platform test health. As such, we need to perform a research spike and look for example KPI's used in the industry that we could collect and monitor from the TestGrid Data.

Acceptance Criteria:

  • create a markdown document of KPI's. Issue must include link to resource used to discover the metric, an explanation of why it would be useful to track, and a brief outline describing how we could generate it from our existing data sources.
@oindrillac
Copy link
Member

#177

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

2 participants