Book Image

Mastering Angular 2 Components

By : Gion Kunz
Book Image

Mastering Angular 2 Components

By: Gion Kunz

Overview of this book

<p>Through this book, you will learn how to use Angular 2 and its component-based architecture in order to develop modern user interfaces. A new holistic way of thinking about UI development will be established throughout this book, and you will discover the power of Angular 2 components through many examples. This book is based on Release Candidate 1(RC1) of Angular 2.</p> <p>On this journey, you'll discover the benefits of component-based user interfaces over the classical MVC design. Also, you will get a chance to compare a classical MVC with a component-based approach and understand the challenges of modern user interfaces. You will learn the very basics of the required core technologies and the setup needed to get going with Angular 2, and progressively enhance your understanding of Angular 2 components by working on the example application.</p> <p>After reading the book and following the example application, you will have built a small-to-mid-sized application with Angular 2 using a component-based UI architecture.</p>
Table of Contents (19 chapters)
Mastering Angular 2 Components
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

An introduction to Jasmine


Jasmine is a very simple testing framework, which comes with an API that allows you to write Behavior-driven Development (BDD) style tests. BDD is an agile software development process of defining specifications in a written format.

In BDD, we define that an agile user story consists of multiple scenarios. These scenarios closely relate to or even replace the acceptance criteria of a story. They define requirements on a higher level, and they are mostly written narrative. Each scenario then consists of three parts:

  • Given: This part is used to describe the initial state of the scenario. The test code is where we perform all the setup that is needed to execute the test scenario.

  • When: This part reflects the changes that we perform to the system under test. Usually, this part consists of some API calls and actions that reflect the behavior of a user of the system.

  • Then: This part specifies what the system should look like after the given state and the changes applied...