Justifying and Realizing a Strong ROI on Test Automation Sign up now

Webinar Summary: Testim Talks- How to have stable locators in your test

Web applications are constantly changing to help businesses differentiate or remain competitive. Each change to the frontend has the potential…

By Jennifer,

Web applications are constantly changing to help businesses differentiate or remain competitive. Each change to the frontend has the potential to break functional tests. Is AI the answer? In this webinar, we will discuss the challenges of frontend testing, backed by results of a Testim survey. We will show how test automation frameworks have evolved, and how artificial intelligence (AI) and machine learning (ML) can create a new path forward for test automation.

If you missed the webinar you can catch the recording below:

 

Here are two questions we received:

Q. If a button moves like that though, wouldn’t you want your test to fail so that you know the button has moved? If it still passes when elements have moved all over the place then you could end up with a horrendously messy page that doesn’t look right at all, but the tests still pass?

A. For both questions, When testing a business processes; having a test fail because a button moved or changed size with an “Element not found” error Is less than ideal. It causes extra work to figure out why a test is failing with a generic error message.

Better would be to let the business process testcase pass with moved (but logically correct) objects and then to have separate UI validation tests that validates location, size and/or style of objects within the page’s layout.

 

Testim's latest articles, right in your inbox.

From our latest feature releases, to the way it impacts the businesses of our clients, follow the evolution of our product

Blog Subscribe