rcasia / neotest-java

neotest-java Neotest adapter for Java, using JUnit . ⭐ Features • ✅ **Maven & Gradle** - Full support for both build systems (Groovy & Kotlin DSL) • ✅ **Multi-module projects** - Automatic detection and per-module test execution • ✅ **JUnit 5 (Jupiter)** - Support for , , , nested tests • ✅ **JUnit Platform 1.10.x & 6.x** - Compatible with both legacy and latest versions • ✅ **Spring Framework** - Auto-loads , , and files • ✅ **Debugging with nvim-dap** - Full integration with breakpoints, JDWP, and DAP REPL output • ✅ **Incremental compilation** - Smart compilation of only changed files via nvim-jdtls • ✅ **Automatic classpath management** - Retrieves runtime and test classpaths from LSP • ✅ **JUnit JAR management** - Automatic installation, version detection, and upgrade prompts • ✅ **Health check** - Comprehensive diagnostics with > Check ROADMAP.md to see what's coming! 📦 Installation Prerequisites • **Neovim 0.10.4+** • **nvim-treesitter** with Java parser: • **nvim-jdtls** - Language server for Java • **nvim-dap** - For debugging support (optional) Setup with lazy.nvim JUnit JAR Installation After setting up the plugin, run: This will automatically download and verify the JUnit Platform Console Standalone JAR from Maven Central with SHA-256 checksum verification. > [!TIP] > The plugin will detect if you have an older JUnit version installed and prompt you to upgrade to the latest version. ⚙️ Configuration All configuration options are optional. Pass them to : Options | Option | Type | Default | Description | |-------------------------------|------------|------------------------------------------------------------|-----------------------------------------------------------------------------| | | | | Path to JUnit Platform Console Standalone JAR | | | | | Additional JVM arguments for test execution | | | | | Enable incremental compilation (recompile only changed files) | | | | | Disable notifications about available JUnit updates | | | | | Regex patterns for test class names (classes must match at least one pattern)| ⚠️ Troubleshooting Spring Tests Failing with "parameter name information not available" If you're running Spring tests that use reflection (e.g., , ) and encounter errors like: **Solution:** Configure the JDTLS compiler to preserve parameter names in bytecode by adding the following to your project's file: If the directory doesn't exist, create it in your project root: After adding this setting, restart your LSP server ( ) and run your tests again. 🤝 Contributing Contributions are welcome! Please feel free to: • 🐛 Report bugs and issues • 💡 Suggest new features or improvements • 🔧 Submit pull requests See CONTRIBUTING.md for guidelines. ✨ Acknowledgements Thanks to all contributors who have helped improve this project!