trinodb/trino

Migrate JDBC tests from testng to JUnit

Open

#27600 opened on Dec 10, 2025

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

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

Tech stack
java
Domain
backendtesting
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
JavaJUnitTrino JDBC modules
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
Examine the three modules (trino jdbc, trino test jdbc compatibility old driver, trino test jdbc compatibility old server) to identify all TestNG imports and annotations. Replace them with JUnit 5 equivalents, update build configuration (pom.xml) to remove testng dependency, and ensure tests pass. Refer to issue comments for any discussed complications or guidance from maintainers.