Software engineers tend to be enamored with complexity. Yes, systems and programs are complex by nature. But the truth is a little more … sinister. Who does complexity benefit ? Complexity actually is quite advantageous — for the individual developer. With a complicated codebase, the architect can impress people with their personal raw intelligence. New…

Unlike app development, QA automation always deals with two codebases, always in parallel: the automation code, and the actual application under test. Let’s take a look at the relationship between these two — specifically, stable and unstable branches, and how “cross-targeting” these branches can improve your automation efficiency big time. A Tale of Two Repositories

QA is boring. Let’s write our tests with bullets! Cucumber is great but … I’ve used Cucumber for test automation for a lot of my career, and honestly I’ve been pretty happy. It’s a great way to pull one’s thinking out of the granular code level, and starting thinking about domain or enterprise level problems…

Wherein all will be explained, answered, fixed, thoroughly tested and approved. Ship it! Test Driven Development aka TDD, and Behavior or Business Driven Development aka BDD, are both approaches to automated testing, originally stemming from Agile and Extreme Programming in the 2000s. It’s taken a while, but today these approaches…

Espresso tests are pretty unwieldy out of the box. Here’s a take on better architecture through layers. Lessons from the Browser Age Web test automation has a best practice called “Page Object Models”, which separates test code into two parts: An abstraction layer which models the application under test Business…