"Create VectorCAST Environment" vs. "Create VectorCAST Environment in Project"

[sesame0707]

Hello!

What's the exact difference between "Create VectorCAST Environment" and "Create VectorCAST Environment in Project" when you right-click on a source code file?

[sesame0707]

Hello!

What's the exact difference between "Create VectorCAST Environment" and "Create VectorCAST Environment in Project" when you right-click on a source code file?

By the way, none of these options seem to work (the new unit test environment is not being created - as opposed to using the VectorCAST GUI)

[Den1552]

Hi Piotr,

Thank you for reaching out. I’m happy to clarify the difference between the two commands in the VectorCAST VS Code extension.

First of all:
A project in VectorCAST is a collection of related test environments, compiler settings, and configuration data that are centrally managed together. When you want to create an environment from source files, you have these two options:

1) Create VectorCAST Environment
This generates a standalone environment for the C/C++ file(s) you’ve selected. It places the environment (by default) under the folder you’ve configured as the Unit Test Location (for example, ./unitTests next to your source file). You can also change this location in your VectorCAST Test Explorer extension settings (in VS Code: Ctrl + Shift + P → VectorCAST Test Explorer: Configure → Unit Test Location).

2) Create VectorCAST Environment in Project
If you are working within an existing VectorCAST project (which must be part of your opened workspace in VS Code), this option lets you create an environment from source files and integrates it into the project. We are also currently adding the ability to create a new project within VS Code.

Feel free to let me know if you have any further questions — we can also set up a meeting to go through this together if you like!

[sesame0707]

Thank you very much for the detailed answer! It clarifies my question. Hence, I'm closing the discussion