Once you start actively automating Tests and run those Test Cases, you will face some errors due to either incorrect usage or random Application Behaviour.
The former can be rectified with some help from the Support team. Here are some of the common failures in Testsigma and how we debug them.
Most common issues caused when navigating to a website - Goto NLP Statement
Most common causes for Page load Timeout issues in Testsigma
Most Common causes for Click/Tap NLP failure
Most common causes for Text Verification Errors in Testsigma - Verify, Click, Wait for, or Scroll to Element
For Action-related Errors, you will find the reason for the error and ways to fix the error in the Failed Step Error message. If that's not clear, feel free to contact the Support team.
UI Identifiers(element locator) related Errors
Most common issues caused when using NLP locators like title, placeholder, label, Index, and Text
Most common issues caused when using UI Identifiers
For UI Identifier related errors, you will get the below two Actions in the failed step:
1. “Click here to know other tests which may have been affected”
This will let you see all the tests that will be impacted by this failure. If you click on the above option below page appears showing all the Test Cases associated to the particular UI Identifier(if any):
2. ‘Click here to edit UI identifier'
We are taken to the faulty UI identifier to do edits if needed. After fixing the error, the test can be re-executed by clicking on Re-Run at the top to execute the test case again.
Once the test is fixed you can rerun the same test using the same old configuration.
You may now start exploring the other features in Testsigma, we recommend you to go through the same order that we have maintained in this portal menu section.