@ffbit Before JUnit 4, JUnit relied on naming conventions to identify test methods (methods whose names are prefixed with ```test```), setup methods executed before each test method (methods named ```setUp()```) etc. In Junit 4 annotations are instead used for identification ```@Test``` -> test method, ```@Before``` -> setup method executed before each test method. The Wikipedia example still used the old naming convention even though it is not necessary (test method prefixed ```test``` for instance).

Now it is unusual to see test methods starting with ```test```, in this test class ```should``` is used as prefix for test methods (Dan North was advocating [```should```](http://dannorth.net/introducing-bdd/) early). I personally like ```should``` and in the test method names focusing on what the object under test should do, rather than what the test does.

When using JUnit 4 and ```@Before```, I personally view the name ```setUp()``` as a lost opportunity to document and communicate what set up is performed before each test method (which is something you must know when interpretation the implementation in the test method):
```
@Before // is performed before each test method
public void setUp() { // is performed before each test method (Yeah, I got that from the @Before annotation)
```
```
@Before // is performed before each test method
public void fetchUsEnglishXStreamConverterLookup() { // what is performed before each test method
```
Best regards.