Taghamcrest

Create your own hamcrest matcher

In Agile, Java, Test Driven Development, Testing

March 7, 2012

9 Min read

If you are familiar with hamcrest and JUnit the time will come when you have the need to create your own matchers. Creating your own matcher can be as simple as useful. One reason for creating your own matcher could be that your object is not a default object like a String or a Collection. And if you would like to get a more readable version of the assert for the next developer who has to read your test. Let’s make an example. If you have an object with two methods; “getName”...

Read on

Easier JUnit testing with hamcrest

By Adrian Elsener

In Java, Testing

February 7, 2012

3 Min read

Have you ever thought that JUnit assertions are not really readable and do not correspond to natural language? It is a mess that the expected value is the first argument on an assert? This would not be like the spoken language where you would say “assert that this value is equal to this expected one” ? Or have you had tests where the expected value and the value to test were inverted? In this case you have not found an old friend of JUnit called hamcrest.

Read on

Taghamcrest

Create your own hamcrest matcher

Easier JUnit testing with hamcrest

Search

Recent Posts