Validation Testing Framework Prerequisites

Running the Validation Testing Framework on a target runtime

As provided in the Device Kit, example launch configurations for running validation tests support Equinox or a standard JRE from the Eclipse SDK workbench. To run a validation test on a target runtime environment the following prerequisites must be met, besides the general Device Kit and Service Activator Toolkit minimum requirements, like a Java 1.4 JVM and an OSGi/Minimum-1.1 Java Runtime Environment.

JUnit 3.8.1 (Java 1.4 or later) or JUnit 4 (Java 5).

When running the test manager on the target runtime: a namespace-aware parser for the Simple API For XML Parsing (SAX) 2.0.

When accessing the target runtime from a test manager running on a remote system: support for the Java Remote Method Invocation (Java RMI).

When running inside the Eclipse SDK workbench using one of the example launch configurations, the prerequisites are fulfilled by default. Both a JUnit 3.8.1 and a JUnit 4 plug-in are part of the Eclipse base platform, and a SAX 2.0 or later parser is part of the J2SE core APIs.

When running on a target Java Runtime Environment, the following applies:

	Standard Java runtime	OSGi runtime
JUnit	Add junit.jar (Java 1.4 or later) or junit4.jar (Java 5) to the classpath.	Install Device Kit bundle org.eclipse.soda.dk.junit-osgi-min. This bundle provides an implementation of Junit 3 that is compatible with the OSGi/Minimum-1.1, Java Micro Edition and Standard Edition execution environments.
SAX	If not already part of the core APIs of the Java runtime, add a SAX parser implementation compatible with the JRE to the classpath.	If not already part of the core APIs of the Java runtime, add a SAX parser implementation compatible with the JRE to the classpath, or install a bundle exporting a SAXParserFactory as OSGi service. One way to do this is to add the Xerces implementation JAR files, which can be downloaded from http://xerces.apache.org/xerces2-j/ to the extensions directory of the JRE. Then, if using Equinox as the OSGI implementation, modify the org.osgi.framework.system.packages property in the config.ini file to specify the XML packages to be exported^[1]. Alternatively, since the test manager can be run remotely from the test controller, and only the test manager requires an XML parser, it is also possible to run just the test controller on the target machine, and to run the test manager on a separate machine that supports a full J2SE JRE. In this case, no modifications need to be made to support the XML requirement.
RMI	If not already part of the core APIs of the Java runtime, add an implementation of the JSR-66 RMI Optional Package Specification version 1.0 for the target JRE to the classpath.

Standard Java runtime

OSGi runtime

JUnit

Add junit.jar (Java 1.4 or later) or junit4.jar (Java 5) to the classpath.

Install Device Kit bundle org.eclipse.soda.dk.junit-osgi-min. This bundle provides an implementation of Junit 3 that is compatible with the OSGi/Minimum-1.1, Java Micro Edition and Standard Edition execution environments.

SAX

If not already part of the core APIs of the Java runtime, add a SAX parser implementation compatible with the JRE to the classpath.

If not already part of the core APIs of the Java runtime, add a SAX parser implementation compatible with the JRE to the classpath, or install a bundle exporting a SAXParserFactory as OSGi service. One way to do this is to add the Xerces implementation JAR files, which can be downloaded from http://xerces.apache.org/xerces2-j/ to the extensions directory of the JRE. Then, if using Equinox as the OSGI implementation, modify the org.osgi.framework.system.packages property in the config.ini file to specify the XML packages to be exported^[1]. Alternatively, since the test manager can be run remotely from the test controller, and only the test manager requires an XML parser, it is also possible to run just the test controller on the target machine, and to run the test manager on a separate machine that supports a full J2SE JRE. In this case, no modifications need to be made to support the XML requirement.

RMI

If not already part of the core APIs of the Java runtime, add an implementation of the JSR-66 RMI Optional Package Specification version 1.0 for the target JRE to the classpath.

^[1] To do this add the following line to the config.ini file: org.osgi.framework.system.packages=javax.xml,javax.xml.datatype,javax.xml.namespace,javax.xml.parsers,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.sax,javax.xml.transform.stream,javax.xml.validation,javax.xml.xpath,org.w3c.dom,org.w3c.dom.bootstrap,org.w3c.dom.events,org.w3c.dom.ls,org.xml.sax,org.xml.sax.ext,org.xml.sax.helpers