kestra-io/kestra

Add code coverage in repositories and search

Closed

#8,533 opened on Apr 25, 2025

View on GitHubContributor guide
 (7 comments) (0 reactions) (0 assignees)Java (2,579 forks)batch import
area/backendgood first issuekind/cooldown

Repository metrics

Stars
 (26,854 stars)
PR merge metrics
 (Avg merge 1d 19h) (495 merged PRs in 30d)

Description

Most of the search method use a list of parameters, but only one parameter is used during unit testing. We then don't know which parameter are really used, and if they work.

It will allow us to find a lot of bugs before it's too late.

Contributor guide

Research direction
Review the search method implementations and their unit tests to identify parameters not tested. Then set up a code coverage tool like JaCoCo and generate coverage reports to find gaps.
Tech stack
java
Domain
testing
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
JavaGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75