Steps to Reproduce
-
Create a VectorCAST environment (e.g., for source.c) outside of the VS Code extension using the standard workflow.
-
Launch VS Code from a batch file that sets the required environment variables and compiler path.
Example:
call setenv.bat
start D:\Users\vulwns\AppData\Local\Programs\Microsoft_VS_Code\Code.exe
The batch file should:
- Set
VECTORCAST_DIR
- Set
VECTOR_LICENSE_FILE
- Add the compiler location to
PATH
-
In VS Code, open the working directory as a workspace.
This allows the VectorCAST Test Explorer extension to recognize the environment and enables the VectorCAST context menu options within the Testing view.
-
Open the Testing view (flask icon) and locate the environment.
-
Right-click the environment and select Environment Rebuild.
-
Open the Output panel:
- Navigate to View → Output
- In the Output panel, use the dropdown on the right and select VectorCAST Test Explorer as the output source.
Please look at the attached output_log.txt
output_log.txt
Observed Behavior
The VectorCAST Test Explorer output log displays environment rebuild messages twice, even though only a single environment rebuild operation was performed.
Expected Behavior
Only one set of rebuild messages should be displayed in the output log for a single environment rebuild operation.
Steps to Reproduce
Create a VectorCAST environment (e.g., for
source.c) outside of the VS Code extension using the standard workflow.Launch VS Code from a batch file that sets the required environment variables and compiler path.
Example:
The batch file should:
VECTORCAST_DIRVECTOR_LICENSE_FILEPATHIn VS Code, open the working directory as a workspace.
This allows the VectorCAST Test Explorer extension to recognize the environment and enables the VectorCAST context menu options within the Testing view.
Open the Testing view (flask icon) and locate the environment.
Right-click the environment and select Environment Rebuild.
Open the Output panel:
Please look at the attached output_log.txt
output_log.txt
Observed Behavior
The VectorCAST Test Explorer output log displays environment rebuild messages twice, even though only a single environment rebuild operation was performed.
Expected Behavior
Only one set of rebuild messages should be displayed in the output log for a single environment rebuild operation.