I often have many different reference folders open in my VS Code workspace, but I don't necessarily want to scan all of those for VectorCAST artifacts. In some cases, I really don't want to scan those folders -- I have a bunch of legacy and out-of-date experiments that clog the log with extra information. Others may have a repository with test artifacts from multiple development teams, but I only want to focus on the tests from my team.
Scanning the extra folders takes a bit more time on each launch/restart of VS Code, and if there are errors then the logs and pop-up notifications are a little distracting. My instinct is to try to adjust settings to avoid the extra output, but I don't think TestExplorer currently provides that.
It would be nice if the extension either provided exclusion patterns ("don't scan these folders"), or some type of "use opt-in logic" setting, where the default logic of scanning everything in the workspace would be reversed: The default would be to scan nothing and only designated ("opt-in") folders are scanned.
For example:
- Set "use opt-in"
- Designate folders matching "**/unitTests" for scanning, which is a pattern I know I've only used with TestExplorer. (.gitignore would be a good reference for a well-known format for specifying these globbing patterns.)
- TestExplorer only scans folders matching the "opt-in" pattern(s)
I often have many different reference folders open in my VS Code workspace, but I don't necessarily want to scan all of those for VectorCAST artifacts. In some cases, I really don't want to scan those folders -- I have a bunch of legacy and out-of-date experiments that clog the log with extra information. Others may have a repository with test artifacts from multiple development teams, but I only want to focus on the tests from my team.
Scanning the extra folders takes a bit more time on each launch/restart of VS Code, and if there are errors then the logs and pop-up notifications are a little distracting. My instinct is to try to adjust settings to avoid the extra output, but I don't think TestExplorer currently provides that.
It would be nice if the extension either provided exclusion patterns ("don't scan these folders"), or some type of "use opt-in logic" setting, where the default logic of scanning everything in the workspace would be reversed: The default would be to scan nothing and only designated ("opt-in") folders are scanned.
For example: