The VectorCAST Test Explorer extension has the handy snippet for adding vmocks: when you type //vmock the extension helps write the code for mocks.
A similar feature would be useful for requirements:
When you type //vcast_reqs: the extension should look at the requirements gateway for the environment the coded test file is attached to and display the requirements ID and title and allow one or more to be selected. The selected requirement keys separated by commas should be appended to the //vcast_reqs: line
The VectorCAST Test Explorer extension has the handy snippet for adding vmocks: when you type //vmock the extension helps write the code for mocks.
A similar feature would be useful for requirements:
When you type //vcast_reqs: the extension should look at the requirements gateway for the environment the coded test file is attached to and display the requirements ID and title and allow one or more to be selected. The selected requirement keys separated by commas should be appended to the //vcast_reqs: line