bug(testability): scheduling a task with setInterval causes angular to be seen as unstable indefinitely #8089

Activity

1. sjelin commented on Apr 15, 2016

   

   sjelin

   on Apr 15, 2016

   Last edited by sjelin

   ContributorAuthor

   More actions

   Minimal(ish) reproduction:

   describe('async angular2 application', function() {
     it('should work with setInterval', function() {
       browser.get('/ng2/#/async');
       $('#periodicIncrement .action').click();
       browser.waitForAngular();
     });
   });

   This is a protractor spec against our ng2 testapp. I tried just doing an executeScript instead of clicking on an element but that didn't work, presumably because it wasn't being executed within an angular component.
2. juliemr commented on Apr 25, 2016

   

   juliemr

   on Apr 25, 2016

   Contributor

   More actions

   This is working as intended - you should run the setInterval outside of the Angular zone. We should make sure that we have good documentation for this.

   👍React with 👍1Reacted by Michael Prentice
3. juliemr commented on Apr 25, 2016

   

   juliemr

   on Apr 25, 2016

   Contributor

   More actions

   See instead #8219
4. juliemr

   closed this as completedon Apr 25, 2016
5. wesley-trantham

   added a commit that references this issue on Dec 1, 2017

   fix(E2E tests in Protractor): Change to setInterval to run outside of…

   ...

   d8599d7
6. angular-automatic-lock-bot commented on Sep 8, 2019

   

   angular-automatic-lock-botBot

   on Sep 8, 2019

   More actions

   This issue has been automatically locked due to inactivity.
   Please file a new issue if you are encountering a similar or related problem.

   Read more about our automatic conversation locking policy.

   _{This action has been performed automatically by a bot.}
7. angular-automatic-lock-bot

   locked and limited conversation to collaborators on Sep 8, 2019