unit testing - How do I test an $httpBackend POST error state with AngularJS / Karma? -


i'm trying write unit test angular service , here's function in service:

login = function(authobject) {   deferred = $q.defer();    $http({     url: '/api/v1/session/create',     method: 'post',     data: authobject   }).success(function(response) {     var user;     if (response.status === 'ok' && response.user && response.authenticated === true) {       user = response.user;     }     return deferred.resolve(response);   }).error(function(data) {     deferred.reject(data);     return $state.go('api_error');   });   return deferred.promise; };

i can test success case like:

it('should go api error state', function() {   var authobject;   authobject = {     username: 'a@b.com',     password: 'c'   };   $httpbackend.expectpost('/api/v1/session/create').respond(somedata);    userservice.login(authobject).then(function(response) {     return console.log("not error", response);   }, function(response) {     return console.log("error", response);   });   return expect($state.go).tohavebeencalledwith('api_error'); });

that works fine, if do: $httpbackend.expectpost('/api/v1/session/create').respond(500, 'error');, error case doesn't called. doing wrong?

in order .then() error callback called, previous promise in chain should result in error (e.g. throw exception) or rejected.

returning 500 cause error callback in login() method called, since callback neither throws error nor gets rejected, chained error callback won't called.

e.g. changing: 

}).error(function(data) {     deferred.reject(data);     return $state.go('api_error'); });

to: 

}).error(function(data) {     return deferred.reject(data);     //return $state.go('api_error'); });

would work (but doesn't want :d).

i not familiar ui-router, in case possible $state.go() aborts current execution chain, not sure following work:

}).error(function(data) {     $state.go('api_error');     return deferred.reject(data); });

Comments

Post a Comment

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

request animation frame stops working when exiting fullscreen clicking on original space's safari window. fine if fullscreen mode canceled escape key or calling cancelfullscreen(). steps reproduce: open https://dl.dropboxusercontent.com/u/769042/prezi/safari-fullscreen.html click "draw raf", kittie appears click "fullscreen", go fullscreen click "draw raf", kittie appears go space original safari was, showing "click exit fullscreen mode", click anywhere, out fullscreen click "draw raf", nothing happens what handling click calling: window.requestanimationframe(draw); which draws on canvas context: function draw() { ctx.drawimage(img, math.random()*500|0, math.random()*400|0, 100, 100); } i checked .hidden , .visibilitystate, updated correctly. tested on osx 10.9.3, safari 7.0.4 (9537.76.4). has workaround/solution other switching old settimeout? this sounds webkit bug 88940 : using reque...
Read more

jsf - How to ajax update an item in the footer of a PrimeFaces dataTable? -

this visual of table have: +---------+------------+-------------------+ | header1 | header2 | header3 | +---------+------------+-------------------+ | row | input | calc'ed output | | row b | input b | calc'ed output b | | etc.. | etc.. | etc.. | +---------+------------+-------------------+ | total: total calc'ed output | +------------------------------------------+ and stripped-down code: <p:datatable id="mytable" value="#{mybean.somelist}" var="currentitem"> <p:column headertext="header1"> <h:outputtext value="#{currentitem.name}" /> </p:column> <p:column headertext="header2"> <pe:inputnumber value="#{currentitem.inputval}"> <p:ajax event="change" listener="#{mybean.changelistener}" update="outputval outputtotal...
Read more

django - CSRF verification failed. Request aborted. CSRF cookie not set -

error: reason given failure: csrf cookie not set. in general, can occur when there genuine cross site request forgery, or when django's csrf mechanism has not been used correctly. post forms, need ensure: browser accepting cookies. view function uses requestcontext template, instead of context. in template, there {% csrf_token %} template tag inside each post form targets internal url. if not using csrfviewmiddleware, must use csrf_protect on views use csrf_token template tag, accept post data. you're seeing section of page because have debug = true in django settings file. change false, , initial error message displayed. can customize page using csrf_failure_view setting. did find, nothing helped, must foolish(( my template <form method="post">{% csrf_token %} {% field in form %} <div class="control-group"> {{ field }} </div> {% endfor %} <input type=...
Read more