How to enable Screenshots for your Test Steps in Testsigma?

You can enable screenshots in your Execution in two ways depending on the type of Execution you are using. 

  • In the Create Execution Configuration page for Dry Run Executions or,
  • In the Executions page for Normal/ Quick Executions

Please check the following article for more details - How to enable screenshots for your Test Steps in Testsigma?

Why is my Test Case not visible in Test Suite creation page?

Test Case has to be in Ready state to be visible and usable in other parts of the Tool such as Test Suites page or to create a quick Execution without creating a Test Suite.

Why does my App data(login details, history e.t.c) get cleared when automating Apps using Testsigma and Appium?

By Default, Appium resets the App Data of the Application to be tested when starting a session. We need to set the desired capability 'noReset' to 'true' to restrict Appium from reseting the App Data.

If you are using Appium Desktop, please follow the below guide:

How to set Desired Capabilities on Appium Desktop for automating Mobile Apps?

Here's the Official Documentation

Appium Desktop : Starting a new Session with desired Capabilities

Why does some of my Tests run successfully on one Browser(Chrome) and fail on another(IE) with the same steps and same UI Identifiers?

This is caused due to the difference in the implementation of rendering engines in different Browsers. Most of the well known Browsers use different rendering engines for parsing or displaying Web pages.

  • Chrome uses an engine named 'Blink' and 'V8'
  • Older version of Firefox uses 'Gecko' and the newer version use 'Quantum'
  • Safari uses 'WebKit'
  • Edge uses 'EdgeHTML' and 'Chakra'
  • Internet Explorer uses 'Trident'

The reason for specifying these names is to show that there is a huge disparity in the rendering done by different Browsers. This leads to difference in evaluation of the HTML DOM by different Browsers and eventually to the success and failure of same UI Identifier on different Browsers.

The solution is to use CSS Selectors or Relative XPaths with as little DOM propagation as possible. As the number of ancestors for a node increases, there is an increased chance for failure of the locators.

Why can't we use Testsigma Labs or other Cloud Execution models for testing locally hosted applications using Testsigma?

Cloud Execution models in Testsigma such as Testsigma Labs uses devices on cloud to run the Tests rather than your local device. Therefore, they do not have access to applications that are not publicly available on Internet or which are guarded by a corporate firewall.

For testing locally hosted Applications, we can use Hybrid(Local) Execution Model on Testsigma that uses the local machine to run tests. Please check this guide to know more about Hybrid Execution - How to execute Web Application tests in Hybrid model?

A quick test to check if an application is accessible for Hybrid Execution on a Test System is to actually access it in the default Web Browser on the Test System which you have selected in Execution Configuration of your Hybrid Execution.

How is Testsigma different from other Testing Tools online?

Many of Automated Testing tools online use a Record and Playback methodology for creation of Test Cases. This approach is easy to use but lacks the flexibility to handle complex operations and to make commands tailored to your application.

Although we have provided a Record and Playback tool ourselves to get acquainted to Testsigma and to help you make Test Cases for small applications, we are focusing on developing a platform that allows non-programmers to create Test Cases with the same flexibility of using programming based tools with minimum effort.

Why can't Test Data Profiles be associated to Step Groups in Testsigma?

Step Group is a reusable set of Test Steps and a Step Group cannot be associated to a single Test Data Profile in Testsigma. The reason for this design decision can be explained as given below:

Step Group is designed to be used in different Test Cases and therefore cannot be associated to a single Test Data Profile. Associating a single Test Data Profile to a Step Group would create a hard dependency  and that would hinder its re-usability across multiple Test Cases.

Currently, Step Groups inherit the Test Data Profile that its parent Test Case is associated with. That allows it to be used freely in different Test Cases without dependencies.