You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/tdd-design-benefits.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ Most of us think of TDD as a tool for software testing and verification. But if
12
12
Since Test Drive Development (TDD) was introduced by Kent Beck it has always been a bit of a controversial topic. Today we are going to explore what TDD has to offer apart from being a way
13
13
to test and verify software. Before we dig deeper, let's take a look back at what is TDD, in the first place.
14
14
15
-
> ### TDD is a process used to build software in which unit tests are written even before writing any code.
15
+
> TDD is a process used to build software in which unit tests are written even before writing any code.
16
16
17
17
As defined above, we write unit tests even before we write the code. This might sound counterintuitive as to how can we test something before it even exists.
18
18
To make this easier to understand, try to think of it like this. It is not testing but stating what you expect the code to do. With this, you are trying to put your expectation before writing the code.
@@ -55,7 +55,7 @@ This helps us understand how complicated the code setup could be if it needs a l
55
55
This acts as an indicator and surfaces tight coupling if any early on in the development lifecycle.
56
56
We could consider this as a tool which would prevent the design of the system from having high coupling and reduce complexity.
57
57
58
-
> ### TDD is not just about having tests but a lot more than that. It not only helps us verify the correctness of the software but if practised well, helps us design the software well. This is why I sometimes think of TDD as **Test Driven Design**
58
+
> TDD is not just about having tests but a lot more than that. It not only helps us verify the correctness of the software but if practised well, helps us design the software well. This is why I sometimes think of TDD as **Test Driven Design**
59
59
60
60
All of this sounds too good, but it's easier said than done.
61
61
Here is one of the many reasons why people are not able to successfully adopt this practice into their development lifecycle.
@@ -68,4 +68,4 @@ We are going to be slow in anything we don't know, not just TDD.
68
68
Only spending enough time with any skill will make us move faster.
69
69
Be it learning a new programming language, playing a new musical instrument or learning to drive.
70
70
71
-
##To conclude, TDD could be used to improve the overall design of the system instead of just using it to increase code coverage.
71
+
>To conclude, TDD could be used to improve the overall design of the system instead of just using it to increase code coverage.
0 commit comments