AutomationdesignFailing tests

Abstraction and Testing – UI Component Testing

Abstraction is one of the founding principles of software. In this post I describe UI component testing breaks through abstraction and causes fragile tests.

Interface and the sides

AutomationdesignFailing tests

Abstraction and Testing – The Other Side

Abstraction is one of the founding principles of software. In this post I describe how interfaces are just one side of the problem in testing.

mocking and abstraction in testing

AutomationClean codedesignFailing tests

Abstraction and Testing – Mocks

Abstraction is one of the founding principles of software. In this post I describe how mocks break abstraction and its effect on testing.

Abstraction in testing

AutomationClean codedesignFailing tests

Abstraction and Testing – Intro

Abstraction is one of the founding principles of software. It allows us to simplify ideas, code and usage. It also impacts testing directly.

Failing testsQualityTesting

The Truth About Fragile Tests

We call fragile tests like that because that’s what we see when they break. Instead, we should probably focus on the production code that breaks them.

Gil Zilberfeld explains how Unit tests (and integration tests) not only check that the code works, but are also hold useful information when they fail.

Failing testsWriting Tests

Triangulation: The Other Role Of Unit Tests

“Why do we need unit tests?” Seems like a silly question. We want to check if something is working, right? Let’s dig deeper, though. At the time of writing, if we’re using test-first or TDD, we’re designing interfaces, apply usage… Continue Reading…