Search tips

apple banana
Find rows that contain at least one of the two words.

+apple +juice
Find rows that contain both words.

+apple macintosh
Find rows that contain the word 'apple', but rank rows higher if they also contain 'macintosh'.

+apple -macintosh
Find rows that contain the word 'apple' but not 'macintosh'.

+apple ~macintosh
Find rows that contain the word 'apple', but if the row also contains the word 'macintosh', rate it lower than if row does not. This is "softer" than a search for '+apple -macintosh', for which the presence of 'macintosh' causes the row not to be returned at all.

+apple +(>turnover >strudel)
Find rows that contain the words 'apple' and 'turnover', or 'apple' and 'strudel' (in any order), but rank 'apple turnover' higher than 'apple strudel'.

Find rows that contain words such as 'apple', 'apples', 'applesauce', or 'applet'.

"some words"
Find rows that contain the exact phrase 'some words' (for example, rows that contain 'some words of wisdom' but not "some noise words").

By continuing to use this site you agree to the use of cookies. For more information and to find out how to change this click here. Accept Cookies
Please enable cookies in your browser for this website.
Advanced search

VectorCAST Identifying Impacted Requirements

Last updated: 2019-10-02

Does VectorCAST track changes in linked requirements from an external management system?

How does VectorCAST prevent a changed requirement from being overlooked?


If VectorCAST detects that a requirement has been updated and it is linked to a test case in a VectorCAST unit test environment, then the requirement is considered "impacted". Any test cases linked to impacted requirements are then marked as needing review.

The user is then prevented from changing the list of linked requirements, and from exporting case pass/fail data back to the requirements / ALM system.

The user then verifies that the test case still satisfies the test's associated requirement(s), perhaps modifying Input or Expected Values and executing as needed.

When done, the user marks the test case as having been reviewed. This action then frees up the restrictions on the test case, allowing the user to once again change the list of linked requirements, and export the pass/fail status back to the requirements / ALM system.

See also this video tutorial.

Article Options
Views: 56