Test Execution
Page tree

Versions Compared

Old Version 4

changes.mady.by.user user-f1009

Saved on

compared with

New Version Current

changes.mady.by.user jonny steiner

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Mobile tests execution time is too long

SEO Metadata
titleTroubleshooting

When running mobile tests using SeeTest Digital Assurance Lab, we take screenshot after each command.

When running mobile tests using SeeTest Digital Assurance Lab, we take screenshot after each command.

Taking screenshot can take a long time and cause the whole test to take longer. If you wish to give up on a test report creation you should include this capability in your test:

Code Block
languagejava
titleCode example
DesiredCapabilities dc = new DesiredCapabilities();
dc.setCapability("deviceQuery", "@os='android');
dc.setCapability("username", "cloudUsername");
dc.setCapability("password", "cloudPassword");
dc.setCapability("projectName", "cloudProject");


//Add this capability in order to disable reports & get faster execution times
dc.setCapability("generateReport", false);	
   
AndroidDriver driver = new AndroidDriver<>(new URL("http://"+cloudHost+":"+cloudPort), dc);

Table of Contents


Web tests fail with Timeout

When running web tests using SeeTest Digital Assurance Lab, we take screenshot after each command.

Taking screenshot can take a long time (particularly in Internet Explorer), so when running web grid tests on SeeTest Digital Assurance Lab user should do one of the following:

  1. Disable taking screenshots by adding the capability takeScreenshots=false in the conf.js file.
  2. Increase default timeout. In Protractor it's done by adding the following piece of code to the exports.config in conf.js file:
Code Block
languagejs
titleprotractor.conf.js
exports.config = {
..
..
	jasmineNodeOpts: {
	defaultTimeoutInterval: 2500000
	},
..
..
}