Repository navigation
[Proposal]: Open source the full MySQL test suite and QA tooling, not only MTR #156
Description
Pre-flight Checklist
- I have searched existing GitHub issues and did not find a duplicate proposal.
- I have removed or redacted sensitive information.
Primary Contact Name
Adam Levin
Primary Contact Email
Company / Organization
VillageSQL
Role
Product
Additional Authors / Contributors
Oracle publishes the MySQL Test Framework (MTR), but part of the testing that qualifies a MySQL release is not in the public source tree. The public mysql-test-run.pl loads code from an internal/ directory that the tree does not contain, and the release test collections run suites such as nist, i_innodb, i_rpl, and i_binlog that are not in the tree. This issue requests that Oracle open source the test suites, harnesses, and QA tools that are used to qualify a Community Server release, so that contributors, distributions, and downstream builds can run the same tests and reproduce Oracle's results. This would lead to better testing and higher quality contributions from the community.
Component
Server
Target Release (Optional)
No response
Roadmap Section
Extensibility/Ecosystem
Related Issues / Pull Requests / References (Optional)
No response
Executive Summary
Oracle publishes the MySQL Test Framework (MTR), but part of the testing that qualifies a MySQL release is not in the public source tree. The public mysql-test-run.pl loads code from an internal/ directory that the tree does not contain, and the release test collections run suites such as nist, i_innodb, i_rpl, and i_binlog that are not in the tree. This issue requests that Oracle open source the test suites, harnesses, and QA tools that are used to qualify a Community Server release, so that contributors, distributions, and downstream builds can run the same tests and reproduce Oracle's results. This would lead to better testing and higher quality contributions from the community.
User / Developer Stories
No response
Proposed Scope
No response
Out of Scope / Future Work
No response
References
No response
Functional Requirements
No response
Non-functional Requirements
No response
Impact Areas
- SQL syntax or statements
- Configuration options or system variables
- Command-line options or utilities
- User-visible behavior
- Observability
- Security or privilege model
- Protocol or replication behavior
- Upgrade / downgrade compatibility
- Performance or resource usage
- Files, persistence, or metadata formats
- APIs or internal interfaces
- Testing or QA coverage needs
Summary of the Approach
No response
User Interface
No response
Configuration / Knobs
No response
Observability
No response
User Procedure
No response
Security Considerations
No response
Compatibility and Behavior Changes
No response
Block Diagram
No response
Interface Specification
No response
Proposed Implementation Plan
No response
QA Notes
No response
Activity