trinodb/trino

Migrate JDBC tests from testng to JUnit

Open

#27,600 opened on Dec 10, 2025

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Java (2,678 forks)batch import
good first issuejdbctest

Repository metrics

Stars
 (9,113 stars)
PR merge metrics
 (Avg merge 6d 3h) (251 merged PRs in 30d)

Description

Remove testng dependency from trino-jdbc, trino-test-jdbc-compatibility-old-driver, trino-test-jdbc-compatibility-old-server. Migrate remaining tests to JUnit.

These modules may or may not be possible to update separately.

Contributor guide

Research direction
Examine the pom.xml files for testng dependencies, then migrate test classes step by step from testng to JUnit, ensuring all tests pass.
Tech stack
java
Domain
testing
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaMavenJUnit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70