This is the second and last part of the series on replacing Protractor with Cypress. This article gives you a quick introduction and show you potential pitfalls.
On 24th April, Angular announced the deprecation of their E2E testing tool protractor. It was unclear if there will be a successor or if Angular delegates this to its users. At the time of this writing, WebDriver.IO, TestCafé and Cypress came up with schematics for the Angular CLI.
In this article, I will provide a short overview over the differences between the various E2E frameworks, argue why you should use Cypress and – in the second part – help you with the first steps.
If you prefer watching over reading, then this recording of my talk is for you:
In this article, I will show you the quickest way to publish a Java library to Maven Central.
In this article, I want to share the 5 basic pillars I believe a successful programming course should build upon.
Introducing SneakyThrow. A Java library to ignore Checked Exceptions.
In this article, I show how to ignore checked exceptions in Java. I will cover the rationale, common patterns and list some libraries created for this use case.
I want to make the case that good design makes exceptions the exception — something so wrong that the user can not do anything about it. In most cases, the best approach will be to show the user a single, generic message when exceptions occur.
In this article I show how well-meant null checks and default values can cause serious bugs.