Book Image

Test-Driven JavaScript Development

By : Ravi Kumar Gupta
Book Image

Test-Driven JavaScript Development

By: Ravi Kumar Gupta

Overview of this book

Initially, all processing used to happen on the server-side and simple output was the response to web browsers. Nowadays, there are so many JavaScript frameworks and libraries created that help readers to create charts, animations, simulations, and so on. By the time a project finishes or reaches a stable state, so much JavaScript code has already been written that changing and maintaining it further is tedious. Here comes the importance of automated testing and more specifically, developing all that code in a test-driven environment. Test-driven development is a methodology that makes testing the central part of the design process – before writing code developers decide upon the conditions that code must meet to pass a test. The end goal is to help the readers understand the importance and process of using TDD as a part of development. This book starts with the details about test-driven development, its importance, need, and benefits. Later the book introduces popular tools and frameworks like YUI, Karma, QUnit, DalekJS, JsUnit and goes on to utilize Jasmine, Mocha, Karma for advanced concepts like feature detection, server-side testing, and patterns. We are going to understand, write, and run tests, and further debug our programs. The book concludes with best practices in JavaScript testing. By the end of the book, the readers will know why they should test, how to do it most efficiently, and will have a number of versatile tests (and methods for devising new tests) to get to work immediately.
Table of Contents (16 chapters)
Test-Driven JavaScript Development
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface
Index

Applying proper processes


In Chapter 1, Overview of TDD, and Chapter 2, Testing Concepts, you learned about the TDD life cycle. Processes mentioned in the following section will be helpful to make successful implementation of TDD.

Making sure that tests are written before starting implementation

It is an extremely helpful practice to write test cases for all the requirements before the code is implemented, as it ensures that the code, hence implemented, covers all the requirements. This process helps to understand requirements in details to any developer before starting coding for respective module. Understanding the requirements in detail, will make sure that the implementation done for any module is accurate and properly written.

Let's take an example of change request for any project. In that case, we should first write a test before starting the implementation so that we will get an idea of the number of existing requirements that a change request is affecting. If this is not followed properly...