In Jasmine versions 3.0 and above you can use withArgs describe(‘my fn’, function() { it(‘gets user name and ID’, function() { spyOn(externalApi, ‘get’) .withArgs(‘abc’).and.returnValue(‘Jane’) .withArgs(‘123’).and.returnValue(98765); }); }); For Jasmine versions earlier than 3.0 callFake is the right way to go, but you can simplify it using an object to hold the return values describe(‘my fn’, … Read more
Just did the test and it works with toEqual please find my test: http://jsfiddle.net/7q9N7/3/ describe(‘toEqual’, function() { it(‘passes if arrays are equal’, function() { var arr = [1, 2, 3]; expect(arr).toEqual([1, 2, 3]); }); }); Just for information: toBe() versus toEqual(): toEqual() checks equivalence. toBe(), on the other hand, makes sure that they’re the exact … Read more
I discovered that Jasmine allows you to prefix describe and it methods with an f (for focus): fdescribe and fit. If you use either of these, Karma will only run the relevant tests. To focus the current file, you can just take the top level describe and change it to fdescribe. If you use Jasmine … Read more
I hope you’ve installed – npm install –save-dev @types/jasmine Then put following import at the top of the hero.spec.ts file – import ‘jasmine’; It should solve the problem.
The rewire module is definitely the answer. Here’s my code for accessing an unexported function and testing it using Mocha. application.js: function logMongoError(){ console.error(‘MongoDB Connection Error. Please make sure that MongoDB is running.’); } test.js: var rewire = require(‘rewire’); var chai = require(‘chai’); var should = chai.should(); var app = rewire(‘../application/application.js’); var logError = app.__get__(‘logMongoError’); … Read more
Each of your .spec.ts file have all its tests grouped in describe block like this: describe(‘SomeComponent’, () => {…} You can easily run just this single block, by prefixing the describe function name with f: fdescribe(‘SomeComponent’, () => {…} If you have such function, no other describe blocks will run. Btw. you can do similar … Read more
What I do when I wonder something like the question asked here is go to the source. toBe() expect().toBe() is defined as: function toBe() { return { compare: function(actual, expected) { return { pass: actual === expected }; } }; } It performs its test with === which means that when used as expect(foo).toBe(true), it … Read more
I’m with you, even though it’s a good goal to “only unit test the public API” there are times when it doesn’t seem that simple and you feel you are choosing between compromising either the API or the unit-tests. You know this already, since that’s exactly what you’re asking to do, so I won’t get … Read more
For primitive types (e.g. numbers, booleans, strings, etc.), there is no difference between toBe and toEqual; either one will work for 5, true, or “the cake is a lie”. To understand the difference between toBe and toEqual, let’s imagine three objects. var a = { bar: ‘baz’ }, b = { foo: a }, c … Read more
Try using an anonymous function instead: expect( function(){ parser.parse(raw); } ).toThrow(new Error(“Parsing is not possible”)); you should be passing a function into the expect(…) call. Your incorrect code: // incorrect: expect(parser.parse(raw)).toThrow(new Error(“Parsing is not possible”)); is trying to actually call parser.parse(raw) in an attempt to pass the result into expect(…),