3 ms·
Engineers SHOULD be responsible for testing code they write themselves. Which has absolutely nothing to do with the need for QAs to test as well. At the very
by addicted 6y ago
Engineers SHOULD be responsible for testing code they write themselves.
Which has absolutely nothing to do with the need for QAs to test as well.
At the very least there is a completely different psychology required in testing, where the goal is to break things, but when you are the person who has created that thing there is sub conscious resistance to breaking things too much.
- nicoburns 6y ago> when you are the person who has created that thing there is sub conscious resistance to breaking things too much. Definitely this. I'm primarily a developer, but while I can do a good job of QA on someone else's code, I find it almost impossible to do a thorough job on my own.
- dragonsngoblins 6y agoFor me I think the reason I can't do a thorough job on my own code is down to a combination of two reasons: 1) Testing my own code is boring. I keep thinking about what it should do and then taking shortcuts where I don't test every possible circumstance because I believe I can infer what will happen in one case from another. 2) Testing my own code is time I'm not spending working on the next bit of code in my queue. At a certain point I start feeling like I should just be working on the next thing
- nicoburns 6y agoFor me, I think it's partially that I have too many preconceptions about how the code will be used. I still have the implementation in mind when I'm testing. Whereas good QA will be naive and test things that the dev might not have thought of.