bashunit
bashunit: a testing framework for Bash with parallel and snapshot testing, test doubles and data providers. From dev frustration to open source.
Software testing strategies, frameworks, and testing culture.
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.

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.

If you see something, in the scope of your current task, that can be easily improved, improve it. And if you have any questions about it, ask.

Clear contracts, isolated side effects, testability, low complexity and cognitive load, code fluidity, and confidence in yourself.

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