Consultancy
A collaboration between The Software Sustainability Institute and the Provenance Tool Suite team at Electronics and Computer Science at the University of Southampton.
The aims of our collaboration are as follows.
- Deployment experience report. A report summarising experiences of deploying Provenance Tool Suite and setting up a local development environment for building and testing its packages and services.
- Round-trip interoperability test specification. Specification of round-trip interoperability tests to be implemented with reference to PROV and packages and services of the Provenance Tool Suite.
- Round-trip interoperability test harness design. Design for a test harness which systematically checks convertibility and round-trip conversions across combinations of these.
- Round-trip interoperability test harness. Test harness implementation, with implementation of round-trip interoperability tests specified in the Round-trip interoperability test specification. The test harness will be complemented with documentation on how to deploy, maintain and extend the test harness.
For the background to this work, please see Provenance Tool Suite on the Software Sustainability Institute web site.
Notes, commands and code excerpts used as the basis of this report are in:
Sample guides based on current pages and adopting recommendations from Tool Deployment Experiences
- ProvToolbox:
- ProvPy:
- ProvJS:
Interoperability test harness
Test cases
Comments on issues raised by Dong, Luc and Danius:
- Evaluate nose-testconfig for configuration #6
- HTML test report generation #8
- Running test cases in parallel #9
- Invoking interop jobs automatically #10
- Isolate specific job configurations and framework configurations #11
Inter-operability test harness, partitioned into a core framework and component specific packages (in package
branches):
- interop-test-harness
- provpy-interop-job
- provstore-interop-job
- provtoolbox-interop-job
- provtranslator-interop-job
- Tests to checks ProvValidator and ProvStore services work by running basic REST invocations and checking for 2xx/3xx HTTP responses.
- GitHub
- TravisCI
- Pull request with configuration configuration files needed to run the Jasmine NodeJS tests using both Grunt and Karma, and a Travis CI job file.
- Merged into ProvJS
- TravisCI