Java201.com

• An early look at JUnit 4 by Elliotte Harold   - [Clicks: 88]
  JUnit is the de facto standard unit testing library for the Java language. JUnit 4 is the first significant release of this library in almost three years. It promises to simplify testing by exploiting Java 5's annotation feature to identify tests rather than relying on subclassing, reflection, and naming conventions. In this article, obsessive code tester Elliotte Harold takes JUnit 4 out for a spin and details how to use the new framework in your own work. Note that this article assumes prior experience with JUnit.
  http://www-128.ibm.com/developerworks/java/library/j-junit4.html - Sep, 2005
• JUnit antipatterns by Alex Garrett   - [Clicks: 97]
  The advent of JUnit has been a boon to developers. Unfortunately, many think it's enough to learn the JUnit API and write a few tests in order to have a well-tested application. This idea is worse than not testing at all because it leads to a false sense of code health. Learning JUnit is the easiest part of testing. Writing good tests is the hard part. This article presents some common JUnit antipatterns and shows how to resolve them.
  http://www-128.ibm.com/developerworks/opensource/library/os-junit/ - Jul, 2005
• Test Framework Comparison by Justin Lee   - [Clicks: 116]
  Justin Lee has written up a comparison between JUnit, JTiger, and TestNG, focusing on the differences between them to illustrate how each might be used.
  http://www.theserverside.com/articles/article.tss?l=TestFrameworkComparison - Jul, 2005
• Taking JUnit Out of the Box by Amir Shevat   - [Clicks: 69]
  This article will describe how JUnit can perform complex test scenarios by introducing Pisces, an open source JUnit extension that lets you write test suites composed of several JUnit tests, each running on a remote machine serially or in parallel. The Pisces extension will allow you to compose and run complex scenarios while coordinating all of them in a single location.
  http://www.onjava.com/pub/a/onjava/2005/07/13/pisces.html - Jul, 2005
• AOP@Work: Use AOP pointcuts to skip patterns in the JUnit Cook's Tour by Wes Isberg   - [Clicks: 38]
  In "JUnit: A Cook's Tour," authors Erich Gamma and Kent Beck discuss the design of JUnit. They point out that TestCase, like key abstractions in many mature frameworks, has a high pattern density, making it easy to use but hard to change. In this installment of the AOP@Work series, Wes Isberg revisits the Cook's Tour and shows you how using AOP pointcuts rather than object-oriented designs can help you avoid some of the pattern density that makes mature designs hard to change.
  [Includes source code]
  http://www-128.ibm.com/developerworks/java/library/j-aopwork7/index.html - Jun, 2005
• Build, deploy, and test EJB components in just a few seconds by Nader Aeinehchi   - [Clicks: 91]
  Wouldn't life be easier if you could build, deploy, and test Enterprise JavaBeans (EJB) components in just a few seconds? This article shows you how to simplify the EJB development cycle. Author Nader Aeinechi shows how to easily create input data for your JUnit tests with XStream. He explains the benefits of running your tests with an embedded EJB container called OpenEJB and how those same tests can be run unmodified on your full-featured production EJB container.
  http://www.javaworld.com/javaworld/jw-06-2005/jw-0613-ejb.html - Jun, 2005
• Execute EJB JUnit Tests in Your Deployed Apps by Lara D'Abreo   - [Clicks: 47]
  Extend the life of your JUnit tests by enabling them to be executed inside a real deployed J2EE app, not just on developer PCs.
  http://www.devx.com/Java/Article/28119 - May, 2005
• Assertion Extensions for JUnit by Tony Morris   - [Clicks: 32]
  JUnit lets you test software code units by making assertions that the intended requirements are met, but these assertions are limited to primitive operations. IBM Software Engineer Tony Morris fills the gap by introducing Assertion Extensions for JUnit, which provides a set of complex assertions that execute within the JUnit framework. Follow along as the author shows you how using this new package from alphaWorks can increase the reliability and robustness of your Java software.
  http://www-128.ibm.com/developerworks/java/library/j-unitx/ - Mar, 2005
• Test your tests with Jester by Elliotte Rusty Harold   - [Clicks: 44]
  A comprehensive unit-test suite is a necessity for a robust program. But how can you be sure that your test suite is testing everything it should? Jester, Ivan Moore's JUnit test tester, excels at finding test-suite problems and provides unique insights into the structure of a code base. Elliotte Rusty Harold introduces Jester and shows how to use it for best results.
  http://www-128.ibm.com/developerworks/java/library/j-jester/ - Mar, 2005

[Top]

• JUnit: The Definitive Guide  by Derek Lane   - [Clicks: 151]
  This thorough and practical guide to the JUnit testing framework shows IT managers what to expect if they implement unit testing in their projects. It also arms developers with everything they need to know for installing and using JUnit. Through targeted reference information and examples, it effectively breaks down complex concepts for easy comprehension.
  ,  - Jul, 2005

[Top]

• Test Driven Development : Why using Jython and Python to write Junit tests by Laurent Ploix   - [Clicks: 21]
  ... The best technic I found consists in writing my unit tests in a scripting language. I use Jython for that when it comes to Java, and C-python otherwise. I wrote an article about Jython on DevX, here, but it needs to be completed. So now let's focus on some points : * Point 1 : Unit Tests should be written in a scripting language (I chose the python family) ; * Point 2 : Unit Tests results should be displayed in your IDE; * Point 3 : Unit Tests should be "played" as often as possible ...
  [Includes source code]
  http://lauploix.blogspot.com/2005/03/test-driven-development-why-using.html - Mar, 2005

[Top]