[Feature][connector-jdbc][DB2] Optimize unit testing for DB2 in JDBC connector · apache/seatunnel#10216

2025-12-18T14:46:28.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 This issue focuses on improving and expanding unit test coverage for the DB2 case in the connector-jdbc module, consistent with the scope defined in #10210. 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. ### 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)

(1 commento) (0 reazioni) (1 assegnatario)Java (1432 fork)batch import

good first issuehelp wanted

Metriche repository

Star: (6897 star)
Metriche merge PR: (Merge medio 13g 21h) (143 PR mergiate in 30 g)

Descrizione

Search before asking

I had searched in the feature and found no similar feature requirement.

Description

This issue focuses on improving and expanding unit test coverage for the DB2 case in the connector-jdbc module, consistent with the scope defined in #10210.

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.

Usage Scenario

No response

Related issues