In February 2017, they merged a PR adding this feature, they released in April 2017. so to spy on getters/setters you use: const spy = spyOnProperty(myObj, ‘myGetterName’, ‘get’); where myObj is your instance, ‘myGetterName’ is the name of that one defined in your class as get myGetterName() {} and the third param is the type … Read more
Ok figured this one out a while ago, sorry I forgot I had posted here. We basically created a configuration array in another file, (though this is not necessary, just makes the code easier to read) and then pulled that array into a var right above the test we wanted to repeat. Then we surrounded … Read more
If you’re just needing some testing on event firing and catching, this is how I do it. For ensuring that a certain event gets fired ($emit-ed or $broadcast-ed), a spy is the way to go. You need a reference to the scope that will be calling the $emit or $broadcast, and then just to do … 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(…),
There might be multiple reasons for that and it is going to be a guessing game anyway. it could be that there is an another element matching the .login-button locator and you are clicking a different element. Let’s improve the locator: element(by.css(“.login-form .login-button”)).click(); wait for the element to be clickable: var EC = protractor.ExpectedConditions; element(by.model(‘credentials.username’)).sendKeys(‘RET02’); … Read more
If you are defining your function: function test() {}; Then, this is equivalent to: window.test = function() {} /* (in the browser) */ So spyOn(window, ‘test’) should work. If that is not, you should also be able to: test = jasmine.createSpy(); If none of those are working, something else is going on with your setup. … Read more
You can also just use the RouterTestingModule and just spyOn the navigate function like this… import { TestBed } from ‘@angular/core/testing’; import { RouterTestingModule } from ‘@angular/router/testing’; import { Router } from ‘@angular/router’; import { MyModule } from ‘./my-module’; import { MyComponent } from ‘./my-component’; describe(‘something’, () => { let fixture: ComponentFixture<LandingComponent>; let router: Router; … Read more
I’m not sure why the way you did it doesn’t work, but I usually do it with the spyOn function. Something like this: describe(‘Testing remote call returning promise’, function() { var myService; beforeEach(module(‘app.myService’)); beforeEach(inject( function(_myService_, myOtherService, $q){ myService = _myService_; spyOn(myOtherService, “makeRemoteCallReturningPromise”).and.callFake(function() { var deferred = $q.defer(); deferred.resolve(‘Remote call result’); return deferred.promise; }); } it(‘can … 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
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 … Read more