Erkan Yilmaz tagged me with a few questions regarding testing. However, I’m not a tester, I just happen to be interested in some areas of testing, e.g. unit testing & test-first-coding.
Could you tell something about your first tests?
I started getting interested in unit testing in the late 90s when XP came up. Still not 100% sure about where unit testing ends and acceptance testing begins.
What would you like to highlight as an important thing of testing – from your personal experiences?
As far as unit testing & test-first-coding is concerned, the most important aspect is “Just doin’ it even if you think you can’t do it”.
Why is testing not trivial?
Testing is always hard for a software developer because his/her brain knows about the inner workings of the code and therefore it requires an enormous amount of discipline to thoroughly test the code.
Test-first-coding is hard because it requires to change your mind set from testing as an afterthought to testing before you start coding.
What do you do after testing at work?
Coding 🙂
How do you think testing will evolve in the next 13 years?
Most of the kind of testing I’m interested in very much depends on the way the code is structured. So I would guess that the most interesting things will happen round tools & patterns which enable testable code.
Hello HMK,
thank you very much for your reply.
>“However, I’m not a tester”:
I did not mean to tell that you are a tester or not (for this I yet do not know you that well 🙂 )
and you will know the best what you are or what you are not. Sorry if there was miscommunication.
I think I need to quote something here about developers and testers.
As you will agree we should see not the roles primarily, because this makes us blind.
We should see ourselves as explorers (who at work try to make the product succeed and do their best also after work).
As you can see, my image of a tester differs from other peoples image.
And we can only get to know this by talking about it.
Erkan YILMAZ