Running Non-Eyes tests

You can use Execution Cloud to run non-Eyes tests. A Non-Eyes test runs a script, and confirms that a process can be completed successfully without taking a screenshot for visual validation. For example, you may have a script which opens a Login window and confirms that the test is able to successfully enter a user name and password and open the Welcome screen.

Non-Eyes tests include Self-healing and troubleshooting features.

Creating a Non-Eyes test

  • Set up the environment as described in Setting up Execution Cloud.

  • Use the driver.executeScript command to run the test:

    startTest:

    
                                            

    endTest:

    
                                            
    • status: (Optional) The status to apply when the test is complete (Passed or Failed). If you do not set that status, the status will be listed as Completed or Aborted if the test timed out before it completed.

    Use driver.executeScript to start and end the test instead of eyes.Open and eyes.Close which is used in a standard Eyes visual test.

Viewing results in the Test Manager

If there are Non-Eyes test in a batch, the Test Manager displays the number of Eyes and Non-Eyes tests in the batch and there is an option to view a Test Type column which identifies which tests were Non-Eyes tests.