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

Making the test better


There are a couple of things that were discussed in this chapter that need further clarification. These include the following:

  • Where is the asynchronous logic?

  • How do we really implement TDD with end-to-end tests?

Async magic

In the preceding tests, we saw some magic that you might be questioning. Here are some of the magic components that we glanced over:

  • Loading a page before test execution

  • Assertion on elements that get loaded in promises

Loading a page before test execution

In the previous test, we used the following code to specify that the browser should point to the home page:

browser.get(''); 

The preceding command will launch the browser and navigate to the baseUrl location. Once the browser reaches the page, it will have to load Angular and then implement the Angular-specific functions. Our tests don't have any wait logic, and this is part of the beauty of Protractor with Angular. The waiting for page loading is already built into the framework for us. Our tests...