diff options
author | Alex Clayton <alex.clayton@isode.com> | 2018-07-19 12:40:16 (GMT) |
---|---|---|
committer | Alex Clayton <alex.clayton@isode.com> | 2018-08-09 12:46:43 (GMT) |
commit | e906d1c46a854de703017cbb05e1adde5babe417 (patch) | |
tree | 55516b842367b0d9cb53ed796b2dc9c2892c924a /test/com/isode/stroke/serializer | |
parent | 17a1e7662102eea20ddc104133e2e30a70fefdc1 (diff) | |
download | stroke-e906d1c46a854de703017cbb05e1adde5babe417.zip stroke-e906d1c46a854de703017cbb05e1adde5babe417.tar.bz2 |
Update stroke junit tests so it can cope with the latest version of
Junit 4 (4.12) which no requires both Junit and Hamcrest to be on the
classpath.
This is done using a method similar to how JUNIT is currently set.
The make file passes a new HAMCREST enviroment variable to the ant
script as HAMCREST_JAR which ant then adds to the tests classpath.
So to run the tests with the new JUNIT will need to set JUNIT to point
to junit.jar and HAMCREST to the hamcrest jar, then run Make test.
Also make use of ant's junitreport task to create a html version of
the junit test's results, which makes diagnosing failures easier.
Test-information:
After setting HAMCREST and JUNIT then running Make Test on OSX and
Unix all tests pass and HTML output is generated.
If HAMCREST is not set but JUNIT points to latest junit.jar (i.e one
that requires hamcrest on class path) tests fail with error about not
being able to find hamcrest classes.
If HAMCREST not set but JUNIT points to an older junit.jar then tests
run correctly.
On Windows got the unit tests to run by calling ant directly, again
with HAMCREST and JUNIT set tests run correctly.
Change-Id: I272b1dbe1bde05593df15f22814b7882a494f2c8
Diffstat (limited to 'test/com/isode/stroke/serializer')
0 files changed, 0 insertions, 0 deletions