net.sourceforge.groboutils.junit.v1.iftc

Home
Java Source Code / Java Documentation
1.6.0 JDK Core
2.6.0 JDK Modules
3.6.0 JDK Modules com.sun
4.6.0 JDK Modules com.sun.java
5.6.0 JDK Modules sun
6.6.0 JDK Platform
7.Ajax
8.Apache Harmony Java SE
9.Aspect oriented
10.Authentication Authorization
11.Blogger System
12.Build
13.Byte Code
14.Cache
15.Chart
16.Chat
17.Code Analyzer
18.Collaboration
19.Content Management System
20.Database Client
21.Database DBMS
22.Database JDBC Connection Pool
23.Database ORM
24.Development
25.EJB Server
26.ERP CRM Financial
27.ESB
28.Forum
29.Game
30.GIS
31.Graphic 3D
32.Graphic Library
33.Groupware
34.HTML Parser
35.IDE
36.IDE Eclipse
37.IDE Netbeans
38.Installer
39.Internationalization Localization
40.Inversion of Control
41.Issue Tracking
42.J2EE
43.J2ME
44.JBoss
45.JMS
46.JMX
47.Library
48.Mail Clients
49.Music
50.Natural Language Processing
51.Net
52.Parser
53.PDF
54.Portal
55.Profiler
56.Project Management
57.Report
58.RSS RDF
59.Rule Engine
60.Science
61.Scripting
62.Search Engine
63.Security
64.Sevlet Container
65.Source Control
66.Swing Library
67.Template Engine
68.Test Coverage
69.Testing
70.UML
71.Web Crawler
72.Web Framework
73.Web Mail
74.Web Server
75.Web Services
76.Web Services apache cxf 2.2.6
77.Web Services AXIS2
78.Wiki Engine
79.Workflow Engines
80.XML
81.XML UI
Java Source Code / Java Documentation  » Test Coverage » GroboUtils » net.sourceforge.groboutils.junit.v1.iftc 
net.sourceforge.groboutils.junit.v1.iftc
net.sourceforge.groboutils.testing.junit.v1 Classes to aid in testing interfaces, abstract classes, and base classes for "contract tests".

Interface Testing

The Sun Java Tutorial indicates that classes which implement an interface "[sign] a contract" [1]. In some cases the contract has meta-data beyond the API declared in the interface source-code, such as "must never return null", usually declared in the JavaDoc. Forcing each implemented class to test this on its own is both poor coding practice and unenforcable. Instead, what we need is a way to write test cases for the interface, and each implemented class can execute an instance of that class against the tests. This framework eases this practice by extending the JUnit framework.

The interface creator creates a TestCase which extends InterfaceTest, commonly through InterfaceTestCase. The class to test need not be only an interface: in can be any kind of class.

Implemented classes need to use something like the following to test through an interface test:

import net.sourceforge.groboutils.junit.v1.iftc.*;
import junit.framework.*;

public MyClassTest extends TestCase {
    public MyClassTest( String name ) {
        super( name );
    }

    public static Test suite() {
        TestSuite suite = new TestSuite( MyClassTest.class )
        InterfaceTestSuite its = MyInterfaceTest.suite();
        its.addFactory( new CxFactory( "A" ) {
            public Object createImplObject() {
                return new MyClass( "string" );
            }
        } );
        its.addFactory( new CxFactory( "B" ) {
            public Object createImplObject() {
                return new MyClass( null );
            }
        } );
        suite.addTest( its );
        
        return suite;
    }
    ...
}
The interface test would then look something like:
import net.sourceforge.groboutils.junit.v1.iftc.*;
import junit.framework.*;

public MyInterfaceTest extends InterfaceTestCase {
    public MyInterfaceTest( String name, ImplFactory f ) {
        super( name, MyInterface.class, f );
    }

    public static InterfaceTestSuite suite() {
        InterfaceTestSuite suite = new InterfaceTestSuite(
            MyInterfaceTest.class );
        
        return suite;
    }
    
    ...
}

References

  1. Various. The Java Tutorial. Online at http://java.sun.com/docs/books/tutorial/java/interpack/usinginterface.html .
Java Source File NameTypeComment
AntJUnitEUTest.javaClass Tests the functionality of the Ant JUnit optional tasks for what is expected in operation of the naming facilities.
CxFactory.javaClass Helper abstract class that aids in the setting of a unique and distinguishable name for a test case's factory.

As of 08-Dec-2002, the original constructor will NOT add the owning class's name to the factory toString() output.

CxFactorySample.javaClass Sample CxFactory used in CxFactoryUTest.
CxFactoryUTest.javaClass Tests the CxFactory class.
ICxFactory.javaInterface An ICxFactory is an extension of ImplFactory that has provisions for cleaning up generated objects on test tear down.
ICxFactoryUTestI.javaClass Tests the ICxFactory interface.
ImplFactory.javaInterface Allows for tests to be written on interfaces or abstract classes, by creating a specific instance of the interface or abstract class.
ImplFactoryUTestI.javaClass Tests the ImplFactory interface.
InnerClassNameEUTest.javaClass Tests the functionality of the JUnit TestSuite class for conformance to expected behaviors.
InterfaceTestCase.javaClass A subclass of TestCase to ease the requirements of creating an interface test.
InterfaceTestCaseUTest.javaClass Tests the InterfaceTestCase class.
InterfaceTestSuite.javaClass Allows for tests to be written on interfaces or abstract classes.
InterfaceTestSuiteUTest.javaClass Tests the InterfaceTestSuite class.
Sample1.javaInterface Sample interface.
Sample1IUTestI.javaClass Tests the Sample1 interface.
Sample2.javaInterface Sample interface.
Sample2IUTestI.javaClass Tests the Sample2 interface.
Sample3.javaClass Sample abstract class.
Sample3Impl.javaClass Sample implementation.
Sample3ImplIUTest.javaClass Tests the Sample3Impl class.
Sample3IUTestI.javaClass Tests the Sample3 abstract class.
Sample4.javaInterface Sample interface.
Sample4IUTestI.javaClass Tests the Sample4 interface.
w___ww__.___j__a__v_a_2___s.__c__o__m__ | Contact Us
Copyright 2009 - 12 Demo Source and Support. All rights reserved.
All other trademarks are property of their respective owners.