T4Z can reference workspaces to other VS Code Testing Extensions

Products

• Test4z

Issue/Introduction

When initializing a workspace with Test4z, is it possible to handle the tests using Test Explorer?

Is it possible to use the graphical capabilities when the tests are in another directory that is not the standard one ("./test" directory)?

When using B4G or Explorer for Endevor, the test files are placed in directories that follow an "Endevor internal path" (e.g. DEV/1/SYS1/SUB1/COBTEST)

and the Test4Z extension capabilities are not enabled.

Resolution

Other directories can be added to the configuration to view them in the graphical extension.

For example, if tests exist in "test" and "Sample-Test" directories, the configuration should be updated as follows to include both.

  "cobolTestGlobs": [

    "Sample-Test/*.cbl",

    "test/*.cbl"

  ], 

To view test cases in the Test4Z extension within the B4G workspace, update the "cobolTestGlobs" value with the respective paths in the test4z.project.config.json.

  "cobolTestGlobs": [

    "DEV/1/RISYS1/RISUB1/COBTEST/*"

  ],

Graphical symbols will be seen beside the test when the mouse is held over the test case.

NOTE:  Test4z versions prior to v1.1.3209 may present problems with the Test Explorer not finding and listing the test suites when t4z initializes a workspace that holds the test suites in a named directory that is not "/test" .