Comments by "" (@retagainez) on "Total TDD | VOL. 1: What Is It, What To Do When It Goes Wrong u0026 Why Hasn't It Taken Over The World?" video.

Isnt it a necessary step for when theres things like compliance, if you want to be a successful tech org?
1
I think a lot of people have the same exact comment. To stand out, would you help out by describing why that seems to be the case? Especially if you consider that a common way to do BDD is to do TDD.
1
@DirkBotha Colorful language is probably the reason if I had to guess. Either way, its not my responsibility. I'm mostly confused on how you've managed to get BDD without following the more common TDD steps to reach it.
1
@Trythrow If you host infrastructure for tons of tech companies, you simply can't not test. Your contracts can force you to pay out so much money if your software fails the customer.
1
@SirBenJamin_ If you're having to pass in parameters for testing so early in development, whos to say you wont need to do it for a production use case? If it already "broke" once as soon as you changed something as part of your development, it surely suggests and could correlate to an error of that same kind occurring in production in the near future. An added point to adding in a test double or mock thru DI is to avoid all the overhead of bringing in a real engine.
1
@SirBenJamin_ The users dont need to know about engines, they can, its optional in a car to know this. Most people just drive them and want them to be reliable. Same thing with the test example.
1
@ibolcina If you regularly talk to customer, you don't have to throw everything away. You do a small amount of work, check with them, and then in a roman gladiator style they give you a "thumbs up" or a "closed fist". If they don't like it, then figure out why how to talk to them better, that's it. Worst case scenario is you throw out a week or two of work. The more you work with them, the more you'll understand ALL requirements and that is what decreases the problems you encounter. There's no reason for these cop out explanations like "humans are unreliable and give me a poorly written contract"
1
@ibolcina You might test that your data is persistent and accessible to a customer, not that a table is defined in a database. That is already tested by the database developers... I would advise you to listen to what other people are telling you. Using small notes to describe high level is probably the most ideal amount of "proof of concept" work you should do for anything.
1