autonomousapps / autonomousapps/dependency-analysis-gradle-plugin
False positive with new style gradle test suite definition
- Dominant language
- Kotlin
- Stars
- 2.2k
- Forks
- 158
- Avg merge
- 16h 25m
- Merged PRs (30d)
- 46
Description
**Build scan link**
**Plugin version**
2.0.2
**Gradle version**
8.10.1
**JDK version**
17
**(Optional) Kotlin and Kotlin Gradle Plugin (KGP) version**
NA
**(Optional) Android Gradle Plugin (AGP) version**
NA
**(Optional) `reason` output for bugs relating to incorrect advice**
warns junit -jupiter not needed at by testImplementation, but that dep is not explicitly present, nor is it shown by depedency-tree output.
```
Advice for root project
Unused dependencies which should be removed:
testImplementation 'org junit jupiter: junit-jupiter:5.11.0'
```
**Describe the bug**
Gradle now offers "suite" concept for configuring junit with
```
testing {
suites {
configureEach {
useJunitJupiter(junitVersion)
**To Reproduce**
Steps to reproduce the behavior:
1. ... run buildHealth
**Expected behavior**
health passes
**Additional context**
Contributor guide
Research direction
Reproduce the report with Gradle 8.10.1, JDK 17, plugin 2.0.2, and the testing.suites configuration using useJunitJupiter, then run buildHealth. Trace how the plugin identifies the junit-jupiter dependency and compare that with Gradle's suite-managed dependency; done means buildHealth no longer reports the dependency as unused.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100