Book Image

Jasmine Cookbook

By : Munish Kumar
Book Image

Jasmine Cookbook

By: Munish Kumar

Overview of this book

Related Content you might be interested in

Current Title:

Small book image
Jasmine Cookbook
Munish Kumar
Apr, 2015 | 276 pages
No titles found
Table of Contents (16 chapters)
Jasmine Cookbook
Jasmine Cookbook
Credits
Credits
About the Author
About the Author
About the Reviewer
About the Reviewer
www.PacktPub.com
www.PacktPub.com
Preface
Preface
Free Chapter
1
Getting Started with Jasmine Framework
Getting Started with Jasmine Framework
Introduction
Writing your first Jasmine test
Adding specs to your Jasmine test
Adding expectations and matchers to the test
Applying different matchers to the Jasmine test
Applying setup and teardown functions to the Jasmine test
Using the "this" keyword
2
Jasmine with TDD and BDD Processes
Jasmine with TDD and BDD Processes
Introduction
Writing Jasmine tests using TDD and BDD processes
Creating a Jasmine test for new code using TDD and BDD
Designing Jasmine tests for existing code using TDD and BDD
Defining nested suites to write more meaningful specs
3
Customizing Matchers and Jasmine Functions
Customizing Matchers and Jasmine Functions
Introduction
Writing a Jasmine test using a custom equality tester function
Writing Jasmine tests with custom matchers
Writing Jasmine tests for exceptions
Declaring pending specs with Jasmine tests
4
Designing Specs from Requirement
Designing Specs from Requirement
Introduction
Writing useful specs by analyzing the test requirements
Implementing the Jasmine test corresponding to the specs
Applying Acceptance Criteria to the Jasmine test
Organizing Jasmine specs into groups and subgroups
5
Jasmine Spies
Jasmine Spies
Introduction
Writing Jasmine tests using the spyOn() method and special matchers for spies
Writing Jasmine tests using tracking properties
Writing Jasmine tests with your own custom spy method
Using jasmine.any and jasmine.objectContaining
Writing Jasmine tests to mock the JavaScript timeout functions
6
Jasmine with AJAX, jQuery, and Fixtures
Jasmine with AJAX, jQuery, and Fixtures
Introduction
Writing Jasmine specs for AJAX
Designing Jasmine specs with HTML and JSON fixtures
Writing Jasmine specs for jQuery
Writing Jasmine specs using custom jQuery matchers
Writing Jasmine specs for asynchronous operations using the done() function
7
Code Coverage with Jasmine Tests
Code Coverage with Jasmine Tests
Introduction
Configuring code coverage tools
Generating code coverage using karma and istanbul
Writing Jasmine specs for uncovered branches/code
Increasing code coverage for existing code
8
Jasmine with Other Tools
Jasmine with Other Tools
Introduction
Writing Jasmine tests for AngularJS
Using Jasmine with CoffeeScript
Writing Jasmine tests for Node.js
9
Developing JavaScript Apps Using Jasmine – a Real-time Scenario
Developing JavaScript Apps Using Jasmine – a Real-time Scenario
Introduction
Defining Jasmine specs corresponding to a user story
Implementing Jasmine specs with Web/HTML
Implementing Jasmine tests with a Data-Driven approach
Creating Jasmine tests for a change request
Index
Index

Introduction

Behavior-Driven Development (BDD) is a software development process based on Test-Driven Development (TDD). Before we start writing Jasmine tests using TDD and BDD, let's get a briefing of how both processes work and how they play a pivotal role in software development.

TDD is a unit testing based test-first or fail-first approach where we write the test before writing the code. Thereafter, we write the minimum amount of code just to pass the test. Finally, we refactor the code to acceptable standards. This form of approach focuses on the specification of the application, thus decreasing the probability of bugs. In other words, we can say that TDD is a defect-prevention approach that focuses on internal (code) quality.

A JavaScript application can be developed using TDD by performing the following steps:

  1. Write a failing unit test.

  2. Make the test pass.

  3. Refactor the test.

  4. Repeat the steps.

  5. When you cannot think of any more tests or there is no more scope for refactoring, you should...

Previous Section
End of Section 2
Next Section