bashunit
bashunit: a testing framework for Bash with parallel and snapshot testing, test doubles and data providers. From dev frustration to open source.
Test-Driven Development: writing tests first to drive better design.

bashunit: a testing framework for Bash with parallel and snapshot testing, test doubles and data providers. From dev frustration to open source.

A practical guide to pair programming that works: roles, rotation, when to pair, common pitfalls, and how to make sessions productive.

From time to time I have had to face this question: how to test private methods? I have put together in an article the techniques that I usually use.

Let's talk about the QA position. The hidden truth behind poor software quality, and why it concerns you if you write code.

My interview with devm.io regarding Agile and Extreme Programming. Agile is more about HOW you do certain things, rather than WHAT things you do.

Uncle Bob on the three pillars of craftsmanship: TDD disciplines with examples, standards for teams, and a programmer's ethics.

Real seniority goes beyond job titles. It's about impact, mentoring others, owning outcomes, and raising the bar for your entire team.

Software demands non-stop learning. How to create the spaces your team needs to leave the comfort zone and embrace change.

There are two known schools in TDD: the mockist school (aka Outside-in) and the classicist school (aka Inside-out).

These are two different techniques. The key to each of them is about the mindset and context of what you want to achieve.

TDD is a design practice, not just a testing technique. Writing tests first changes how you think about code and shape its structure.

Mocking is useful, but 'what to mock' usually turns out to be a more complicated than expected if you don't treat this carefully.

How to write characterization tests for legacy code to safely refactor without breaking existing behavior.

Why you should consider testing as part of your daily development habit and how it's directly linked to the software quality.

Back to basics on Agile: what it was, what motivated it, and what has happened to it since. Uncle Bob's account.

Kent Beck on XP, the most specific agile framework about engineering practice, and how it raises software and team quality.

Michael Feathers on adding tests to untested code, breaking dependencies, and refactoring legacy systems safely.

Uncle Bob on professional behaviour in software: time management, handling pressure, TDD, and what a craftsman actually owes.

Bad code works, but it drags a whole organization down. Uncle Bob on what clean code is and how to keep it that way.
A live coding session on test-first development and refactoring, solving a code kata from scratch in pair and mob programming.