Vitess original testcases can be devided into: unit_test, endtoend(single process), endtoend(cluster). However, vitess was designed mostly for sharding, the endtoend test is not suitable for our project, and since we modified the architecture to not support sharding, most of the test cases fail.
So we need our own end-to-end tests to:
Ensure that the SQL functionality that should work properly in wesql-scale is functioning correctly.
Understand the compatibility of wesql-scale.
The test suite should be as comprehensive as possible, and we can refer to MTR for guidance.
We can also use a test framework such as https://github.com/pingcap/mysql-tester.
Feature Description
Vitess original testcases can be devided into: unit_test, endtoend(single process), endtoend(cluster). However, vitess was designed mostly for sharding, the endtoend test is not suitable for our project, and since we modified the architecture to not support sharding, most of the test cases fail.
So we need our own end-to-end tests to:
The test suite should be as comprehensive as possible, and we can refer to MTR for guidance. We can also use a test framework such as https://github.com/pingcap/mysql-tester.