Preconditions

• iValidator needs min. JDK 1.3
• the Eclipse Plugin needs min. Eclipse 3.0.1

Download

iValidator download is provided on Sourceforge.

You can download a binary version and/or an eclipse plug-in of iValidator:

• The binary version can be started on the commandline or via ant. It is intended for automated execution of large scenarios, e.g. overnight.

• The eclipse plugin provides interactive use during the development process. This helps to develop tests parallel to the application development and rerun failed test scenarios for fault finding and error correction.

All test implementations and definitions can naturaly be run either from the commandline or in the plugin without any changes!

There are no differences for Unix and Windows implementation. Additionally the iValidotor sources are available in a separate download archive. The download archives contain all necessary jars.

It is advisable to download the samples as well because they provide a mini application to evaluate the framework.

Tutorial

Starting with version 2.3.2 we offer a Getting Started Tutorial (German Version).

iValidator Binaries and iValidator Samples

Unzip the archives into a directory of your choice.

The sub directories /ivalidator (refered to as IVALIDATOR_HOME) and /ivalidator-samples (refered to as IVALIDATOR_SAMPLE) will be created automatically.

Okay, the framework ist now available. Use the sample application to get a first impression.

iValidator Sample Application

The directory org.ivalidator.sample.testapp contains a mini application to provide a system under test (SUT).

The directory org.ivalidator.sampl.base contains the corresponding iValidator test setup for tests of the SUT. You will find

• Adapter to connect to the SUT,
• Units to perform tests,
• XML-TestDescriptions for several scenarios in the subdirectory '/input'
• several XML-Configurations (configuration.xml, config_simple.xml, ...) as startup parameter for the iValidator Testrunner

Starting the Test

So, to start a Test, go to the directory IVALIDATOR_SAMPLE/org.ivalidator.sample.base and type:

java -jar IVALIDATOR_HOME/ivalidator.jar configuration.xml

If you are not in the correct directory when issuing the command, the testdescriptions will not be found.

Starting the Test using Ant

Instead of using an iValidator configuration.xml, you can use the iValidator Ant Task to configure and start a test. To try that, go to the directory IVALIDATOR_SAMPLE/org.ivalidator.sample.base and type:

ant -buildfile ant_run_config_simple.xml

It might be necessary to set the IVALIDATOR_HOME variable in the  ant_run_config_simple.xml.

Viewing the Results

The results of the testrun can be found in the subdirectory '/result', resp. /ant_result, depending on how you started the tests. They are XML-Reports containing a stylesheet that uses a bit of javascript for presentation and navigation within the report.

Some test intenionally produce errors to demonstrate the effect.

iValidator Eclipse Plugin and iValidator Samples

Unzip the download archive into the plugin directory of your eclipse installation (min. release 3.0.1). After restarting eclipse the iValidator is available as a plugin with the following features:

• A launch configuration shortcut: a testrun can be started by right-clicking on a configuration file and selecting "Run" -> "iValidator Run"
• A launch configuration dialog
• An iValidator View to present the report of the testrun "on the fly".

iValidator Sample Application

You can use the sample application to evaluate the plugin:

• Copy directories org.ivalidator.sample.testapp and org.ivalidator.sample.base from the samples download archive into your Eclipse workspace.
• Create 2 new Java project with the names org.ivalidator.sample.testapp and org.ivalidator.sample.base by using File->New->Project->Java-Project. The files from copied directory are automatically imported into your new project.
• In the project org.ivalidator.sample.base a project dependency to project org.ivalidator.sample.testapp must be established by right clicking on the Project Properties and select Java-Build-Path->Projects. (Depending on the downloaded release it might already exist)
• Depending on the downloaded release a project dependency to org.ivalidator.framework may exist. This should be removed
• Then insert/update a variable IVALIDATOR_HOME with the extension ivalidator.jar to the Java Build Path of the project by using Java-Build-Path->Libraries->Add-Variables and Extend... button.

The project org.ivalidator.sample.testapp contains a mini application to provide a system under test (SUT).

The project org.ivalidator.sampl.base contains the corresponding iValidator test setup for tests of the SUT. You will find

• Adapter to connect to the SUT,
• Units to perform tests,
• XML-TestDescriptions for several scenarios in the subdirectory '/input'
• several XML-Configurations (configuration.xml, config_simple.xml, ...) as startup parameter for the iValidator Testrunner

Starting the Test

You can start using iValidator plug-in in two ways.

• Click button "Run..." and the Launch Configuration Dialog will pop up.
• Right-click directly on the file configuration.xml and a launch shortcut can be performed. "Run as..." -> "iValidator Run"

Viewing the Results

In addition to the output in an XML-Report file as described above, the report is shown in the iValidator view of your eclipse environment. Icons give a quick view of success, warnings and errors and you can click through the test hierarchy levels to find runtime information and error or success messages for every suite and unit.

Some test intenionally produce errors to demonstrate the effect.