cockroachdb / cockroachdb/cockroach
sql, test: identify tests which frequently catch regressions post-merge
Open
A-testing
C-enhancement
T-sql-foundations
- Dominant language
- Go
- Stars
- 32.5k
- Forks
- 4.1k
- PR merge metrics
- PR metrics pending
Description
## Summary
Can we reduce the number of issues which are caught during post-merge testing by analyzing which tests most frequently catch these issues and considering moving them (or a key element from them) into the CI testing that runs against each PR?
## Details
Epic: CRDB-60540
Jira issue: CRDB-60553
Contributor guide
Assessment
This issue has not been assessed yet.