This post is available at http://www.thinkcode.se/blog/2016/10/03/creating-confidence-when-testing
October 3, 2016
September 4, 2016
This post is available at http://www.thinkcode.se/blog/2016/09/01/why-should-you-care-about-quality
August 6, 2016
This post is available at http://www.thinkcode.se/blog/2016/08/06/creating-technical-debt-is-like-gaining-weight
August 4, 2016
This post is available at http://www.thinkcode.se/blog/2016/08/04/gatling-a-tool-for-load-testing
July 25, 2016
This post is available at http://www.thinkcode.se/blog/2016/07/25/the-right-tool-for-the-job
June 22, 2016
This post is available at http://www.thinkcode.se/blog/2016/06/22/cucumber-antipatterns
April 18, 2016
Hamcrest, JUnit, Mockito, IntelliJ IDEA, Gradle, and java.lang.NoSuchMethodError: org.hamcrest.Matcher.describeMismatch
Ever included Mockito in your project and lost the nice feedback from Hamcrest? And only when running your unit tests from IntelliJ IDEA? Instead of a message describing what you should fix, you see
I have. More than once and been very frustrated. These are tools I like. Not getting good messages upsets me.
April 2, 2016
This post has been migrated to http://www.thinkcode.se/blog/2016/04/02/cucumber-regular-expression-cheat-sheet
If you are like me, then you will feel a lump in your stomach when you realize that you need a regular expression. I think that the saying “If you have a problem that requires a regular expression, then you have two problems” is very appropriate most of the time.
It turns out that you need a some regular expressions when you are working with Cucumber. In this case, they are usually not very complicated.
March 26, 2016
This post has been migrated to http://www.thinkcode.se/blog/2016/03/26/where-should-you-use-behaviour-driven-development-bdd
When I was at the European Testing Conference 2016 in Bucharest, a colleague asked me about my thoughts on they should use Behaviour Driven Development, BDD. I didn’t get a good chance to elaborate on my view so I decided that I should write this instead.
March 25, 2016
This post has been migrated to http://www.thinkcode.se/blog/2016/03/25/dependencies-between-tests
A test must be independent. That is, a test should never depend on the result of another test.
If you run two tests in a specific order, you should expect the same result as if you run them in the reverse order.