Securing the Future: Testing Like a Developer with Filip Hric

Um, and so like one of the things that, uh, I've always found quite interesting in the work that you've done is that you've, you've pushed quite heavily, um, and I've, I've always tried to push the same thing, is that, uh, if you're doing test automation, you're some form of developer, right?

Yeah.

And that goes without saying, despite a lot of people going, "No, I'm a tester." It's like, no, if you're writing code, any form of code, you're a coder.

Uh-

Yeah

... how deep that goes, that's a different type of question.

Um, but, uh, one of the things that you've always argued, no matter what, who you are, is that you need to understand what the building blocks of any application is, right?

Yeah.

Um, why is that, um, why is that distinction and being able to understand that so important for modern quality engineering?

I, I have a theory on this, and I'm sure-- So I have already had ar- arguments with people about this.

Uh, so- some people even might feel that if you step way too much into the developer space, you might lose something from your tester's perspective, which I don't think is the case.

I, I, I would say it's, it's quite the opposite.

I would say that stepping into developer space, like e- makes you even better, uh, in your testing field.

That's what I always felt.

And the reason why, I give like countless of arguments and examples on that in my, uh, in my past talks.

Uh, the, the very simple argument is that, all right, imagine you're, you're testing a login screen, right? Your developers have done some work on it, and you're, uh, you're trying to, uh, test that.

And it's, and it's a robust thing.

Like even those two fields, name and password, are like pretty robust 'cause you have to look for, uh, happy paths, the edge cases, the, the-

Yeah

...

the typos and all kinds of different cases, logging with Google, et cetera.

And imagine jumping into that with like no knowledge of how that system works, and you find a bug, you cannot log in.

So you go ahead to your developer and say like, "Hey, it's, it's, it's broken.

You need to fix it." And they go ahead and fix it, not providing you with the information of what was wrong.

Yeah.