Enhancement
HTTP interface documentation and tests
Issue description
The HTTP interface needs to be documented. Since this documentation will mainly address developers, it would be ok to have the behavior noted *formally*. This formal description of what the interface does can be used as a test suite as well.
So here is the plan:
* Set up a Topincs Store to hold the information
* Think of an ontology for HTTP interface description
* Use that ontology to describe the Topincs Interface
* Write a minimal program *P* , that can be integrated in Ant to generate the runnable tests
* The runnable tests can use Rhino to create an request, HTTPUnit to issue it and Rhino to apply post-conditions to the response.
Since *P* does computation, it will assume that certain statements hold for the data it is fed. This brings in the problem of validation.
Rejection comment
No need for that anymore.
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.