alexcrack / alexcrack/angular-ui-notification

protractor tests : using $interval instead of $timeout for notify duration management

Open
#78 3 comments 1 reaction 0 assignees View on GitHub
Dominant language
JavaScript
Stars
529
Forks
164
PR merge metrics
No merged PRs in 30d

Description

I use this module in my application to display notifications that disappear after a few seconds, and I write protractor e2e tests : the notifications are not testable.
This issue comes from the $timeout service to manage notification duration : protractor waits for $timeouts (and $http) before to run actions and expectations. So notification with duration can't be tested as they disappear before protractor tests them.
I think you are aware of this since you used the ignoreSynchronization parameter in your own protractor tests. But this is not a solution, we should still be able to let protractor wait for the end of $http requests.
In documentation (https://github.com/angular/protractor/blob/master/docs/timeouts.md), protractor team advises to replace $timeout services by $interval services to this kind of issue.

Have you considered using $interval instead of $timeout ?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.