4 ms·
Wait, what?! Writing tests before you code was supposed to require less testing than writing the tests after you code? Also a large red flag: are testers supp
by marcosdumay 6y ago
Wait, what?!
Writing tests before you code was supposed to require less testing than writing the tests after you code?
Also a large red flag: are testers supposed to make your program secure? How would that even work?
I ought to give up on clicking on TDD articles at some point. People pushing it seem to come from some parallel universe completely different from here.
- necovek 6y agoUhm, this article is doing anything but pushing TDD, so while you may have not given up on clicking them, you have at least given up on reading them ;-) This article instead argues how TDD is insufficient and QA is still needed. I would argue that the article author does not even understand TDD himself, but I'll clarify that in another comment.
- muricula 6y agoSecurity analysis is uses framed as finding bugs. There's a few main ways of doing this when searching for bugs in C/C++ code: * Design consultations early in development to address insecure or risky designs. * Reading risky parts of the code line by line hunting for buffer overflows and many other things. If you don't have access to the source, you can read the disassembly too, and people find a lot of bugs doing that! * Fuzzing. Basically hooking up the program to a harness which throws random data at its attack surface until the program crashes, although it can get a lot more nuanced than that. * Running static analysis tools to search for problematic code patterns. The C/C++ code which powers all major operating systems and web browsers is rife with security issues. There are also whole other sub-disciplines auditing websites, corporate networks, and cryptography implementations, which generally use analogous techniques.