[Feature][connector-jdbc] Optimize unit testing of jdbc connector code · apache/seatunnel#10210

2025-12-18T13:41:26.000Z

### Search before asking - [x] I had searched in the [feature](https://github.com/apache/seatunnel/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description ### Problem 1. 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. 2. 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. 3. 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 - [x] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)

(3 Kommentare) (1 Reaktion) (0 zugewiesene Personen)Java (1.432 Forks)batch import

good first issuehelp wanted

Repository-Metriken

Stars: (6.897 Stars)
PR-Merge-Metriken: (Durchschn. Merge 13T 21h) (143 gemergte PRs in 30 T)

Beschreibung

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