jasmine Async callback was not invoked within timeout specified by jasmine DEFAULT TIMEOUT INTERVAL

Question

I have an angular service called requestNotificationChannel   app factory  requestNotificationChannel   function  rootScope         var  DELETE MESSAGE      DELETE MESSAGE         function deleteMessage id  index             rootScope  broadcast  DELETE MESSAGE     id  id  index  index                 return          deleteMessage  deleteMessage               I am trying to unit test this service using jasmine    use strict    describe  Request Notification Channel   function         var requestNotificationChannel  rootScope  scope       beforeEach function  requestNotificationChannel             module  messageAppModule             inject function  injector   requestNotificationChannel                 rootScope    injector get   rootScope                scope   rootScope  new                requestNotificationChannel    requestNotificationChannel                       spyOn rootScope    broadcast                  it  should broadcast delete message notification   function done             requestNotificationChannel deleteMessage 1  4           expect rootScope  broadcast  toHaveBeenCalledWith   DELETE MESSAGE      id  1  index  4             done                         I read about the Asynchronous Support in Jasmine  but as I am rather new to unit testing with javascript couldn t make it work   I am receiving an error       Async callback was not invoked within timeout specified by jasmine DEFAULT TIMEOUT INTERVAL   and my test is taking too long to execute  about 5s    Can somebody help me providing working example of my code with some explanation

User · Answer

This is more of an observation than an answer, but it may help others who were as frustrated as I was.

I kept getting this error from two tests in my suite. I thought I had simply broken the tests with the refactoring I was doing, so after backing out changes didn't work, I reverted to earlier code, twice (two revisions back) thinking it'd get rid of the error. Doing so changed nothing. I chased my tail all day yesterday, and part of this morning without resolving the issue.

I got frustrated and checked out the code onto a laptop this morning. Ran the entire test suite (about 180 tests), no errors. So the errors were never in the code or tests. Went back to my dev box and rebooted it to clear anything in memory that might have been causing the issue. No change, same errors on the same two tests. So I deleted the directory from my machine, and checked it back out. Voila! No errors.

No idea what caused it, or how to fix it, but deleting the working directory and checking it back out fixed whatever it was.

Hope this helps someone.

User · Answer

In my case  this error was caused by improper use of  fixture detectChanges    It seems this method is an event listener  async  which will only respond a callback when changes are detected  If no changes are detected it will not invoke the callback  resulting in a timeout error  Hope this helps

User · Answer

As noted by  mastablasta  but also to add that if you call the  done  argument or rather name it completed you just call the callback completed   in your test when it s done       this block signature will trigger async behavior  it  should work   function done        do stuff and then call done      done            this block signature will run synchronously it  should work   function

User · Answer

You also get this error when expecting something in the beforeAll function    describe        function           beforeAll function                           expect element by css   id  title      isDisplayed    toBe true                it  should successfully       function

User · Answer

You can use karma-jasmine plugin to set the default time out interval globally   Add this config in karma conf js   module exports   function config      config set       client          jasmine            timeoutInterval  10000

User · Answer

What I did was  Added Updated the following code   framework   jasmine   jasmineNodeOpts            Jasmine default timeout     defaultTimeoutInterval  60000      expectationResultHandler passed  assertion                  do something

User · Answer

It looks like the test is waiting for some callback that never comes  It s likely because the test is not executed with asynchronous behavior  First  see if just using fakeAsync in your  quot it quot  scenario  it  should do something   fakeAsync      gt     You can also use flush   to wait for the microTask queue to finish or tick   to wait a specified amount of time

User · Answer

Works after removing the scope reference and the function arguments    use strict    describe  Request Notification Channel   function         var requestNotificationChannel  rootScope       beforeEach function             module  messageAppModule             inject function  injector   requestNotificationChannel                 rootScope    injector get   rootScope                requestNotificationChannel    requestNotificationChannel                      spyOn rootScope    broadcast                  it  should broadcast delete message notification with provided params   function             requestNotificationChannel deleteMessage 1  4           expect rootScope  broadcast  toHaveBeenCalledWith   DELETE MESSAGE      id  1  index  4

User · Answer

Instead of  beforeEach      gt        use  beforeEach fakeAsync      gt

User · Answer

Having an argument in your it function  done in the code below  will cause Jasmine to attempt an async call     this block signature will trigger async behavior  it  should work   function done                  this block signature will run synchronously it  should work   function                  It doesn t make a difference what the done argument is named  its existence is all that matters  I ran into this issue from too much copy pasta   The Jasmine Asynchronous Support docs note that argument  named done above  is a callback that can be called to let Jasmine know when an asynchronous function is complete  If you never call it  Jasmine will never know your test is done and will eventually timeout

User · Answer

If you have an argument  done  in the it function try to remove it as well it s call within the function itself   it  should broadcast delete message notification   function   done - gt  YOU SHOULD REMOVE IT            requestNotificationChannel deleteMessage 1  4       expect rootScope  broadcast  toHaveBeenCalledWith   DELETE MESSAGE      id  1  index  4            done    - gt  YOU SHOULD REMOVE IT

User · Answer

jasmine DEFAULT TIMEOUT INTERVAL   100000   Keeping this in the block solved my issue   it          gt     jasmine DEFAULT TIMEOUT INTERVAL   100000

User · Answer

Don t use done  just leave the function call empty

User · Answer

Even for async tests  there is a timeout that goes off in this cases  You can work around this error by increasing the value for the limit timeout to evaluate an async Jasmine callback  describe  Helper   function          var originalTimeout       beforeEach function             originalTimeout   jasmine DEFAULT TIMEOUT INTERVAL          jasmine DEFAULT TIMEOUT INTERVAL   1000000               afterEach function           jasmine DEFAULT TIMEOUT INTERVAL   originalTimeout               it  Template advance   function doneFn              ajax               url   public your-end-point mock json               dataType   json               success  function  data  response                       Here your expected using data                 expect 1  toBe 1                  doneFn                               error  function  data  response                       Here your expected using data                 expect 1  toBe 1                  doneFn                                            Source  http   jasmine github io 2 0 introduction html section-42

User · Answer

import   fakeAsync  ComponentFixture  TestBed   from   angular core testing     use fakeAsync   beforeEach fakeAsync       gt       your code          describe  Intilalize        gt            it  should have a defined component   fakeAsync      gt                createComponent                expect  AddComponent ngOnInit  toBeDefined

User · Answer

This error started out of the blue for me  on a test that had always worked  I couldn t find any suggestions that helped until I noticed my Macbook was running sluggishly  I noticed the CPU was pegged by another process  which I killed  The Jasmine async error disappeared and my tests are fine once again   Don t ask me why  I don t know  But in my circumstance it seemed to be a lack of system resources at fault

User · Answer

This error can also be caused by leaving out inject when initializing a service factory or whatever  For example  it can be thrown by doing this   var service  beforeEach function  TestService         service    TestService         To fix it just wrap the function with inject to properly retrieve the service   var service  beforeEach inject function  TestService         service    TestService

[javascript] jasmine: Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL

Examples related to javascript

Examples related to angularjs

Examples related to unit-testing

Examples related to asynchronous

Examples related to jasmine