結果がありません。
リクエストされたページは見つかりませんでした。記事を探すには、検索条件を絞るか、上記のナビゲーションを使ってください。
In this chapter, you’ll learn about the various options to control test runs and execute tests in the test suite view.
In this chapter
The screencast “test suite execution options” walks you through the information found in this chapter.
The explanations in this chapter are based on a sample solution. You can download it below.
Theme: Test suite run
Time: Less than 10min
Unzip to any folder on your computer.
Start Ranorex Studio and open the solution file RxDatabase.rxsln
The sample solution is available for Ranorex versions 8.0 or higher. You must agree to the automatic solution upgrade for versions 8.2 and higher.
You can include and exclude test cases and smart folders from a test run. To do so, simply check or uncheck them in the test suite.
Checkboxes to include/exclude from
The current state of checked/unchecked test cases and smart folders is called a run configuration. You can save run configurations for reuse and switch between them using the drop-down menu in the test suite view.
Manage run configurations
Click the run configurations drop-down menu.
Click Manage run configurations…
Adding a new run configuration
Click Add.
Give the new run configuration a meaningful name.
Click OK.
Different run configurations
TestRun configuration including all test suite elements
TestWithoutValidation configuration excluding the validation smart folder
Similar to including/excluding test cases and smart folders, you can also enable and disable recording modules, code modules, module groups, and
Disabling a recording module
Right-click the item you want to disable.
Click Disable. The item will be grayed out.
By default, test cases and smart folders are run once during test execution. However, you may want to run them several times. You can do so with run iterations.
Configuring run iterations
With a test case or smart folder selected, press F4.
The Properties pad appears to the right of the test suite.
Next to Iteration count, set the desired number of iterations.
Iteration count in the Properties.
In UI testing, errors will sometimes occur simply because the application under test was unresponsive. In these cases, one solution is to simply re-run parts of the test. You can do so with auto-retry. Test cases or smart folders with an auto-retry count will be rerun until they are either successful or all retries have been used up.
Configuring auto-retry
Select the desired test case or smart folder.
Press F4. The Properties pad appears to the right of the test suite.
Next to Retry count, set the desired number of retries.
Retry count in the Properties.
If there are data bindings or run iterations, the retries will start at the point of failure. For example, if the failure occurred at iteration 3 of 5, that’s where the retry will start
Only test cases or smart folders that failed every single retry will be marked as failed in the report.
You can also set the report level of test cases and smart folders in the test suite. Report levels allow you to control what information appears in the report, and where it appears. This is especially useful for complex tests with many test cases and smart folders, to keep the report structured.
Report levels are beyond the scope of this chapter. They
Errors are part of testing. This is why it’s important to tell Ranorex what to do when an error occurs. You can do so by configuring the error behavior of test cases and smart folders in the test suite.
The error behavior is set up in the context menu of a test case or a smart folder. There are four different types, explained below.
Specification of error behavior
The default error behavior is Continue with sibling.
Error behavior: Continue with iteration
Continue with iteration
The test run will continue with the next iteration of the smart folder Validation.
Error behavior: Continue with sibling
Continue with sibling
The test run will continue with the next sibling test case or smart folder. In our case, this is the smart folder DatabaseCleanUp.
Error behavior: Continue with parent
Continue with parent
The test run will continue with the next parent test case or smart folder. In our case, this is the test case CompleteDatabaseTest.
When the Stop error behavior is selected, an error immediately stops the entire test run.
Setup and teardown regions follow a special, fixed error behavior.
Running a test
Click RUN.
Watch Ranorex Studio execute the test.
Observe the progress information during the test.
After you’ve clicked RUN, do not use the keyboard or mouse. Doing so would interfere with the test actions and cause a test failure.
Reports are described in
Ranorex Studio fundamentals > Reporting > ⇢ Introduction.
You can also pause and resume test runs. This is explained in
Ranorex Studio fundamentals > Ranorex Recorder > ⇢ Run and debug recordings.
The Test Suite Runner is a stand-alone program which executes test suites without Ranorex Studio. It
You can use the Ranorex Test Suite Runner to execute entire test suites, run certain test cases and smart folders, or just run a specific module.
In addition, you can create new run
You can’t make changes to the test suite itself, however.
In Windows, double-click a test suite file. The file opens in the Test Suite Runner.
Click RUN.
Stand-alone Test Suite Runner
Currently loaded test suite