This part is intended for JNode testers.
Here you can find informations related to the tests on filesystems.
Running the tests outside of JNode
With Ant run the target tests in the file /JNode-All/build.xml.
The results are sent to the standard output and unexpected exceptions are also sent as for any other JAVA application.
To debug the functionalities whose tests are failing, you can use Log4j that is configured through the file /JNode-FS/src/test/org/jnode/test/log4jForTests.properties.
By default traces are sent to the localhost on the port 4445. I recommand to use Lumbermill as a server to receive the log4j messages.
Running the tests in JNode
Type AllFSTest in the JNode shell. The results and unexpected exceptions are sent to the console. Log4j is automatically configured by JNode itself and manually with the shell command log4j.
We assume in the following tests that IP address of JNode is 192.168.44.3.
The JNode-shell project includes a test harness for running "black-box" tests on JNode commands and scripts. The harness is designed to allow tests to be run both in a development sandbox and on a running JNode system.
The test methodology is very straight-forward. Each testcase consists of a JNode alias, Java classname or inline script, together with an optional set of arguments and an optional inline input file. The command (alias or class) or script it run with the prescribed arguments and input, and the resulting output stream, error stream and return code are compared with expected results in the testcase. If there are any discrepancies between the expected and actual results, the testcase is counted as "failed". If there are any uncaught exceptions, this counts as a test "error".
The testcases are specified in XML files. Examples may be found in the JNode-Shell project in the "src/test" tree; e.g. "src/test/org/jnode/test/shell/bjorne/bjorne-shell-tests.xml". Each file typically specifies a number of distinct testcases, as outlined above. The "all-tests.xml" file (i.e. "shell/src/test/org/jnode/test/shell/all-tests.xml") should include all tests in the shell tree.
Running tests from Eclipse
The following steps can be used to run a set of tests from Eclipse.
You should now see a Console view displaying the output from running the tests. The last line should give a count of tests run, failures and errors.
Running tests from the Linux shell
Running the tests from the Linux shell is simply a matter of doing what the Eclipse launcher is doing. Put the relevant "JNode-*/classes" directories on the classpath, then run:
java org.jnode.test.shell.harness.TestHarness <xxx-tests.xml>
Running tests from within JNode.
In order to run the tests on the JNode platform, you must first boot JNode with the all plugins and tests loaded. Then, run the following command at the JNode command prompt:
org.jnode.test.shell.harness.TestHarness -r /org/jnode/test/shell/all-tests.xml
Notes:
TestHarness command syntax.
The TestHarness command has the following syntax:
command [ <opt> ...] <spec-file> ...
where <opt> is one of:
--verbose | - v # output more information about tests run
--debug | - d # enable extra debugging
--stopOnError | -E # stop test harness on the first 'error'
--stopOnFailure | -F # stop test harness on the first 'failure'
--sandbox | -s <dir-name> # specifies the dev't sandbox root directory
--resource | -r # looks for <spec-file> as a resource on the classpath
The first two options enable more output. In particular, "-d" causes all output captured by the harness to be echoed to the console as it is captured.
The "-s" option can be used when the running the test harness outside of JNode when the root of the development sandbox is not "..".
The "-r" option tells the harness to try to find the test specification files on TestHarness's classpath rather in the file system. This allows the test harness to be run on JNode without the hassle of copying test and test suite specification files into the JNode filesystem.
Note that the TestHarness command class does not implement JNode's "Command" API, so command completion is not available when running on JNode. This is a deliberate design decision, not an oversight.
Reading and writing test specifications.
If a test fails, you will probably need to read and understand the test's specification as a first step in diagnosing the problem. For a description of specification file syntax and what they mean, please refer to the Black-box command tests with TestHarness page.
To run the mauve tests, proceed as follow :
- boot JNode and choose the choose the option "all plugins + tests" (should be the latest choice in the menu), that will allow you to use the mauve plugin.
- when boot is finished, type the command cd /jnode/tmp to go in a writable directory
- type mauve-filter and answer to the asked questions, that will create a file named "tests" in the current directory
- type testCommand and the tests will run
If you find some bugs by this way, don't forget to submit it or fix it. Depending on the case, it is possible that a patch to fix the bug is needed on Classpath/Openjdk side ... and/or on JNode side.
We have created a straight-forward way to run various tests from the Linux commandline in the development sandbox. The procedure is as follows:
$ ./test.sh all
For brief help on the script's arguments, just run "./build.sh" with no arguments.
The "./build.sh" script is just a wrapper script for using Ant to run tests that are
defined as targets in the "<project>/build-tests.xml" files. You can add new
tests to be run by adding targets, or (if required) cloning an existing file into
a project that doesn't have one.
TODO