This document describes the test method and test results of the Grimoires project.
JUnit is used as a test tool in the Grimoires project.
In Grimoires' build.xml, there is an ant target "test-junit", which runs the junit test suite to test against a deployed Grimoires. Before run this target, you need to set up the "wstester/bos.properties" file. For instance, if Grimoires is deployed on the http://localhost:18080/grimoires/, registryBaseURL = http://localhost:18080/grimoires/services.
We have maintained an online nightly JUnit test report, which will be run at each night.
If Jena is used as the triple store, the JUnit test expects 2 errors and 5 failures:
| Test case | Error/failure reason |
| testGetBusinessDetail2 | The test case itself does not follow the Java binding spec. This is not a bug in Grimoires service. |
| testRelationshipFindRelatedBusinesses1 | Grimoires does not fully support "business relationship"-related operations. |
| testRelationshipGetAssertionStatusReport1 | Grimoires does not fully support "business relationship"-related operations. |
| testRelationshipDeletePublishAssertions1 | Grimoires does not fully support "business relationship"-related operations. |
| testRelationshipSetPublishAssertions1 | Grimoires does not fully support "business relationship"-related operations. |
| testRelationshipGetPublishAssertions1 | Grimoires does not fully support "business relationship"-related operations. |
| testUserGetRegisteredInfo1 | Grimoires does not fully support UDDI get_registeredInfo operation. |
If Sesame is used as the triple store instead of Jena, more errors/failures are expected. This is because Sesame does not support regular expression in searching. Note regular expression is not required by the UDDI specification.
There is a paper describing the performance benchmark methodology and results.