6 Steps to Automate Cross Browser Testing for Continuous Delivery

“Cross Browser Testing is a testing approach that essentially helps us to assure compatibility of our Application across all the Browsers that are used by the End User of the Application.” –  Advantages of Cloud Based Cross Browser Testing Tools

“Testing across a variety of browsers will reveal issues the developer may have left uncovered.  Finding a bug at the user level is not welcome in a competitive world and the users may not necessarily stay and give a chance which in turn affects the business. Hence, Cross Browser Testing becomes very important to ensure cross browser compatibility of your website and application.” – 8 Essential Elements Required in Automated Cross Browser Testing Tools

Why Automated Cross Browser Testing?

Reason 1 – Manually testing across all these Test Environments takes huge amount of time and resources.

Reason 2 – Another reason for advocating Automated Cross Browser Testing would be to include Continuous Delivery practices. It is almost impossible to implement Continuous Testing and Continuous Delivery with manual Testing alone.

How Testsigma can help

Testing of an application across multiple browsers is a tedious task. Considering the fact that there is a need for continuous testing in today’s agile development environment, the difficulty only increases.

Testsigma is an End to End Test Automation platform. It enables you to create Tests in Simple English as well as provide a Cloud-based Execution Platform to execute the created Tests.

Testsigma simplifies your job by managing multiple browser environments. You can use the cloud infrastructure if you don’t have the physical infrastructure for running parallel browser sessions on multiple devices.

Testsigma is built to address the automated cross-browser testing requirements.

Steps to automate Cross Browser Testing using Testsigma

For performing Cross Browser Testing in Testsigma, we need to follow the below steps:

1. Create one or more Test Cases and add a few Test Steps

Testsigma allows you to Write Automated Tests Quickly Using Simple English – Everyone can write automated tests at least 5X faster using simple English. No coding skills required.

If you are not familiar with creating Test Cases in Testsigma, please check out our previous DZone article – Web Application Automated Testing With Testsigma to gain some insight into the process of creating and executing a simple Test Case in Testsigma.

Let us assume we have already created a Test Case to check the login page of Testsigma in three web browsers, Chrome, Firefox, and Internet Explorer. You can add more browsers to the list.

Automated Test Steps

Once the Test Cases are created and Test Steps are added to it, you can move onto creating a Test Suite to group the Test Cases.

2. Create a Test Suite and add the previously created Test Case/Cases to it

Test Suites are used to group a set of Test Cases for Execution. We need to create a Test Suite even though we have only a single Test Case in this example. Test suites are mandatory for execution since every Execution takes a Test Suite as input.

Check the below article to know how to create Test Suite and add Test Cases to it.

How to add/edit/Delete Test Suites

Now we can move onto the next step, creating an Execution and adding multiple Execution Environments to it. We need to create a separate Execution Environment for each of the web browsers in which we want to run the Tests.

3. Create an Execution and add separate Test Environments for each of the web browsers

Run Tests on 1000+ Real Desktop Mobile Browsers – Test your web applications over 1000 operating system and browser combinations instantly available in the Cloud.

To create an Execution, you can navigate to the Executions page by going through:
Applications > Select Application > Select Version > Executions

1. Click on the Create button in the top right corner to create an Execution. The Create Execution page would open up as shown below:

Create Execution Page
Create Dry Run Page

2. Enter the required details such as Execution Name, Execution Model, etc. We will select the Test Lab Type as ‘Testsigma Lab’ and Execution Type as ‘Cross Browser Testing’ for this example.

3. Click on Select Test Suite to open the Select Test Suite overlay page and select the required Test Suite/Suites to be included. We will select the Test Suite created in previous section.

4. Click on Select Test Environment to open the Select Test Environment page. In this page, we can specify the Operating System and Browser settings for each Test Environment. Finally, click on the Create button.

5. Repeat the above step (Step 4) to create more Test Environments for each of the Browsers.

With Testsigma, you can Speed up Test Runs with Parallel Test Executions – Run tests in parallel across many different test environments to cut down your build times.

Once all the required Test Suites and Test Environments are added, it will look similar to the below image:

3 different Test Environments

Here, we have created three Test Environments – for Google Chrome, Mozilla Firefox, and Internet Explorer.

6. Now, click on the Create button to create the Execution.

7. We will be taken to the Executions page. Click on the newly created Execution name to go to the Execution details page. You can find the CI Integration details there.

CI Integration

4. Integrate into the CI Pipeline

Using Continuous Integration for Agile and DevOps Teams – Shift-left approach and seamless integrations with CI/CD tools ensures the quality of your applications in continuous delivery practices.

As you can see in the above section, we have obtained the command to start the CI Integration.

curl -X POST -H 'Content-type: application/json' -u <Username>:<Password> https://app.testsigma.com/rest/execution/<execution ID>/run

Note: Replace the dummy values between <> with the required values.

You can use the above command as your post build step in your Continuous Integration server to integrate the Test into your CI/CD pipeline.

Also, you can use Testsigma’s Execution Status REST API call to wait for the execution completion and notify you once the execution is complete.

5. Analyse individual Environment results

We get Comprehensive Reports and Debugging Tools – Dynamic and customizable reports with text logs, screenshots, video recordings and many more to help you analyze results faster.

Once you get the Execution completion notification, you can log in and check the test results for the individual Environments

Run Results – Run ID page
Run Results – Test Environment Page

6. Debug and Report Bugs easily

Drill down the Test Results to get to the root cause of the failure and file a bug into the integrated Bug Platform such as JIRA.

Testsigma is built for all your continuous testing requirements and Cross Browser Testing is just one of them.

Signup for free to get access to everything needed for your continuous testing instantly.
Try Testsigma Now!