Writing a minimum viable end-to-end test suite for a simple application
End-to-end testing (or e2e for short) is on the other end of the spectrum as far as unit testing is concerned. The entire application exists as a black box, and the only controls at your disposal—for these tests—are actions the user might take inside the browser, such as firing click events or navigating to a page. Similarly, the correctness of tests is only verified by inspecting the state of the browser and the DOM itself.
More explicitly, an end-to-end test will (in some form) start up an actual instance of your application (or a subset of it), navigate to it in an actual browser, do stuff to a page, and look to see what happens on the page. It's pretty much as close as ...
Get Angular 2 Cookbook now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
