Book Image

Angular Test-Driven Development - Second Edition

By : Md. Ziaul Haq
Book Image

Angular Test-Driven Development - Second Edition

By: Md. Ziaul Haq

Overview of this book

<p>This is a complete guide that shows you testing techniques with Karma that will help you perform unit testing and end-to-end testing with Protractor. It will show you how to optimize your Angular development process using TDD techniques and ensure your final project is free of bugs. All examples in this book are based on Angular v2 and are compatible with Angular v4.</p> <p>We start by reviewing the TDD life cycle, TDD in the context of JavaScript, and various JavaScript test tools and frameworks. You will see how Karma and Protractor can make your life easier while running JavaScript unit tests. We will enable you to build a test suite for an Angular application and build a testable medium-to-large scale Angular application by handling REST API data.</p> <p>Building on the initial foundational aspects, we move on to testing for multiple classes, partial views, location references, CSS, and the HTML element. In addition, we will explore how to use a headless browser with Karma. We will also configure a Karma file to automate the testing and tackle elements of Angular (components, services, classes, and broadcasting) using TDD.</p> <p>Finally, you will find out how to pull data using an external API, set up and configure Protractor to use a standalone Selenium server, and set up Travis CI and Karma to test your application.</p>
Table of Contents (15 chapters)
Angular Test-Driven Development
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface

Top-down versus bottom-up approach - which one do we use?


From a development perspective, we have to determine where to start. The approaches that we will discuss in this book are as follows:

  • The bottom-up approach: With this approach, we think about the different components we will need (class, service, module, and so on) and then pick the most logical one and start coding.

  • The top-down approach: With this approach, we work from the user scenario and UI. We then create the application around the components in the application.

There are merits to both these approaches, and the choice can be based on your team, the existing components, requirements, and so on. In most cases, it is best for you to make the choice based on the least resistance.

In this chapter, the approach of the specification is top-down; everything is laid out for you from the user scenario and will allow you to organically build the application around the UI.