junit test run

[maxandersen]

how hard would it be to make run test working on unit classes?

 @Test
    public void testParse() {
...

in a java project with unit "run test" shows up ...would be great if did that too with Vscode-java

[maxandersen]

@fbricon any idea?

[fbricon]

I don't see why it wouldn't work. But https://github.com/microsoft/vscode-java-test is responsible for running tests, not sure why it doesn't pick it up, the fix might need to be done there (@jdneo ?). Do you have a sample script to share?

[maxandersen]

just any simple test class with junit annotations on them.

///usr/bin/env jbang "$0" "$@" ; exit $?

//DEPS org.junit.jupiter:junit-jupiter-engine:5.12.2
//DEPS org.junit.platform:junit-platform-console:1.12.2
//DEPS org.assertj:assertj-core:3.27.3


import static org.assertj.core.api.Assertions.assertThat;

import org.junit.jupiter.api.Test;
import org.junit.platform.console.ConsoleLauncher;

public class consoleTests {

    // Define each Unit test here and run them separately in the IDE
    @Test
    public void testPass() {
        assertThat(2+2).isEqualTo(4);
    }   

    @Test
    public void testFail() {
        assertThat(2+2).isEqualTo(42);
    }   
}

[maxandersen]

just to answer my own question - issue is that junit filters out all jars - only scans directories.

thats...unfortunate :/

[maxandersen]

well here is a minimal "hack":

ConsoleLauncher.main( "execute", "--scan-class-path", "-cp", System.getProperty("java.class.path")); 

or if wanna avoid scanning all jars on claspath:

///usr/bin/env jbang "$0" "$@" ; exit $?
package wonka;

//DEPS org.junit.jupiter:junit-jupiter-engine:5.12.2
//DEPS org.junit.platform:junit-platform-console:1.12.2
//DEPS org.assertj:assertj-core:3.27.3


import static org.assertj.core.api.Assertions.assertThat;

import java.io.File;
import java.util.Arrays;

import org.junit.jupiter.api.Test;
import org.junit.platform.console.ConsoleLauncher;

public class consoleTests {

    // Define each Unit test here and run them separately in the IDE
    @Test
    public void testPass() {
        assertThat(2+2).isEqualTo(4);
    }   

    @Test
    public void testFail() {
        assertThat(2+2).isEqualTo(42);
    }   

    // Run all Unit tests with JBang with ./calculator.java
    public static void main(final String... args) {
        String jarsList = Arrays.stream(System.getProperty("java.class.path").split(File.pathSeparator))
        .filter(path -> path.contains("/cache/jars/"))
        .reduce((a, b) -> a + File.pathSeparator + b)
        .orElse("");

        ConsoleLauncher.main( "execute", "--scan-class-path", "-cp", jarsList); 
    }
}

I might simply just do the full scan one by default as its a one liner - and document the more fine tuned one for those who have too big a project :)