Search results

...tput of each Test group is placed within a hierarchy of named suites. (The root suite does not have a name.) ...elimited by "/" (forward slash) and are always specified starting from the root.

...stallation example assumes the the installation package is located in your root directory and that the directory <tt>\stride</tt> exists. You can choose to ...hat the <tt>STRIDE_DIR</tt> environment variable exists and is set to the root installation directory (<tt>\stride</tt>). If this environment variable doe

...stallation example assumes the the installation package is located in your root directory and that the directory <tt>\stride</tt> exists. You can choose to ...hat the <tt>STRIDE_DIR</tt> environment variable exists and is set to the root installation directory (<tt>\stride</tt>). If this environment variable doe

...ill run the three tests in the order shown, putting their results into the root test suite. Or, if your test results are to be published in the root suite, you can use this simplified syntax:

* A <code>[section]</code> in Testspace schema "root" settings hides [[STRIDE Runner]] command line options.

...he default flat hierarchy with each test unit's corresponding suite at the root level of the report.

: Here we specify two tests to be run and published to the root suite

* A <code>[section]</code> in Testspace schema "root" settings hides [[STRIDE Runner]] command line options.