While some applications are straightforwardly built, others have more dynamic, complex needs, especially if you’re customizing the app to fit your needs. Salesforce is one of those tricky apps, but we’re experts at making every part of Salesforce testing a breeze.

What makes an element complex?

An element is considered complex if it involves dynamic data, changing attributes, or dependencies on other elements, making it harder to identify or interact with. Common complexities include dynamically generated locators, conditional visibility, asynchronous loading, nested structures like shadow DOM, or reliance on custom widgets and frameworks. Elements with animations, dynamic styling, or intricate interactions (like drag-and-drops) also add to the challenge. Typically, testing such elements effectively requires strategies like robust locator usage, explicit waits, and controlled test data to ensure reliability and coverage. 

How does Virtuoso QA handle complex elements?

The first step to identifying an object is the hint that the tester enters into Virtuoso QA. This can be as simple as the words on a button or as specific as pulling an ID from the inspector console. Once the element has been correctly identified, Virtuoso QA uses as many IDs for an object as it can find, including Xpaths, Xpaths ID, and CSS selectors, to build a complete model of each element. That way, if one of those IDs suddenly changes or becomes invalid, Virtuoso QA still has plenty of data to fall back on.

But what about when there are multiple similar elements to choose from? Or when you have to deal with JavaScript events before the value is entered into the input field? Luckily, our Virtuoso QA expert, David Ross, has put together an ebook just for those instances, plus a handful of best practices to keep in mind. Enjoy knowing that testing those complex elements is simple with Virtuoso QA!