Share the intellectual wealth

From time to time, we encounter bugs in the software systems that we work on.

The way a team handles defects reveals much about how their organisation approaches quality.

So I’ve encountered this specific test case, which is quite elaborate.

The quality of software, or any product, can be viewed from different perspectives.

Today I got reminded of a great video of GeePaw Hill about the “Five Underplayed Premises Of TDD” . 1.

This is the final installment of a three-part series about contract tests.

In the previous blog post, we’ve discussed the rationale behind contract tests.

One of my favorite awesome talks of all time is Integrated Tests Are a Scam by J.B.

Back in 2003, Brian Marick wrote an excellent article series about agile testing.

I’ve heard that you’ve been working on this new feature for the payroll system based on the newly voted government legislation?

In the previous blog post, we discussed how to use Approval Tests for verifying generated PDF documents.

A while back I was confronted with a part of a legacy system that generates PDF documents.

Most test frameworks out there have the capability to disable tests.

I’m very happy to announce that Writing Maintainable Unit Tests is also available as a paper book.

Do you have 15 minutes to spare?

I’m very happy to announce that I’ve finished writing my first book Writing Maintainable Unit Tests.

Using inheritance for test classes is not a desirable thing as it introduces a number of issues.

Once in a while I get asked the question whether one should write solitary tests for logging functionality.

Previously we discussed why solitary tests should be easy to read.

Occasionally someone asks me the question whether it’s necessary to test the code of solitary tests?

So I noticed that you completed that feature that we’ve been pair programming yesterday?

Solitary tests never cross the process boundary in which they are executed.

I’m very happy to announce that the first draft of my book Writing Maintainable Unit Tests has been published on LeanPub.

One of the most commonly asked questions in developer communities regarding Test-Driven Development and unit testing is whether one should write unit tests for private methods, and if so, how to accomplish this.

Test-Driven Development is a discipline that exists for about two decades now.

In the previous blog post, we’ve talked about avoiding excessive specification of test doubles.

Previously we’ve discussed the different kinds of test doubles.

When stating the definition of a solitary test, we mentioned that they have two constraints: The code being exercised by these tests never cross the process boundary in which they are executed.

In the previous blog post, we’ve talked about indirect inputs and outputs when a unit test exercises a Subject Under Test.

Previously we discussed what state and behaviour verification is about.

When reasoning about types of automated tests, I find it quite useful to reason about two different categories, namely solitary and sociable tests.

In a previous blog post, we discussed the test pyramid and why it is a useful model to reason about a healthy mix of solitary and sociable tests.

Previously, we touched on two different categories of automated tests, namely solitary and sociable tests.

Last week I published my very first video course titled Writing Maintainable Unit Tests.

I’m very proud to announce that my first video course has been published on Udemy.

In the previous blog post, we touched on two different categories of automated tests, namely solitary and sociable tests.

It’s more than fair to say that the terminology used in the world of automated tests can be a bit overwhelming.

Test-Driven Development is a discipline that exists for almost two decades now.

Developers are lazy.

A while back I stumbled upon this talk titled Built-in Fake Objects.

People who know me personally know that I like to go for a long run on a regular basis.

A while back, I was doing a code review.

One of the most fascinating documents I’ve read to date is the memo from Roger Boisjoly on O-Ring Erosion.

Back in 2008, Jeremy Miller introduced the Thunderdome Principle, a technique he used for building maintainable ASP.NET MVC applications which later led to the FubuMVC open-source project.

One of the first issues I faced when learning F# was finding out how to specify multiple parameters to a function.

I’ve been removing a couple of dead features this week.

A software development team in an organization should be able to focus on the core domain that reflects the business it’s serving.

The first time I read the GoF book, I didn’t understand it.

When I started blogging back in 2005 I created my personal blog on Blogger.

I’ve been learning about functional programming for quite some time now, trying to wrap my head around the various concepts that this paradigm has to offer.