3 ms·
I disagree. With good testing discipline, you can bring in freelance developers. Developers have the luck of not needing 100% understanding, as this is grown th
by scott_w 14y ago
I disagree. With good testing discipline, you can bring in freelance developers. Developers have the luck of not needing 100% understanding, as this is grown through the writing of code.
Testing, on the other hand, is a simulation of how your system responds to user input, and how your users respond to the system's outputs.
If your tester can't simulate a user, then you can make your services as micro as you like - it'll make no difference when you get the phone call saying the system doesn't work as expected.
- eru 14y agoIf new people picking up the app have a problem simulating users, then how do you assume your users will go about picking up the up to actually use it?
- scott_w 14y agoRead my comment below. It's not about users understanding the program per se, it's about testers having the domain knowledge to perform meaningful tests. Without that domain knowledge, the testers may find implementation bugs, but they won't expose the issues caused by the developer's lack of understanding. The latter is almost always more valuable to find and more difficult to fix.
- eru 14y agoOh, ok. I guess writing automatic tests is one way to nudge developers into understanding the domain better. And getting a person on the team, even freelance, whose job it is to push for tests, might help. Going off another tangent, getting not a generic tester, but a domain expert who's also a tester, might help.