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

Summary


In this chapter, we have seen how to write unit tests with the use of different tools such as JsUnit, QUnit, Karma, and DalekJS. You learned how can you install different tools, use them to write different tests, and finally wrote one example in each and every tool to understand them in detail.

In fact, there are so many tools available, sometimes created eventually to satisfy specific requirements, or as an improvement to some existing tool or framework. The purpose of this chapter was to showcase a variety and a couple of different syntax these tools use. The point to mention here is that despite the difference in syntax or naming conventions, almost all of the tools use assertions, actions, suits, set up, tear down, and so on.

In the next chapter, you will learn about Jasmine in more detail and understand how Jasmine works with the use of some examples.