by Ruslan Khamitov This article was adapted from a Google Testing on the Toilet (TotT) episode . You can download a printer-friendly version of this TotT episode and post it in your office. Adding ID attributes to elements can make it much easier to write tests that interact with the DOM
Save button
Edit button
<div class="button">Save</div>
<div class="button">Edit</div>
One option is to interact with the button using a CSS selector: div.button
Another option would be to write an XPath, which is generally fragile and discouraged: //div[@class='button' and text()='Save']
Your best option is to add unique hierarchical IDs contact-form .save-button
contact-form .edit-buttonIn GWT you can accomplish this by overriding onEnsureDebugId()on your widgets @Override protected void onEnsureDebugId (String baseId) {
super .onEnsureDebugId (baseId);
saveButton.ensureDebugId (baseId + ".save-button" );
editButton.ensureDebugId (baseId + ".edit-button" );
}
Let’s set IDs for repeated UI elements in Angular <tr id="feedback-{{$index}} " class="feedback" ng-repeat="feedback in ctrl.feedbacks" >
In GWT you can do this with ensureDebugId() @UiField FlexTable table;
UIObject.ensureDebugId(table.getCellFormatter().getElement(rowIndex, columnIndex),
baseID + colIndex + "-" + rowIndex );
Take-away: Debug IDs are easy to set and make a huge difference for testing
Was wondering where you are running WebDriver tests on hosted mode (on a large project) ? If so, how fast you get feedback?
ReplyDeleteGenerally I try not to touch class, especially without some sort of prefixing thing because you don't know what styles properties are out there current and in the future.
ReplyDeleteInstead, what I like to do is use the 'data-*' properties.. So I might have something like,
driver.find_element_by_css_selector("[data-aut-id='figurestable'] tr[data-aut-id='entry{0}']".format(entryId))