Late September 2019, I've decided that it's time for a career change, so I've started searching through the job market and talking to various companies in need of a Senior Engineering Leader. It's not that I enjoy the process of looking for...
> This blog post covers: why boundaries constitute the structure, why E2E/Integration tests are not enough, what does it even mean "Boundary/Contract tests", who should create such tests & why and how to match expectations of more than one consumer. P.S. All the contracts covered...
I've encountered a very similar situation in so many companies: their IT landscape grew all the time (while nothing was decommissioned), layers they've initially got became more complicated or even split into sub-layers: sometimes parallel, sometimes stacked. Obviously, different components frequently utilize different technologies, so the...
Just some random thoughts / stuff I've bumped into recently. Enjoy. Interweave tests in support I love this legacy code rule (it's supposed to help fighting the technical debt): > When you touch any existing piece of code, always leave it in at least slightly better shape...
The prose of life Test automation ain't trivial & there are several reasons for that, including: * need for scalable structure (hierarchy, naming, etc.) * dealing with dependencies (coupling) * insufficient speed of execution affecting dev agility * shared resources impairing isolation * inertia of data (incl. configuration, parameterization, etc.) But there are...
