Skip to content

Comments

Gradle projects should prefer test class name as NB testsuite name#8879

Merged
mbien merged 1 commit intoapache:masterfrom
wrprice:issue8878
Oct 2, 2025
Merged

Gradle projects should prefer test class name as NB testsuite name#8879
mbien merged 1 commit intoapache:masterfrom
wrprice:issue8878

Conversation

@wrprice
Copy link
Contributor

@wrprice wrprice commented Oct 1, 2025

Java test support for Gradle was favoring the Gradle test suite name over the test class name, but NB expects that test suites are class names. In the Gradle model, the suite name can be a method name within the test class, or even a Gradle task name (when a test class is absent for the event).

fixes #8878


^Add meaningful description above

Click to collapse/expand PR instructions

By opening a pull request you confirm that, unless explicitly stated otherwise, the changes -

  • are all your own work, and you have the right to contribute them.
  • are contributed solely under the terms and conditions of the Apache License 2.0 (see section 5 of the license for more information).

Please make sure (eg. git log) that all commits have a valid name and email address for you in the Author field.

If you're a first time contributor, see the Contributing guidelines for more information.

If you're a committer, please label the PR before pressing "Create pull request" so that the right test jobs can run.

PR approval and merge checklist:

  1. Was this PR correctly labeled, did the right tests run? When did they run?
  2. Is this PR squashed?
  3. Are author name / email address correct? Are co-authors correctly listed? Do the commit messages need updates?
  4. Does the PR title and description still fit after the Nth iteration? Is the description sufficient to appear in the release notes?

If this PR targets the delivery branch: don't merge. (full wiki article)

@wrprice wrprice force-pushed the issue8878 branch 2 times, most recently from cdc0ed6 to 4e8e013 Compare October 1, 2025 14:46
@mbien mbien added the Gradle [ci] enable "build tools" tests label Oct 1, 2025
@mbien mbien added this to the NB28 milestone Oct 1, 2025
@apache apache locked and limited conversation to collaborators Oct 1, 2025
@apache apache unlocked this conversation Oct 1, 2025
@wrprice
Copy link
Contributor Author

wrprice commented Oct 1, 2025

@mbien I noticed the Java modules checks didn't run, but maybe they should because the change is in java/gradle.test/** ?

@mbien mbien added the Java [ci] enable extra Java tests (java.completion, java.source.base, java.hints, refactoring.java, form) label Oct 1, 2025
@mbien
Copy link
Member

mbien commented Oct 1, 2025

@wrprice my mistake. I set the labels before even looking at the code since i was busy doing something else. Next run (e.g next pr sync, rebase etc) should have the java job too. Good catch!

@mbien mbien requested review from lkishalmi and sdedic October 1, 2025 23:01
Copy link
Contributor

@lkishalmi lkishalmi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@apache apache locked and limited conversation to collaborators Oct 1, 2025
@apache apache unlocked this conversation Oct 1, 2025
@wrprice
Copy link
Contributor Author

wrprice commented Oct 2, 2025

Force-pushed to trigger workflows, no changes.

@mbien
Copy link
Member

mbien commented Oct 2, 2025

oh. java/gradle.test didn't have any unit tests so it was never added to CI. Have to put that on my todo list. Probably for the build-tools job next to the other gradle tests.

@mbien mbien merged commit 8dea742 into apache:master Oct 2, 2025
37 checks passed
@mbien mbien mentioned this pull request Oct 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Gradle [ci] enable "build tools" tests Java [ci] enable extra Java tests (java.completion, java.source.base, java.hints, refactoring.java, form)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

JUnit @ParameterizedTest in Gradle project not handled correctly by o.n.m.gsf.testrunner

3 participants