Do test case trial runs

Before you start running tests in earnest, do some trial runs of your test cases first. These trial runs help you find and fix issues, so you can make your test cases as stable and reliable as possible. Once you're in the test execution phase, you don't want to spend valuable time figuring out whether a failed result points to a flaw in your application or in your test.

The results of trial runs are only visible to you. Don't worry about cluttering up your team's views.

Run the test

To start a trial run, select Run.

You don't have to run your entire test case. To try out a group of steps instead of the entire test case, select their checkboxes. When you select Run, only your checked test steps run.

Alternatively, you can skip any test step. Just find the test step you want to skip, select , and select Skip during test run. Then, Tosca Cloud the test case won't run that test step during trial runs or test runs in playlists. You can still edit the test step when it's skipped, so you can fine tune a test step until it's ready without changing the rest of your test case. Later, you can include that test step. Just select , and select Unskip.

Tosca Cloud visualizes trial run results right in the test case.

The test case only shows the results of the latest run. It discards the result view as soon as you edit your test case, start a new trial run, or leave the page.

For trial runs on personal agents, Tosca Cloud also generates an entry on the Test runs page, which includes a log with detailed information. These entries are only visible to you, and they're available for shorter time than other test results. To access the logs, choose one of these options:

  • In the test case area, select View last run. Then, select the test run entry to open the details page, where you check the Logs.

  • Open the Test runs page. Then, find the trial run you're interested in and go to its details page.

Define what you want to run

You don't have to run your entire test case. To try out a group of steps instead of the entire test case, select their checkboxes.

Alternatively, you can exclude any test steps that aren't ready for a trial run yet:

  • In batches, by selecting multiple checkboxes and then Disable in the action bar.

  • Individually, through a step'soptions.

Excluding test steps allows you to create a more compact view. Turn on Show active only in the action bar to hide all test steps that are excluded or don't have a defined Action.

Run the test

How you start a trial run depends on where you are:

  • If you're in the regular test case editor, select Run/Run selected> Run on personal agent. This runs the test on your workstation. Keep in mind that this requires local components.

    A test case can access, read, and modify data on your workstation. Before you run it, make sure that you understand what actions it's going to perform. Also, close all windows that you don't need for the test run, and don't use your workstation while the trial test is running to avoid interfering with it.

  • If you're in the split-screen view of Cloud Scanner, select Run/Run selected. Or select the icon next to the step you want to try. This runs the test in a Tricentis-hosted environment.

Tosca Cloud visualizes trial run results right in the test case.

The test case only shows the results of the latest run. It discards the result view as soon as you edit your test case, start a new trial run, or leave the page or split-screen view.

Results visualization in the test case

For trial runs on personal agents, Tosca Cloud also generates an entry on the Test runs page, which includes a log with detailed information. These entries are only visible to you, and they're available for shorter time than other test results. To access the logs, choose one of these options:

  • In the test case area, select View last run. Then, select the test run entry to open the details page, where you check the Logs.

  • Open the Test runs page. Then, find the trial run you're interested in and go to its details page.

Handle issues

If you see some red in your trial run results, you need to investigate:

If Tosca Cloud can't find or interact with a control, check your application.

  • Does your screen look as expected at this particular point in the test?

    Check your module, especially the identifiers you chose for your controls. You may need to update the module. For example, rescan it to update identifiers after a code change in your application.

  • Are there any unexpected elements on your screen?

    Check for behaviors that you may have missed when you created your test. For example, confirmation dialogs or pop-ups that block the user interface.

Compare the expected result and the actual result.

  • Are you verifying the right control?

    Check your test case to make sure you're verifying the right control. That's especially true for tables, where it can be easy to accidentally identify the wrong cell. You may need to update your test case.

  • Is it a legitimate verification issue? In other words: you're definitely verifying the right control, and there's a difference between your test case and the application.

    Check your test case and your application to figure out which one is wrong. You may have to go through both, step by step, to find the source of the issue.

If Tosca Cloud times out on screens or controls, check your application.

  • Are all controls active that you expect at this particular point in the test?

    Check your application for dependencies between controls. You may need to add wait times to your tests.

  • Did your application take longer to load than expected?

    Check with your QA team. If the screen or control really shouldn't take this long to load, leave your test case as it is. That way, you get the error until your application is fixed. Otherwise, add a wait time.

What's next

Your test cases are as stable and reliable as you can make them. Create a playlist, so you can run your test suite in earnest.