Extension Version
prerelease/other (please specify in the description)
OpenEdge Version
12.8
Bug Description
In a multi-root workspace, with separate projects for test ("unittests"), framework and application logic ("backendproject") development, the coverage indicators are not applied to code in the application logic project. The unit test themselves are decorated appropriately.
There are many lines in the ABLUnit output like thje below. The modules referred are for programs that are in the application logic (or framework) project.
2026-05-08 12:11:33.551 [debug] [ABLProfileJson.addLineSummary (extension.js:10186:13)] could not find module 388 with line 0 (uri=c:\CODE\UnitTests\temp\prof_2.out)
2026-05-08 12:11:33.551 [debug] [ABLProfileJson.addLineSummary (extension.js:10186:13)] could not find module 410 with line 0 (uri=c:\CODE\UnitTests\temp\prof_2.out)
2026-05-08 12:11:33.551 [debug] [ABLProfileJson.addLineSummary (extension.js:10186:13)] could not find module 684 with line 0 (uri=c:\CODE\UnitTests\temp\prof_2.out)
2026-05-08 12:11:33.551 [debug] [ABLProfileJson.addLineSummary (extension.js:10186:13)] could not find module 433 with line 0 (uri=c:\CODE\UnitTests\temp\prof_2.out)
There are also references to programs that are in PROPATH but not in the code-workspace.
I suspect that a fix for this would involve being able to specify referenced projects from the workspace, as part of the ablunit-test-profile.json, similar to what has been done for the ABL extension w.r.t debugging.
Extension version: 1.4.39
Extension Version
prerelease/other (please specify in the description)
OpenEdge Version
12.8
Bug Description
In a multi-root workspace, with separate projects for test ("unittests"), framework and application logic ("backendproject") development, the coverage indicators are not applied to code in the application logic project. The unit test themselves are decorated appropriately.
There are many lines in the ABLUnit output like thje below. The modules referred are for programs that are in the application logic (or framework) project.
There are also references to programs that are in PROPATH but not in the code-workspace.
I suspect that a fix for this would involve being able to specify referenced projects from the workspace, as part of the ablunit-test-profile.json, similar to what has been done for the ABL extension w.r.t debugging.
Extension version: 1.4.39