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'.
apple* 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").
How does VectorCAST handle exceptions in the code?
Do you use exception specifications in your source code?
If your function has an exception specification (e.g. void foo() throw(int)), then a <<throw>> node will appear allowing you to set an expected value. If your function does not have an exception specification and you want to test or set an expected value for an exception, then you must either edit your source code or create a wrapper function which does have a specification. This wrapper can be defined inside unit appendix user code (Environment | User Code | Edit). A rebuild is necessary after any appendix user code has been added.
If you select Tools | Options | Execute, you should see an option labeled Fail on unexpected exceptions. Toggling this check box will control whether or not the test fails.
Are you trying to figure out how to raise an exception from a stub?
If you want an exception to be thrown via user code during the execution of your function under test, the user code will either have to be in configure stubs user code or parameter user code for a stub parameter. The reason for this is that stub calls are the only points where user code can be called during the actual execution of your function under test.
If you have an exception specification for the stub, however, it will be indicated in the parameter tree for that stub and will not require user code to set or test the value.