Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "User:Michael.norman.oracle.com/Info on JUnit4"
(→Information on JUnit4) |
(→Information on JUnit4) |
||
Line 34: | Line 34: | ||
@Before | @Before | ||
− | public void prepareTestData() { ... } | + | '''<font color="#7f0055">public void'''</font> prepareTestData() { ... } |
@Before | @Before | ||
− | public void setupMocks() { ... } | + | '''<font color="#7f0055">public void'''</font> setupMocks() { ... } |
@After | @After | ||
− | public void cleanupTestData() { ... } | + | '''<font color="#7f0055">public void'''</font> cleanupTestData() { ... } |
} | } |
Revision as of 15:12, 4 December 2007
Information on JUnit4
- successor to most widely used unit-testing framework for Java, JUnit3
- under active development (last JUnit3 release 3.8.2 2006-03-03)
- JUnit 4 released 2006-02-16
- 4.1 2006-04-27
- 4.2 2006-11-16
- 4.3 2006-11-16
- 4.3.1 2007-03-28
- 4.4 (current as of 071204) 2007-07-18
- JUnit 4 released 2006-02-16
- based on Java 5 features:
- no longer need to extend class TestCase
- test-method names do not have to start with the prefix test
- mark your test method with a @Test annotation
- use static import's to get assert methods (instead of via inheritance)
importjunit.framework.TestCase; import org.junit.Test; import static org.junit.Assert.*;; public class CalculatorTestextendsTestCase { @Test public voidtestadd() { .... assertEquals(4, calculator.add( 1, 3 )); } }
- improved test lifecycle management:
- setUp() and tearDown() replaced with @Before and @After annotations (allows for multiple @Before/@After methods)
public class CalculatorTest { @Before public void prepareTestData() { ... } @Before public void setupMocks() { ... } @After public void cleanupTestData() { ... } }