StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
15600821
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-03-24T16:12:54.877
FavoriteCount
0
LastActivityDate
2015-08-12T09:23:25.587
LastEditDate
2015-08-12T09:23:25.587
LastEditorUserId
408557
OwnerUserId
408557
ParentId
13421869
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Maybe you could create a custom wrapper mock around $httpBackend that handles your special needs. In detail, Angular overwrites components of the same name with a last-come first-served strategy, this means that the order you load your modules is important in your tests. When you define another service with the same name and load it after the first one, the last one will be injected instead of the first one. E.g.: <pre><code>apptasticMock.service("socket", function($rootScope){ this.events = {}; // Receive Events this.on = function(eventName, callback){ if(!this.events[eventName]) this.events[eventName] = []; this.events[eventName].push(callback); } // Send Events this.emit = function(eventName, data, emitCallback){ if(this.events[eventName]){ angular.forEach(this.events[eventName], function(callback){ $rootScope.$apply(function() { callback(data); }); }); }; if(emitCallback) emitCallback(); } }); </code></pre> This service offers the exact same interface and behaves exactly like the original one except it never communicates via any socket. This is the service we want to use for testing. With the load sequence of angular in mind, the tests then look like this: <pre><code>describe("Socket Service", function(){ var socket; beforeEach(function(){ module('apptastic'); module('apptasticMock'); inject(function($injector) { socket = $injector.get('socket'); }); }); it("emits and receives messages", function(){ var testReceived = false; socket.on("test", function(data){ testReceived = true; }); socket.emit("test", { info: "test" }); expect(testReceived).toBe(true); }); </code></pre> }); The important thing here is that <code>module('apptasticMock')</code> gets executed after <code>module('apptastic')</code>. This overwrites the original socket implementation with the mocked one. The rest is just the normal dependency injection procedure. <a href="http://southdesign.de/blog/mock-angular-js-modules-for-test-di.html" rel="nofollow">This article I wrote</a> could be interesting for you, as it goes into further details.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to mock an function of an Angular service in Jasmine
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USThomas Fankhauser
UserOwnerUserId
1. USThomas Fankhauser
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.