[Feature][connector-jdbc] Optimize unit testing of jdbc connector code #10210
Description
Search before asking
- I had searched in the feature and found no similar feature requirement.
Description
Problem
- At present, the unit tests of connector-jdbc code basically rely on the local environment and will be turned off during the actual running of ci, which will lead to functional risks. We hope to introduce docker containers and run unit tests in the actual ci process.
- The unit test coverage of connector-jdbc code is relatively low, such as the jdbcCatalog test and jdbcDialect test. Additionally, there is a lack of boundary condition test cases. We hope to add relevant test cases.
- After completing points 1 and 2, you can transfer the unit tests in the jdbc-e2e module to connector-jdbc.
Implementation scope
| type | status | Assignees |
|---|---|---|
| mysql | ||
| oracle | ||
| pgsql | ||
| sqlserver | ||
| dameng | ||
| db2 | ||
| kingbase |
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct