How do you Access the Arguments of a Jasmine spy?

Posted At : May 9, 2018 9:00 AM | Posted By : Jeffry Houser
Related Categories: Professional, Jasmine

I've been writing unit tests for clients. It's a nice change to finally have some clients who care about such things.

I have this Angular method that creates an object, then emits an event.

The method was something like this:

onButtonClick() {

let eventParameters = {};

// do stuff

this.eventEmitter.emit(eventParameters);
}

I want to be compare the properties of the eventParameters argument with what I expect them to be. However, I have no way to access the eventParameters directly because it is local to the method. My first thought was to do something like this:

spyOn(component,'onButtonClick').and.returnValue(myOwnEventParametersObject)

However my intent was to test the code inside the method, whereas this bypasses calling the method altogether. That would not suffice.

So, how'd I do it?

First, I saved an instance to the Spy:

const mySpy = spyOn(component.eventEmitter, 'emit');

I can drill down into this spy to get the results of the most recent call:

const recentCallArgs = mySpy.calls.mostRecent().args[0];

Once I have the argument object, I can introspect it to compare the arguments created by the method with what I expected them to be.

expect(recentCallArgs.value).toBe('value');

TaDa!

Comments (0) |

Send |

del.icio.us |

Digg It! |

Linking Blogs | 327 Views

How do I test Observable.timer?

Posted At : April 18, 2018 9:00 AM | Posted By : Jeffry Houser
Related Categories: Professional, Jasmine, Karma

This was trickier than I thought, which is why I'm writing a blog post about it. I'm writing some code which uses an FakeAsync Zone nor RxJS TestScheduler.

The timer() call returns an Observable, so I decided to create one myself which gave me complete control.

let timerObserver :Observer<any>;
beforeEach(() => {
spyOn(Observable, 'timer').and.returnValue(Observable.create(
(observer =>{
timerObserver = observer;
})
));
});

I created an Observer object. This is the internal logic that makes the Observable resolve itself. I used spyOn() inside a beforeEach() to have the unit testing framework return my own Observable and ignore the library code. I save the observer for later usage.

Now, when I'm testing I can resolve the timer immediately:

it('Some Test',()=>{
// do stuff if needed

// trigger the fake timer using the Observer reference
timerObserver.next('');
timerObserver.complete();

//
expect(somethingToHappenAfterTimerCompletes).toHaveBeenCalled();
});

I spent more time banging my head on this than I thought I would, and I hope this helps you.

Comments (0) |

Send |

del.icio.us |

Digg It! |

Linking Blogs | 512 Views

Running Unit Tests from IntelliJ

Posted At : March 31, 2018 9:25 PM | Posted By : Jeffry Houser
Related Categories: Professional, Jasmine, IntelliJ, Karma

I put together this screencast about running Unit Tests using IntelliJ.

Comments (0) |

Send |

del.icio.us |

Digg It! |

Linking Blogs | 402 Views

How do you tell Jasmine to run a single test?

Posted At : March 22, 2018 9:00 AM | Posted By : Jeffry Houser
Related Categories: Professional, Jasmine

Last week I wrote about how to tell Jasmine to ignore a unit test. This week I'll tell you how to ignore every unit test except one.

To use last week's example, a normal unit test would be something like this:

it("True is True", () =>{
expect("True").toBe("True");
});

A normal test suite will include lots of tests spread out through lots of files. You can focus a unit test using fit(). This tells Jasmine to only run the unit test with the 'f':

fit("True is True", () =>{
expect("True").toBe("True");
});

other unit tests will be ignored. This can be a great use when testing something new.

You can use the same thing to disable a full suite with fdescribe() instead of describe:

fdescribe("Some Test Suite"()=>{
it("True is True", () =>{
expect("True").toBe("True");
});
});

This type of stuff can be pretty handy if you're running your tests via command lines.

Comments (0) |

Send |

del.icio.us |

Digg It! |

Linking Blogs | 383 Views

How do I tell Jasmine to ignore a test?

Posted At : March 14, 2018 11:20 AM | Posted By : Jeffry Houser
Related Categories: Professional, Jasmine

Today I learned you can tell Jasmine to ignore a unit test. A normal unit test would be something like this:

it("True is True", () =>{
expect("True").toBe("True");
});

When running a unit test file with this inside the test will run., You could comment it out if you wish, but that can get confusing for larger unit tests with embedded oomments. Instead you can use xit() instead of it():

xit("True is True", () =>{
expect("True").toBe("True");
});

Now when you run your unit test, this test will be marked as viewed as pending and will not be run.

You can use the same thing to disable a full suite with describe():

xdescribe("Some Test Suite"()=>{
it("True is True", () =>{
expect("True").toBe("True");
});
});

This is pretty handy, but something I overlooked when learning all about unit testing.

Comments (0) |

Send |

del.icio.us |

Digg It! |

Linking Blogs | 436 Views