How to Solve Typical Automation Issues

Object Not Found

Q: I recorded a test, started playback, and got an Object Not Found message. What should I do?

A: Don't panic! There are several common reasons why an object is not found during playback.

Reason #1 (most common)

You are testing a web application where elements use dynamic IDs that change on every page load.

How to Fix

• Object Not Found - How to Fix (schema)
• Check that Rapise can find an object on the screen
• Configure Web Recording with Web Application Profile
• Use WebSpy to build a better element locator manually
• Turn On Self-Healing Locators

Reason #2

You are testing a very slow application, and the object is not yet available when it is needed.

How to Fix

• Ways to slow down test execution

Execute Tests Fast and Reliably

Let's talk about how to adjust an automated test to make it run fast and reliably.

Web Recorder Configuration

Rapise has a Web Recorder. When you start recording, Rapise intercepts your keyboard and mouse and adds the UI elements you are interacting with to the Object Tree. For each such element, Rapise generates an XPATH locator. Although it usually does a great job of generating XPATH locators, the default Web Recorder settings do not suit all web applications. For complex, modern applications, you may need to configure the Web Recorder to get the most out of it.