So I have implemented all the features required for the current release. Carefully reviewed my code several times, but no testing.

Tester: everything passed green. Not sure whether you're a good dev or I'm a bad tester.

Me: let's call it a draw.

I always hated testers.

@DarkVoyager I've been in testing for several years, and it changed the way I code.

Nice work 👍🏼

I wish I knew how to write tests better. Always envious of the people who can implement TDD. Especially when working on a group project with people with varying levels of experience and varying levels of friendliness with git.

I like TDD also.

But most testers especially non technical ones are there to get developers. It’s like a Cobra vs Mongoose.

So sometimes I deliberately leave a bug or two in the code to see how thorough the testers are. I do this in early stages of development. I have found the testers that use automated tools can usually catch those bugs. I do respect them.

@AmyShackles look into https://qualitycoding.org

I met this guy Jon Reid many years ago and he got me into TDD.

TDD is actually easier than you make it out to be.

Some of it you probably do it anyway. Like you probably write pieces of code little by little and put print statements to check if that little bit is working. Only thing is your checks are thrown away. TDD makes it more formal but really same dev steps.

@DarkVoyager Hey, thanks, man!

@orseji Simple answer... write tests :P

@orseji I take my time for writing code, imagine how the whole thing will run, think of edge cases and possible failure conditions to make it robust.

Plus that I don't use debuggers and instead prefer to read the code. That may take a bit longer sometimes, but works also for bugs from the field that we can't reproduce in the lab, and also when when I review code.

@rutee07 Yeah, such lazy programming is expensive because it burns through a lot of working hours for the testers. They have to check their test setup, test scripts and make a useful report. Besides, it's a whack-a-mole game that will never lead to robust software.