New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use Angular's testability API to wait for end of e2e tests #3829
Comments
The hack was introduced here: #3822 |
Not as easy as it seems since we have tests which need to wait for Angular 2, and some that don't. @tbosch Any suggestion on how to achieve that in a generic way please? I.e. without setting a flag or doing it in each test? |
I think for the examples/benchmarks that don't use |
FYI, this should eventually be done in Protractor. Setting up the next Protractor release to take care of it. |
The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes angular#3829
The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes angular#3829
The latest Protractor version supports waiting for Angular2 applications, so remove custom waiting logic. Closes angular#3829
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Right now, we rely on a hack to wait for the end of e2e tests: We wait until the "loading..." text disappears. However, Angular exposes an API to know when bootstrap is done via
global.getAllAngularTestabilities()
(see https://github.com/angular/angular/blob/master/modules/angular2/src/core/testability/get_testability.ts). We should use this API to prevent future breakages / hard to explain errors...The text was updated successfully, but these errors were encountered: