enhancement: syncronization with maven #1470

Activity

1. Sheng Chen (jdneo)

   added

   enhancement

   on Aug 16, 2022
2. jdneo commented on Aug 16, 2022

   

   Sheng Chen (jdneo)

   on Aug 16, 2022

   Member

   More actions

   Thank you for your feedback.

   So for now, what kind of configurations you are using in java.test.conig setting?
3. github-actions commented on Nov 12, 2025

   

   github-actionsBot

   on Nov 12, 2025 – with GitHub Actions

   More actions

   Hi Ernst Reissner (@Reissner), I'm an AI Support assistant here to help with your issue. While the team reviews your request, I wanted to provide some possible tips and documentation that might help you in the meantime.

   Current Status

   There is no built-in way to automatically read Maven Surefire settings (properties or include/exclude patterns) from your pom into VS Code’s Java Test Runner. You must manually mirror any configurations in your settings.json.

   Workarounds

   • Use the java.test.config settings to specify include/exclude patterns. For example:

     "java.test.config": {
       "include": ["**/*Test.java"],
       "exclude": ["**/integration/**"]
     }

   • Leverage the default property of a test configuration to avoid repeatedly selecting the same config when you hit Run/Debug (see below).

   References

   • Always use test configuration or make it configurable

     • Discusses using a default field in your test config so VS Code picks it automatically even when using the Run/Debug shortcuts.
     • URL: Always use test configuration or make it configurable #264 (comment)

   • Run a test with a particular maven profile

     • Explains how the Test Runner asks the Java Language Server (m2e) for classpath information based on your Maven import/profiles.
     • URL: Run a test with a particular maven profile #1635 (comment)

   Other references with low confidence

   • Expose “New Maven Module” command to Java Projects view

     • Unrelated to test runner sync.
     • URL: Expose "New Maven Module" command to Java Projects view vscode-maven#1019

   • Support publishing pre-release versions

     • Unrelated to test execution or discovery.
     • URL: Support publishing pre-release versions redhat-developer/vscode-java#2285 (comment)

   The team will respond to your issue shortly. I hope these suggestions are helpful in the meantime. If this comment helped you, please give it a 👍. If the suggestion was not helpful or incorrect, please give it a 👎. Your feedback helps us improve!
4. github-actions

   added

   ai-triaged

   maven

   test-discovery

   on Nov 12, 2025
5. covenant-17 commented on Aug 21, 2026

   

   Maxim Korolev (covenant-17)

   on Aug 21, 2026

   More actions

   Hello! I ran into a similar problem and ended up making a small extension for it.

   It watches Maven Surefire/Failsafe reports and shows the results in VS Code, so Maven stays the actual test runner.

   GitHub: https://github.com/covenant-17/maven-test-explorer-bridge
   VS Code Marketplace: https://marketplace.visualstudio.com/items?itemName=covenant-17.maven-test-explorer-bridge

   It's a slightly different approach from syncing Java Test Runner with Surefire, but maybe it could be useful for your case too.