updated

DavertMik · DavertMik · commit a834d8411215 · 2016-12-22T01:36:43.000+02:00
diff --git a/_posts/2016-12-21-writing-better-tests--expectation-vs-implementation.markdown b/_posts/2016-12-21-writing-better-tests--expectation-vs-implementation.markdown
@@ -4,10 +4,6 @@ title: "Writing Better Tests: Expectation vs Implementation"
 date: 2016-12-21 01:03:50
 ---
 
-*Written by Michael Bodnarchuk @davert.
-
-Thanks to Nick Palamarchuk for the review and ideas.*
-
 
 ![](/images/car_test.jpg)
 
@@ -78,3 +74,7 @@ Overusing mocks also makes tests longer. Lines of test code you write doesn't al
 
 So the actionable advice here is to think **what is important to you: a behavior or a result** (no matter how it is achieved). Try to **discover what is stable and what is not, rely on stable parts, and use public interfaces**. Thanks for reading. 
 
+
+*Written by Michael Bodnarchuk @davert.*
+
+*Thanks to Nick Palamarchuk for the review and ideas.*
