3 ms·
Article is about testing in the TDD sense, not the QA team sense.
by hashkb 10y ago
Article is about testing in the TDD sense, not the QA team sense.
- masklinn 10y agoThat's a distinction without a difference, good software testing is still an ethos of imagining boundary conditions and corner cases to "break" the code. A bad tester will create a test with a few basic inputs, see that it looks fine and be content with that.
- GrumpyYoungMan 10y agoHaving been both QA and dev in my career (and vastly preferring the former), I beg to differ. - TDD / unit testing: "Does it do the thing right?" i.e. does the code behave as the developer intended? This type of testing tends to be more internal than external. - QA testing: "Does it do the right thing?" i.e. does the code fully satisfy customer requirements (including integration testing) and other functional and parafunctional requirements? Certainly there is overlap between the two, e.g. the developers are working from their own understanding of the customers requirements, but they are not IMO the same thing.
- BurningFrog 10y agoTDD is a way to design software and make it easy to refactor. It is mostly "white box". That it leaves behind a solid test suite may not even be the most important thing about it.