A small copy change and a database migration probably shouldn't go through exactly the same release process. Yet in many teams, they do. Both need the same approvals. Both follow the same checklist. Both wait for the same people, regardless of what...

I've been quieter on CoderLegion for a little while. Not because I ran out of things to write about. Quite the opposite. I've been spending a lot of time building Dulvarn, and one thing I've been learning as a solo founder is that a surprising amou...

An end-to-end test fails. The report is red. Someone asks, “Is it a bug?” Maybe. But at that moment, all we really know is that the test didn't observe the expected behavior. That distinction sounds small, but it changed the way I investigate fa...

When I started my first QA job, I had already spent around twenty years working in mechanical engineering and manufacturing. I had technical experience. I had programmed CNC machines. I had used Linux for years. I had even studied programming as a k...

I didn’t start building Dulvarn because I wanted to become a SaaS founder. At least, not at first. I started with a problem I kept seeing again and again in software delivery. A team could have: green CI passing tests successful builds approve...

What Happens After QA Says “Passed”? For a long time, my view of software quality ended at a fairly clear point. You test the feature. You verify the requirements. You report the bugs. The bugs get fixed. You retest. And eventually, you say: ...

My journey into QA didn't start with a testing course. It didn't even start with software testing. It probably started when I was around four years old. Every summer, I used to spend two or three months at my great-grandmother's house in the Czech...

The pipeline is green. QA signed off. The deployment window is open. Someone asks: “Are we good to release?” And then something interesting happens. Everyone looks at someone else. The developer knows the code. QA knows what was tested. DevO...

Your Tests Passed. That Still Doesn’t Mean You Should Release. A green test suite feels reassuring. Unit tests pass. Integration tests pass. End-to-end tests pass. CI is green. At that point, releasing can feel like the obvious next step. But the...

!Image descriptionhttps://dev-to-uploads.s3.us-east-2.amazonaws.com/uploads/articles/jkbnem9ae2wkqfe61is8.png A green CI pipeline is a nice feeling. The build passed. Tests are green. Linting is clean. Nothing obvious is on fire. For a few seconds,...

Every team has a moment like this: CI passes, the PR gets merged, the deploy goes out — and two hours later someone's asking why checkout is throwing 500s in production. Nobody skipped a step. The pipeline was green the whole time. The false comfor...