🐛 [Bug] Tests not found

[PeterJudgeCW]

Extension Version

prerelease/other (please specify in the description)

OpenEdge Version

12.8

Bug Description

Tests are not being identified/provided to VSCode. The Testing view in the Activity bar is not populated even though there are tests in one of the 3 projecst being scanned.

Is there any more logging I can enable?

Extension settings

        "ablunit.suggest.annotations": true,
        "ablunit.suggest.enabled": false,
        "ablunit.suggest.events": false,
        "ablunit.suggest.methods": false,
        "ablunit.suggest.references": false,
        "ablunit.files.exclude": [
            "**/.builder/**",
            "**/.pct/**"
        ]

VSCode

Version: 1.106.2 (user setup)
Commit: 1e3c50d64110be466c0b4a45222e81d2c9352888
Date: 2025-11-19T16:56:50.023Z
Electron: 37.7.0
ElectronBuildId: 12781156
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

[kenherring]

There was a similar issue in a prerelease prior to 1.4.0, but that never got to the "activation complete" step. I'm guessing this is still related though.

Can you check the logs in Help -> Toggle Developer Tools and see if there are any errors that seem related?

[PeterJudgeZA]

I didn't really see anyhting in the developer tools (at least not that what was in the logs).
I changed the settings to "do not activate on open" and bumped up the output channel logging to debug.

There are 2 odd things to me

1. the openedge config logged is from an additional profile, which is not in currently use (the default is being used)
2. the fact that the TestSurchargeService class is found and then not found.

[kenherring]

Shot in the dark here, but can you try disabling all other extensions and see if the functionality is restored? There could be some competition going on.

I think the logging for TestSurchargeService is pretty normal. It's in the VSCode workspace, so it finds it, but then when processing it decides it's not part of the profile. Maybe there is some opportunity for performance improvement there, but it's probably not a big enough problem to invest time into until we learn otherwise.

[PeterJudgeZA]

It looks like it has to do with the 'includes' config value. It may also have to do with the fact that I have >10 projects in the workspace but my TS/JS is not strong enough to say that for a fact. I did see timeouts in the dev tools (it appears like the extensions tries to figure out the include/exclude folders on every file query).

My testing project has the following build path.

  "buildPath": [
    {
      "type": "source",
      "path": ".",
      "includes": "Consultingwerk/**,SimpleUnitTests/**",
      "xref": "../UnitTests-pct"
    },

The doesFileMatch function checks a variety of patterns. I added some debug messages to that function the show the patterns and whether it matches.

Two things stand out. Firstly, the include patterns have a relative path, which is not always correctly taken into account. The project is in UnitTests/ and only the Consultingwerk/ and SimpleUnitTests/ folders should be included.

2026-01-01 22:16:45.645 [debug] [isFileIncluded (extension.js:21874:9)] file is /home/peter/repo/<project>/UnitTests/Consultingwerk/OeraTests4/SCL3241/TestClass.cls
2026-01-01 22:16:45.646 [debug] [doesFileMatch (extension.js:21893:7)] relativePath=Consultingwerk/OeraTests4/SCL3241/TestClass.cls
2026-01-01 22:16:45.646 [debug] [doesFileMatch (extension.js:21895:9)] pattern=/home/peter/repo/<project>/UnitTests/Consultingwerk/**
2026-01-01 22:16:45.646 [debug] [doesFileMatch (extension.js:21896:9)] minimatch=false

Secondly, it seems like there are multiple passes at finding the files. In this case, the exclude patterns are also checked. They return false correctly but that's coincidental.

2026-01-01 22:16:45.644 [debug] [isFileIncluded (extension.js:21855:7)] inclded for /home/peter/repo/<project>/UnitTests/Consultingwerk/OeraTests4/SCL3241/TestClass.cls
2026-01-01 22:16:45.644 [debug] [doesFileMatch (extension.js:21893:7)] relativePath=Consultingwerk/OeraTests4/SCL3241/TestClass.cls
2026-01-01 22:16:45.644 [debug] [doesFileMatch (extension.js:21895:9)] pattern=**/*.{cls,p}
2026-01-01 22:16:45.644 [debug] [doesFileMatch (extension.js:21896:9)] minimatch=true
2026-01-01 22:16:45.644 [debug] [doesFileMatch (extension.js:21898:11)] file Consultingwerk/OeraTests4/SCL3241/TestClass.cls matches '**/*.{cls,p}'
2026-01-01 22:16:45.644 [debug] [doesFileMatch (extension.js:21893:7)] relativePath=Consultingwerk/OeraTests4/SCL3241/TestClass.cls
2026-01-01 22:16:45.644 [debug] [doesFileMatch (extension.js:21895:9)] pattern=**/.builder/**
2026-01-01 22:16:45.644 [debug] [doesFileMatch (extension.js:21896:9)] minimatch=false
2026-01-01 22:16:45.644 [debug] [doesFileMatch (extension.js:21895:9)] pattern=**/.vscode/**
2026-01-01 22:16:45.644 [debug] [doesFileMatch (extension.js:21896:9)] minimatch=false
2026-01-01 22:16:45.645 [debug] [doesFileMatch (extension.js:21895:9)] pattern=**/.pct/**
2026-01-01 22:16:45.645 [debug] [doesFileMatch (extension.js:21896:9)] minimatch=false
2026-01-01 22:16:45.645 [debug] [doesFileMatch (extension.js:21895:9)] pattern=ABL/**
2026-01-01 22:16:45.645 [debug] [doesFileMatch (extension.js:21896:9)] minimatch=false