Understanding and troubleshooting GUI test results

Points to remember

• Use "View Results in Tree" to see detailed error in case a field cannot be detected or test is stuck.
• Use "Summary Report" to get summarised result and error percentage.
• Run a test with Browser head enabled with single virtual user to cross verify the script .
• Change in Instances may result in change in element ids , go through the inspect field and match the values in attached CSV or variables in the script.
• Repeat a test at least 4 times to get better understanding and accuracy of test results.

Troubleshooting the test cases

• Keep Track of error logs and console , when running GUI test cases for better understanding about point of breakdown.
• Data used is dynamic fetched from CSV's understand the script and edit it accordingly . Any error due to variables or paths will be highlighted in the log as well as listeners.
• Sometimes due to null values in the mandatory fields , Predefined Condition failed is received . Check the variables/parameters used to send data in CSV files and script.
• Handle the screen shots path so that GUI breakdown can be figured out when headless test cases are run.
• Error due to dependency can be handled with proper imports and jar files available online.