Comments on: The Complete Guide to Angular Testing and a Weird Trick for Faster Unit Tests (2020)

By: A Curated List of Angular Resources - Hapax Legomenon

A Curated List of Angular Resources - Hapax Legomenon — Tue, 10 Aug 2021 02:19:15 +0000

[…] The Complete Guide to Angular Testing and a Weird Trick for Faster Unit Tests (2019) – Christian L… […]

By: The Most Common Cypress Mistakes – Christian Lüdemann

The Most Common Cypress Mistakes – Christian Lüdemann — Tue, 09 Jun 2020 16:01:14 +0000

[…] Unit testing business logic critical to use cases. These files are critical to use cases we want to test them with 100% coverage. That means 100% coverage on services and pure functions containing business logic […]

By: Naos

Naos — Thu, 23 Jan 2020 11:40:00 +0000

A good read, thank you for sharing. Did you ever explore implementing integration tests using Protractor, headless browser and a mocked backend in a similar way the backend services integration tests are written by mocking HTTP calls with for eg. Wiremock ? I thought about giving it a go as they would really test the whole app integrated, I am not sure about flakiness though. I thought about using the mockserver, which I am already using to be able to run the app locally.

By: Kalule Arthur

Kalule Arthur — Tue, 21 Jan 2020 20:13:00 +0000

Thanks for sharing. I found this helpful.

By: The Ten Commandments of Angular Development – Christian Lüdemann

The Ten Commandments of Angular Development – Christian Lüdemann — Tue, 05 Nov 2019 20:43:38 +0000

[…] Read more about my testing guidelines here. […]

By: Why I Moved from Protractor to Cypress and the 7 Steps to Cypress E2E Testing Success – Christian Lüdemann

Wed, 03 Jul 2019 17:05:28 +0000

[…] the testing pyramid to split the tests between approximately: 80 % of the tests should be unit tests, 15 % is […]

By: The Three Building Blocks of Elite Angular Teams – Christian Lüdemann

The Three Building Blocks of Elite Angular Teams – Christian Lüdemann — Tue, 14 May 2019 17:02:45 +0000

[…] unit test […]

By: End-to-end Testing With Protractor: A Pragmatic Guide Get Started In Your Team – Christian Lüdemann IT

Sun, 25 Nov 2018 18:01:11 +0000

[…] cover the system’s functionality and which can/should be automated. My recommendation from my testing guide is that you should follow the testing pyramid by having unit, integration and end-to-end tests […]

By: All You Need to Know About Mocking Angular Tests – Christian Lüdemann IT

All You Need to Know About Mocking Angular Tests – Christian Lüdemann IT — Sun, 28 Oct 2018 18:04:18 +0000

[…] because it pays for itself in the form of easier maintenance and fewer errors. As I explained in my guide to Angular testing unit tests should be the bedrock of your test coverage as they are the cheapest to create. […]

By: Visual Regression Testing with Protractor – Christian Lüdemann IT

Visual Regression Testing with Protractor – Christian Lüdemann IT — Sun, 14 Oct 2018 17:44:33 +0000

[…] the site works, but on the other site are the flakiest and most expensive to maintain when doing testing in an Angular app. Also, by default, you have to manually code every assertion that the end-to-end test should do, […]