Test Driven Development is alive and well
| Despite what you might have heard around the industry and on the Internet, Test Driven Development (TDD) is not dead. The practice is still alive and well, especially in this new modern agile world. |
http://sdtimes.com/test-driven-development-alive-well/
It might not be dead but it lives its shadow existence. The simple reason is time. This kind development takes more than double of the time. It is not guaranteed that you have less bugs.
The point of a bug is that there is an unexpected condition. It is unlikely that you think of that praticular condition in your test code. Plus there might be bugs in the test code as well.
I would think that the most common testing approch is black box.
The point of a bug is that there is an unexpected condition. It is unlikely that you think of that praticular condition in your test code. Plus there might be bugs in the test code as well.
I would think that the most common testing approch is black box.
In my experience, writing the tests just helps me think about the test cases so I don't have to go back and rewrite code when I think of something while writing it. In that way, it saves be a bunch of time and I've already got a test to make sure I caught that case.
closed account (1vRz3TCk)
Modern Dev Practices Unit Testing high
Published on Jul 3, 2017
In this episode, Robert is joined by Phil Japikse, who explores how in modern development practices, unit testing is part of the development process, not a chore to be tackled after you write your code.
Phil spends most of the time on Test Driven Development (aka Test Driven Design), where you write a test first and then write just enough code to pass the test and then refine the code as you add more tests. In TDD, the tests embody the requirements the code must satisfy.
He also briefly covers Behavior Driven Development [50:20] and Mocks [53:45].
https://www.youtube.com/watch?v=4averylLdjQ
In this episode, Robert is joined by Phil Japikse, who explores how in modern development practices, unit testing is part of the development process, not a chore to be tackled after you write your code.
Phil spends most of the time on Test Driven Development (aka Test Driven Design), where you write a test first and then write just enough code to pass the test and then refine the code as you add more tests. In TDD, the tests embody the requirements the code must satisfy.
He also briefly covers Behavior Driven Development [50:20] and Mocks [53:45].
https://www.youtube.com/watch?v=4averylLdjQ
Last edited on
Topic archived. No new replies allowed.