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
{{ message }}
This repository has been archived by the owner on Jul 29, 2024. It is now read-only.
The findElement call within this example gives a NoSuchElementError, presumably because the element does exist until the beginning of the test is completed.
ptor.get('http://angularjs.org/');varel=ptor.findElement(protractor.By.input('todoText'));el.click()el.sendKeys('Write tests!');varbtn=queryDoc('[ng-submit="addTodo()"] .btn-primary');btn.click();expect(tractor.findElement(ptor.By.css('[ng-repeat="todo in todos"]:nth-child(3) span'))).toEqual('Write tests!');
The text was updated successfully, but these errors were encountered:
To clarify, it's the below bit of code that wasn't working.
expect(ptor.findElement(protractor.By.css('[ng-repeat="todo in todos"]:nth-child(3) span'))).toEqual('Write tests!');
I assumed there was a change with how protractor manages control flow that had caused this test to stop working in the latest protractor, but after getting the debugger to work, it looks like the problem is that the btn.click() isn't actually registering/creating the element for some reason. I'm working on finding out why.
The findElement call within this example gives a NoSuchElementError, presumably because the element does exist until the beginning of the test is completed.
The text was updated successfully, but these errors were encountered: