googletesting: Testing on the Toilet: Web Testing Made Easier: Debug IDs

Testing on the Toilet: Web Testing Made Easier: Debug IDs

Tuesday, August 12, 2014

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.buttonAnother 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 IDscontact-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

1 comment :

Miroslav GenovAugust 13, 2014 at 1:06 AM
Was wondering where you are running WebDriver tests on hosted mode (on a large project) ? If so, how fast you get feedback?
ReplyDelete
Replies

Add comment

Testing Blog

Testing on the Toilet: Web Testing Made Easier: Debug IDs

1 comment :

Labels

Archive

Feed

Company-wide

Products

Developers