Prior to Angular 2.0+, we were using Expected Conditions to wait for modal transitions. Without Expected Conditions, modal transitions would through off the timing of the tests. After migrating the project to Angular 2.0+, these Expected Conditions no longer work.
modalOkButtonElement.click(); // closes the modal (fades the modal away using css transitions, then routes to a different component, which is rendered to the user.)
var EC = protractor.ExpectedConditions;
browser.wait(EC.presence(componentTitleElement), 5000);
expect(componentTitleElement.getText()).toContain("My Routed Component Page Title");
The test runs and stops at the Expected Condition. After waiting some time at the Expected Condition, it times out and outputs that the element is not found. Is this a known problem?
Please advise.
Bug report
Node Version: 7.8.0
Protractor Version: 5.1.1
Angular Version: 2.3.0
Browser(s): Chrome
Operating System and Version OS X Yosemite 10.10.5
Prior to Angular 2.0+, we were using Expected Conditions to wait for modal transitions. Without Expected Conditions, modal transitions would through off the timing of the tests. After migrating the project to Angular 2.0+, these Expected Conditions no longer work.
modalOkButtonElement.click(); // closes the modal (fades the modal away using css transitions, then routes to a different component, which is rendered to the user.) var EC = protractor.ExpectedConditions; browser.wait(EC.presence(componentTitleElement), 5000); expect(componentTitleElement.getText()).toContain("My Routed Component Page Title");
The test runs and stops at the Expected Condition. After waiting some time at the Expected Condition, it times out and outputs that the element is not found. Is this a known problem?
Please advise.
Bug report
7.8.0
5.1.1
2.3.0
Chrome
OS X Yosemite 10.10.5