You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to facilitate rapid development of QA Automation for Beach City, the use of static, unique ID Attributes in HTML elements would be a major improvement. One way to begin with this is to have all of the various controls in the left hand side of the multi-column window have static IDs in their HTML elements. These include all the controls related to toots, such as the CW button, and the "drawer" elements in the top left hand side. An HTML example of what I'm talking about is having a element be modified to include a static, unique id attribute, so that the element would now be .
Motivation
By implementing static Id attributes, automation that can control and change the state of the application doesn't have to require the complexity of needing different locators (such as XPath) for the same controls when the state of the application changes. This also makes automation more maintainable and faster to develop as the total number of locators and their corresponding WebElement objects is reduced.
The text was updated successfully, but these errors were encountered:
Pitch
In order to facilitate rapid development of QA Automation for Beach City, the use of static, unique ID Attributes in HTML elements would be a major improvement. One way to begin with this is to have all of the various controls in the left hand side of the multi-column window have static IDs in their HTML elements. These include all the controls related to toots, such as the CW button, and the "drawer" elements in the top left hand side. An HTML example of what I'm talking about is having a element be modified to include a static, unique id attribute, so that the element would now be .
Motivation
By implementing static Id attributes, automation that can control and change the state of the application doesn't have to require the complexity of needing different locators (such as XPath) for the same controls when the state of the application changes. This also makes automation more maintainable and faster to develop as the total number of locators and their corresponding WebElement objects is reduced.
The text was updated successfully, but these errors were encountered: