Who Needs Testers Anyway?

I think we just have to get this out of the way first.

I see almost two modes in every company I've ever interviewed or interacted with.

That's the no quality whatsoever because it's no one's responsibility or no quality whatsoever because there's a single person, team or organization with quality in their name, effectively isolating from the whole system, having quality built into it.

How does this even happen?

Oh, my God.

If I would know how that happens, oh, dear, I think I'd be a billionaire already.

Honestly, I feel...

There is so much history behind that.

Well, I used to work for quite a long time in so-called quality roles.

So I had the quality or the testing thing in my job title and only just recently got into a company.

But I can tell you a bit more on that later where there was like this,

OK, no

quality, we don't.

Not we don't need it, but there is no person or department responsible for that.

I feel like for me, it's a lot about how we used to work in a waterfall way.

So this one after the other, and it seemed to be clear that, okay, as a business analyst, for example, my responsibility is to write all the requirements, pixel perfect, 100%, and then I'll hand it over to developers, and then they take care of it, and they do the developing, writing, coding stuff.

And then when they are done, and that used to be defined by, okay, the code is there, but testing is not part of my job.

experienced that a lot.

Not so much anymore these days, that's good.

But then, you know, it got handed over to this, ah, there is the quality person, department, team, whoever, and they will magically build that quality in or test it in.

And I never understood how that should happen, how this should work.

It just seems stupid to me from the very

beginning.