[oslc-core] Test Suites for OSLC Specifications

[Steve K Speicher]

Arthur,

Thanks for starting this discussion.  The Eclipse Lyo project (and its 
predecessor oslc-tools on sourceforge.net) have a component intended to 
assist testing both servers (providers) and clients (consumers).  The 
current approach is similar to what you outline, as a way to test 
positive/negative aspects of the specifications.  It is being structured 
to test a specific domain specification.  Since the domain specs build off 
of Core, they share a large number of tests and framework.  In addition, 
we'd like to have a nice way to integrate any existing test suites (RDF, 
HTTP, JSON, etc) instead of recreating these.

Even though the current test suite in Lyo using JUnit to drive the test 
suite, it uses only HTTP to communicate with the server (and therefore 
implementation-neutral).

It would be great to hear of others have thoughts and feedback the test 
suite.

Thanks,
Steve Speicher | IBM Rational Software | (919) 254-0645

> From: Arthur Ryman <ryman at ca.ibm.com>
> To: oslc-core at open-services.net, 
> Date: 10/04/2011 05:29 PM
> Subject: [oslc-core] Test Suites for OSLC Specifications
> Sent by: oslc-core-bounces at open-services.net
> 
> I'd like to start a discussion on how we should handle test suites. Test 

> suites are very valuable for improving the quality of specs and for 
> guiding implementers. Organizations like the W3C require test suites. 
For 
> example, RDF has a test suite [1]
> 
> Currently there are no test suites at OSLC. The Eclipse Lyo project has 
> proposed to create test cases, which is a great step forward. However, 
we 
> should make a clear distinction between test cases that are 
> implementation-neutral versus test cases that are for a given 
> implementation. In particular, the organization that owns the 
> specification should also own the implementation-neutral test cases for 
> it.
> 
> In the case of RDF, the test suite consists of a set of RDF documents 
that 
> cover as many of the features as possible. Both valid and invalid 
> documents should be in the test suite. The meaning of valid RDF/XML 
> documents is expressed by giving the corresponding set of RDF triples 
> expresses in the much simpler N-triples syntax. 
> 
> For OSLC specs, we should provide test cases that give both valid and 
> invalid resources formats, and for HTTP protocol interactions, the 
> expected request and response pairs.
> 
> The Eclipse Lyo project should use these OSLC test suites to validate 
its 
> implementation. Implementers like Lyo should be encouraged to contribute 

> implementation-neutral test cases to the OSLC test suites.
> 
> [1] http://www.w3.org/TR/rdf-testcases/
> 
> Regards, 
> 
___________________________________________________________________________ 

> 
> Arthur Ryman 
> 
> DE, PPM & Reporting Chief Architect
> IBM Software, Rational 
> Toronto Lab | +1-905-413-3077 (office) | +1-416-939-5063 (mobile) 
> 
> 
> 
> _______________________________________________
> Oslc-Core mailing list
> Oslc-Core at open-services.net
> http://open-services.net/mailman/listinfo/oslc-core_open-services.net