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
it('can clear the Roster',function(){RosterPageObject.clearRoster();// expect Roster to be in its initial stateexpect(RosterPageObject.rosterNames().count).to.equal(0);expect(RosterPageObject.nameInputValue).to.equal('');expect(RosterPageObject.isClearButtonVisible).to.be.false;});
It may be helpful for the PageObject to define what it means for the Roster to be "empty" so that the tests don't have to check each individual criterion, and so that these criteria do not need to be repeated every time we need to check whether the roster is empty. A none helper would be useful in this case:
Given the following test...
It may be helpful for the PageObject to define what it means for the Roster to be "empty" so that the tests don't have to check each individual criterion, and so that these criteria do not need to be repeated every time we need to check whether the roster is empty. A
none
helper would be useful in this case:This would allow the test above to be rewritten as follows:
The text was updated successfully, but these errors were encountered: