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 Setup Teardown Scripts

Last updated: 2019-10-02

Is there a way to prepare my compiler, target and/or environment variable before testing in VectorCAST?


Yes, it is often necessary to do some preparatory tasks before running the tests for a VectorCAST environment. These tasks may include starting a target server, setting environment variables, starting simulators, etc. Furthermore, after the environment test-runs, it may be necessary to perform some cleanup tasks. These cleanup tasks may include killing processes, cleaning up files, etc.

See also this video tutorial.

VectorCAST/Manage Projects now contain a script in the <PROJECT_DIRECTORY>/python directory called This script is run when a project is loaded and is used to map the compiler node names within a project to Python classes that contain setup and teardown members.

  1. Access the Setup/Teardown script in Project | Edit Setup/Teardown

  2. In the script, locate class Target and add in what your testing requires in def setup for preparatory tasks and def teardown for cleanup tasks.

    The following example would print Testing setup and Testing teardown during invocation of the setup/teardown when building and executing environments as well as when creating environments.
Article Options
Views: 137