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

Follow proper rules to define test cases


Properly defined test cases gives a better view of the code, and developers can easily find what they want to find in the code. Many tools also need proper naming conventions to be followed. There are so many naming conventions techniques available out of which we will see a few techniques. It is better to follow some naming conventions than nothing, like the saying "something is better than nothing."

Let's take an example of a project. If it is mandatory for all users to follow the same naming conventions, everyone will have to follow the same standard. When it comes to module integration or to understand the code written by other developers, it's easier to follow the flow of system.

Make test case names more readable

The main benefit of following this practice is that it avoids packaging test code with production packages. Even many build tools want us to specify tests in some specific source directory to identify test at runtime. Make sure that you...