trinodb/trino

Add test coverage for blackhole connector

Open

#18,482 opened on Aug 1, 2023

View on GitHubContributor guide
 (6 comments) (0 reactions) (1 assignee)Java (2,678 forks)batch import
good first issuetest

Repository metrics

Stars
 (9,113 stars)
PR merge metrics
 (Avg merge 5d 9h) (306 merged PRs in 30d)

Description

During work on this PR https://github.com/trinodb/trino/pull/18016, noticed that test coverage is pretty small. I think we could refactor current Smoke test to be more consistent with BaseConnectorSmokeTest. And think about BaseConnectorTest

Contributor guide

Research direction
Look at existing BlackholeConnectorSmokeTest and compare with BaseConnectorSmokeTest to identify gaps and refactor accordingly.
Tech stack
java
Domain
backend
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
JavaJUnitTrino testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70