Report test execution progress by JaroslavTulach · Pull Request #14720 · enso-org/enso

JaroslavTulach · 2026-02-03T15:56:52Z

Pull Request Description

initial draft of Make tests part of Enso projects #9039
uses Test Reporting API to report some progress of test execution

the progress is captured by NetBeans infrastructure and displayed in NetBeans IDE (as well as IGV)
next step: get this working also in VSCode via the same infrastructure (provided by Support for visualizing test results in VSCode extension over LSP. apache/netbeans#2766)

Important Notes

Checklist

Please ensure that the following checklist has been satisfied before submitting the PR:

The documentation has been updated, if necessary.
Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
All code follows the
Scala,
Java,
TypeScript,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
Unit tests have been written where possible.
If meaningful changes were made to logic or tests affecting Enso Cloud integration in the libraries,
or the Snowflake database integration, a run of the Extra Tests has been scheduled.
- If applicable, it is suggested to paste a link to a successful run of the Extra Tests.

…est execution to VSCode

JaroslavTulach · 2026-02-04T17:26:37Z

tools/enso4igv/src/main/java/org/enso/tools/enso4igv/enso/EnsoActionProvider.java

+                var ts = new TestSuite("Chunk of tests");
+                var tc = new Testcase("Dummy test", "Simple type", session);
+                var fail = new Testcase("Fail test", "Simple type", session);
+                fail.setStatus(Status.FAILED);


These messages are sufficient to display test results in NetBeans

however in VSCode we see just a torso

what needs to be sent? Let's put breakpoint to TestResultDisplayHandler.Spi methods and mimic the same messages as are sent by the Groovy support: