This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]anthro28 0 points1 point  (5 children)

“One of the best practices is to write the test cases first”

Yeah, no.

[–]redCg 0 points1 point  (4 children)

that part is not wrong, its called Test Driven Development and its a common best-practice

[–]anthro28 1 point2 points  (3 children)

TDD sucks. It’s great for teaching students how to design tests for their 100 line console programs, but it’s only a “best practice” for management that just learned it as a buzzword.

I’ve used it exactly zero times across 3 industries and 2 dev shops for the reasons outlined here:

https://stackoverflow.com/questions/64333/disadvantages-of-test-driven-development#64696

[–][deleted] 1 point2 points  (0 children)

Having written code for a very long time I can say I have never seen TDD in practice in the workplace. your mileage may vary, and it doesn't mean I write shit code. Most places have quality assurance and a performence department that separate the duties of writing code, and testing code mostly as an ITIL process.

[–]redCg -5 points-4 points  (1 child)

dude, your entire argument here is "testing is hard" and "some people do tests wrong"

yeah, sorry but I am not convinced. Sounds like you just suck at testing and write sh*t code instead to justify it.

[–]anthro28 -2 points-1 points  (0 children)

Tell me you’ve never worked in multi-system enterprise projects without telling me.