Check out the latest posts
Sebastian Gebski

Boundary/Contract Testing 101

> 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 here are supposed to...

Sebastian Gebski

Distributed responsibility for Architecture - is it even possible?

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 skill-set required to develop...

Sebastian Gebski

Few test-related tricks for (even) the old dogs

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 than it was before. It...

Sebastian Gebski

What if I told you ... that automating tests may change nothing?

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 two even bigger...

You’ve successfully subscribed to No Kill Switch
Welcome back! You’ve successfully signed in.
Great! You’ve successfully signed up.
Success! Your email is updated.
Your link has expired
Success! Check your email for magic link to sign-in.