# Automating Salesforce Lightning with Playwright: Why Generic Locators Become a Challenge

Description and use

<p>Salesforce Lightning applications can be challenging to automate, particularly when dealing with complex page structures, dynamically rendered components and repeated UI interactions.</p> <p>One challenge that becomes increasingly noticeable when working with browser automation is <strong>locator identification</strong>.</p> <p>In a simple application, identifying an element by its role, accessible name or text may be sufficient. However, enterprise applications such as Salesforce often involve complex workflows where similar interactions are performed across different records and sections.

Problem

<p>Salesforce Lightning applications can be challenging to automate, particularly when dealing with complex page structures, dynamically rendered components and repeated UI interactions.</p> <p>One challenge that becomes increasingly noticeable when working with browser automation is <strong>locator identification</strong>.</p> <p>In a simple application, identifying an element by its role, accessible name or text may be sufficient. However, enterprise applications such as Salesforce often involve complex workflows where similar interactions are performed across different records and sections.

Outcome

<p>Salesforce Lightning applications can be challenging to automate, particularly when dealing with complex page structures, dynamically rendered components and repeated UI interactions.</p> <p>One challenge that becomes increasingly noticeable when working with browser automation is <strong>locator identification</strong>.</p> <p>In a simple application, identifying an element by its role, accessible name or text may be sufficient. However, enterprise applications such as Salesforce often involve complex workflows where similar interactions are performed across different records and sections.

Evidence

Automating Salesforce Lightning with Playwright: Why Generic Locators Become a Challenge

Source