Jasmine is a little Behavior-Driven Development framework, created by the guys at Pivotal Labs to allow you to write automated JavaScript unit tests.
But before we can go any further, first we need to get some fundamentals, starting with what is a test unit.
A test unit is a piece of code that tests a functionality unit of the application code. But sometimes it can be tricky to understand what a functionality unit can be, so for that reason, Dan North came up with a solution in the form of Behavior-Driven Development (BDD), which is a rethink of Test-Driven Development (TDD).
In traditional unit testing practice, the developer is left with no guidelines on how to start in the process of testing, what to test, how big a test should, be or even how to call a test.
To fix these problems, Dan took the concept of user stories from the standard agile construct, as a model on how to write tests.
For example, a music player application could have an acceptance criterion like:
Given a player, when the song has been paused then it should indicate that the song is currently paused.
As you can see, this acceptance criterion is written following an underlying pattern:
given [an initial context]
when [an event occurs]
then [ensure some outcome]
In Jasmine this translates into a very expressive language that allows tests to be written in a way that reflects actual business values. The above acceptance criterion written as a Jasmine test unit would be:
describe("Player", function() {
describe("when song has been paused", function() {
it("should indicate that the song is paused", function() {
});
});
});You can see how the criterion translates well into the Jasmine syntax. In the next chapter we will get into the details of how these functions work.
With Jasmine, as with other BDD frameworks, each acceptance criterion directly translates to a test unit. For that reason, each test unit is usually called a spec, short for specification. During the course of this book, we will be using this terminology.