updated

Author: DavertMik

_layouts/post.html

@@ -19,6 +19,9 @@ <h1>{{ page.title }}</h1>
 
 <p class="lead">
   Published on {{ page.date | date: "%B %d, %Y" }}
+  {% if page.author %}
+  <br>by <strong>{{ page.author }}</strong>
+  {% endif %}
 </p>
 <div class="post">
   {{ content }}

_posts/2016-12-21-writing-better-tests--expectation-vs-implementation.markdown

@@ -2,6 +2,7 @@
 layout: post
 title: "Writing Better Tests: Expectation vs Implementation"
 date: 2016-12-21 01:03:50
+author: Michael Bodnarchuk @davert
 ---
 
 

_posts/2017-04-21-writing-better-tests--obtaining-specification.markdown

@@ -2,6 +2,7 @@
 layout: post
 title: "Writing Better Tests: Obtaining Specification"
 date: 2017-04-21 01:03:50
+author: Michael Bodnarchuk @davert
 ---
 
 When you start implement testing in your development process you should always ask: which tests are important for this project. And there is no general answer to this question. "Test everything, everywhere" is not a good solution as well, by writing more and more lines of code you won't stable software. Tests should be driven by specification, and specification comes from your business. Depending on that you should choose which areas are more important to cover with tests and which are less.