Skip to content

sql, test: identify tests which frequently catch regressions post-merge #163966

@eric-alton

Description

@eric-alton

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-testingTesting tools and infrastructureC-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)T-sql-foundationsSQL Foundations Team (formerly SQL Schema + SQL Sessions)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions