In this chapter, we will learn how to run the test case that we created in the previous Chapter - Chapter 6: Create Test Case. 


To run a test case, you will need a test machine. Testsigma allows you to run a test case on one of the following Test Labs

  1. Testsigma Lab

  2. Local Machines

  3. Third-party IaaS providers like BrowserStack/Sauce Labs

  4. Private Grid

To know more about these test lab types, read What are the Test Lab Types available to execute tests in Testsigma?


In this chapter, we will run the test on a test machine from Testsigma Lab, which is a test lab on the cloud with 700+ unique test machine configurations with a unique operating system, browser, version, and resolution combinations. 

Steps to run the test case

1. Navigate to Test Development > Test Cases

2. On the Test Cases page that opens, click on the test case you created. For us, it is “Fly NYC”

3. Once the Test case is open, the page should look something like this:

4

4. Click on the ‘Run Test Case’ button on the top right corner of the test case. Below window should appear:

5. On this window, you will see that ‘Testsigma Lab’ under ‘Test Lab Type’ is already selected. The OS ‘Windows’ is selected by default. And the browser ‘Google Chrome’ is selected. This means that the test case will run on chrome browser on Windows on Testsigma Lab.


6. There are other conditions also that are already selected:

  1. OS Version - the version of the Operating system on which the test case will be executed

  2. Version - Version of the browser

  3. Screen Resolution - the resolution of the screen on which the test case will be executed.

  4. Capture Screenshots - for what steps should Testsigma capture screenshots, the options are: “Failed Steps”, “Mandatory”, “All steps”, “None”

  5. Environments -  are different testing environments like staging, development, production. You will need to configure them to add values

  6. Page load timeout - The maximum time to wait for a page to load, these can also be configured in the test steps.

  7. Element timeout - The maximum time to wait for an element(on a webpage) to load, these can also be configured in the test steps.

  8. Mandatory steps only - some steps could be marked mandatory and if this is selected, only those test steps will be run while test execution.

  9. Desired capabilities - if you have multiple servers like staging, dev, pre-prod for testing, then these can be configured here.


7. To run the test case, click on the button “Create and Run” on the bottom right.


Viewing the Test Run Result

  1. Test execution starts on clicking on the “Create and Run” button. This creates a test run and executes the test. After the text execution completes, the test result page opens which looks like below:

  1. In the above screenshot, a complete green circle means all the test steps executed successfully. Colors are also decoded on the side. And below there are options “Watch Video”, “Test Step Result”, “Attachments” and “Download Screenshots”.

  1. In the Test result, along with the time and environment of test execution - test priority, test case type, data drive, and message are also displayed. It also shows the user that executed the test case:


  1. To help the tester debug any failures, a test execution video can be accessed under the “Watch Video” tab. As can also be seen in the screenshot below:

  1. Results corresponding to each test step can be accessed under “Test step results” as can also be seen in the screenshot below:


  1. Execution logs can be accessed from the section “Logs” besides the “Test Step Results”. These can be downloaded by clicking on the “Download Logs” button on the right.


  1. Screenshots can also be downloaded from the “Download screenshots” button on the top right of the test steps section, as also can be seen in the screenshot below:


We ran one test case at one time in this chapter. To trigger the execution of many test case at one time, you can learn about Test Suites, Test Plans.


<< Chapter 6: Create Test CaseChapter 8: Analysing and Debugging Failures >>