Contact us
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

Position of Generated Test Cases in Test Execution Tree

Last updated: 2017-08-09
I am missing an ability to structure the test cases developed in Test Diagram Editor. I will create most of my test cases in the Test Table Editor but for some test cases I foresee that the Test Diagram Editor is more useful (e.g. for state transitions, certain sequences etc.). I would then like to be able to control where in the test execution tree structure these generated test cases from Test Diagram Editor are inserted (e.g. by the grouping element). I may not always want to execute these test cases at the position in the test tree where the system places them automatically.

For test cases generated based on path structure or test case annotations, it is not possible to have preconditions or preparations/completions in the Test Diagram Editor. You have to define this logic with the help of the "normal" graphical elements and test commands.

However, if you use the graphical element [Test Case Call] to call a test case defined in CAPL, C# or the Test Table Editor, you can define a precondition for this test case call in the Test Diagram Editor. Additionally it's possible to define a preparation/completion for a test case definition in the Test Table Editor.

If a test unit contains multiple test execution trees (e.g. a Test Table file and a Test Diagram file) the execution trees are put one after another in alphabetical order of the file names.

Article Options
Views: 874
Rate this article:  
Also listed in
Error(s) occurred processing form.
Please complete all required fields. Fields marked with * are required.