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

Testing a component


Before getting into the specifications and the mindset of the feature being delivered, it is important to understand the fundamentals of testing a component class. A component in Angular is a key feature used in most applications.

Getting ready to go

Our sample application (quickstart) has some very basic test specs for unit and end-to-end testing. We will start the TDD approach from the very beginning, so we will not use any of the test specs and the existing component's code in our implementation.

For that, what can we do is just clean up this sample application, and we will just keep the folder structure and application bootstrap files.

So, first of all, we will have to remove the unit test file (app.component.spec.ts) and end-to-end test files (app.e2e-spec.ts). These are two test specs that existed in the application structure.

Setting up a simple component test

When testing a component, it's important to inject the component into the test suite and then initiate the component...