-
Notifications
You must be signed in to change notification settings - Fork 157
Open
Description
Summary:
Running a test case using "Delegate to Gradle" does not produce any test results. It doesn't look like the tests actually run.
Looks like this problem was reported as a VSCode bug some time ago, but was closed there as it was an extension issue. I followed the instructions in that issue and ran the extension bisect, which pointed to the Java Test Runner extension as the problem.
The problem can be reproduced with a default Gradle project by following the steps below.
Environment:
macOS Sequoia 15.4
VSCode Version: 1.99.3 (Universal)
Extensions:
- Extension Pack for Java Version 0.29.0
- Test Runner for Java Version 0.43.1
- Gradle for Java Version 3.16.4
Steps to Reproduce:
- Open VSCode
- Create a new Java Project
- Select a Gradle Project from the options
- Select Kotlin for the DSL (I suspect the problem will occur with Groovy as well)
- Specify a new folder for the project
- Open the project folder after it has been created.
- The project will have an AppTest.java automatically created with a single test case.
- Open the AppTest.java file.
- Run the test case from the gutter. This will use the Java Test Runner by default. This will succeed, and show up as a success under the test results tab.
- Now switch to the Testing view, and change the default test runner to "Delegate to Gradle"
- Re-run the test case from the gutter. This time there won't be any indication of the test succeeding or failing or even running in the test results tab.
mamilic
Metadata
Metadata
Assignees
Labels
No labels