In this article we will go through the properties panel of the setup step, and the common properties that exist in other steps.
Start a new test In the Test Editor (Alt + N).
The new test begins with a step labeled Setup. This step is essentially different from the other steps we are going to have in this test.
Let’s take a closer look:
Select the Setup step and open its properties:
You can change the value of any of the properties by clicking on them.
The URL that serves as the starting point for the test.
Allows you to change the default test configuration settings. This configuration will be used when running the test remotely if no other configurations are specified for running.
- Browser - the browser that opens the test.
- OS - the operating system you are running.
- Resolution - the size of the viewport. The viewport is the frame where the document is shown. A browser window is composed of the outer skeleton (called the chrome) and the viewport, which contains the body.
To change the Configuration just click on the "Configuration" link:
The default time frame (in milliseconds) given to a step in this test to be completed. Each step can override this in its property panel. If any step runs longer than that it is assumed that it’s stuck and the entire test will fail. The default value was set to 30,000 milliseconds (30 seconds). This is a very convenient feature that saves you the need to manually add a timeout to every step in your test.
Slows the pace of your test by adding a fixed delay (in milliseconds) after every step. This makes debugging easier, especially when the test runs very fast and you want to be able to follow it yourself after a new page is opened. This is useful when your pages have an inner logic that takes additional time to complete after the page is loaded but before the test proceeds.
Before test handler - You can choose any shared step you would like to be executed before a test starts.
Before each step handler - You can choose any shared step you would like to be executed before each step
After each step handler- You can choose any shared step you would like to be executed after each step, you can also choose if you want to run it only when step succeeded, failed or always.
- After test handler - You can choose any shared step you would like to be executed the test finished running, you can also choose if you want to run it only when the test succeeded, failed or always.
When a step fails the default environment behavior is to mark the step with error and stop the test. In every step's properties you can override the default behavior:
When a step fails - choose one of the 3 modes to apply to all steps in the test:
- "Mark error & stop" (the default mode) - a failed step is marked in red indicating an error. The test will stop and fail.
- "Mark error & continue" - a failed step is marked in red. The test will not stop but will still fail.
- "Mark warning & continue" - a failed step is marked in orange indicating a warning. The test will not stop and will not fail.
Note: the Setup step can also fail (if, for example, the test fails to navigate to the Base URL). Changing the "When step fails" settings in Setup only affects the Setup step and not the entire test.
Updated 9 months ago