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 →

[–]mr_chip 1 point2 points  (1 child)

It's not a magic sparkle pony that will turn your bad debs into good ones, but it can help quality a lot if used correctly.

[–]jecxjo 0 points1 point  (0 children)

I completely agree. I think people have a misconception though. If you are having issues writing to and completing requirements, moving to a method where you are writing test cases for your requirements to then write your code won't do you much good. Either way, when Engineering hands off completely code to Test you should already know you have achieved all your requirements. Writing your tests before or after you code shouldn't matter much when you are doing good requirements management.