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

Protractor tests - postmortem


It's kind of difficult to debug e2e tests as they depend on the entire ecosystem of an application. Sometimes they depend on prior actions such as login, and sometimes they depend on permissions. Another major barrier to debugging e2e is its dependency on WebDriver. As it acts differently with different operating systems and browsers, this makes it difficult to debug e2e. Besides that, it generates long error messages, which makes it difficult to separate browser related issues and test process errors.

Still, we will try to debug all e2e tests and see how that works for our case.

Types of failure

There might be various reasons for the failure of a test suite as long as it depends on WebDriver and various parts throughout the system.

Let's look at some known failure types:

  • WebDrive failure: WebDriver throws an error when a command can't be completed. For example, a browser can't get the address that's defined to help it navigate, or maybe an element is not found...