Blog

Is there a role where quality is not essential? Whether for personal satisfaction, or as a requirement of your job description, we should strive to deliver quality in our work. In my first role as a graphic designer, I needed to send some business card designs to the printer, and

I’ve said it. You may have heard me say it, or at least seen me write it. Automation development is software development, and we need to treat it as such. I’ve also said the use of record-and-playback, drag-and-drop, or low-/no-code tools is generally not a good way to create an “enterprise-class”

DevOps started with a few revolutionary observations in their day yet seem obvious today. For example, before DevOps, you had the programmers, whose job was to create change, and operations, whose job was to ensure reliability or uptime. The easiest way to ensure uptime was to prevent change. Framed that

A few years ago, a friend emailed me a survey about software testing. The survey asked us to specify our roles, along with which kind of testing we thought was most important. As I recall, the question was, “If you could only do one type of testing, which would you

Behavior Driven Development was a mind hack. Dan North, the creator, was teaching unit testing to programmers and noticed that programmers found testing … well … boring – which made the idea of driving development with tests even less interesting.  Yet what those tests were doing was really defining behavior,

During our recent webinar on revisiting the test automation pyramid, an attendee named Stephen asked for some guidance on when mocking was good or bad. The good folks at Subject7 asked me to take a look at the question and offer my perspective. Mocking Defined A strict definition of a mock is