Cannot build test environments that were created by Manage project

[felixvanoost]

I have a set of test environments that were created within a VectorCAST Manage project (*.vcm) and am trying to configure the VectorCAST Test Explorer extension to build them. The environments show up correctly in the VS Code flash view, but I get the following error when attempting to build:

test explorer  [info]  ----------------------------------------------------------------------------------------------------
test explorer  [info]  VectorCAST Copyright (C) 1993 - 2025
test explorer  [info]  **Version 24.sp6 (11/18/24)
test explorer  [info]      Processing DEM.env
test explorer  [info]  **Environment Builder Version 24.sp6 (11/18/24)
test explorer  [info]      No preprocessor command specified; check your configuration options.
test explorer  [info]      ** ERROR: Environment Creation Failed
test explorer  [info]  ----------------------------------------------------------------------------------------------------
test explorer  [info]  clicast: '-lc env build DEM.env' returned exit code: 12
test explorer  [info]  ----------------------------------------------------------------------------------------------------
test explorer  [info]  Environment build failed, removing artifacts ...
test explorer  [info]  ----------------------------------------------------------------------------------------------------

This is because the environments are not standalone and rely on the configuration options stored in the *.vcm file.

I made a standalone environment based on a CCAST_.CFG file as described in the README, which works as expected in VS Code. I then tried adding it as an existing environment to my *.vcm project, but the test cases script (*.tst) fails to open by default when loading it in the VectorCAST GUI. This prevents me from running the environment in a CI pipeline, as the project doesn't attempt to load the test cases script and therefore no tests are run.

Is there a way to run the same unit test environments cleanly in the Test Explorer and as a part of a Manage project? If not, I think the documentation should be updated to make the distinction between standalone and managed environments more clear.

[aytey]

Hi @felixvanoost -- thanks for trying out the Test Explorer, especially with Manage!

As you identified, if you use the current version of the Test Explorer against a Manage project, then we try to work with the "incomplete" artefacts, and then the Test Explorer does not function as you would expect.

We actually have a branch in progress that adds first-class Manage support -- if you're really curious, you can give it a go: https://github.com/vectorgrp/vector-vscode-vcast/tree/manage_support_dev

I expect us release manage_support_dev sometime in February; however, if you would like to try it out, but need a bit more support, then please reach-out here and we'll be happy to assist you.

[felixvanoost]

Thanks @aytey! Great to hear that Manage project support is in development. I'll give the branch a try and report back if I run into anything unexpected. :)