[gcs-pcs-list] test suite.

[Xiaoming Liu]

On Fri, 3 Mar 2006, Daniel Chudnov wrote:

> Ed Summers wrote, on Fri, Mar 03, 2006 at 03:32:16PM -0600:
>>> Or, actually, any unAPI test suite would be cool, too:  just point
>>> it at some page in your webapp that has at least one unapi-uri and
>>> see if it will do all the stuff you expect.
>>
>> I'm willing to try this. Can you sketch out what you would want it to
>> exercise and check?


In OAI-PMH development, Alan Kent has some good input about testing 
and actually setup a nice site for this. Unfortunately the site has long 
gone, if you are interested, I just found several links:

-- search oai-implementor email list, such as this one
http://www.openarchives.org/pipermail/oai-implementers/2002-February/000347.html

-- his SOAP test site is still available from archive.org
http://web.archive.org/web/*/http://www.mds.rmit.edu.au/~ajk/soap/interop-results.htm

-- and celestial has some similar flavor
http://celestial.eprints.org/cgi-bin/status

maybe these have some reference value.

xiaoming


>
> Hooray for edsu! :)
>
> I *think* the simplest thing that might work would be:
>
> - A commandline app or web form into which you could paste a url
>   (alternately a bookmarklet that would send the current page in)
> - The url should be a web page with at least one unAPI
>   unapi-uri span element and the unAPI link element.
>   - If there's no unapi-uri, but there is a unAPI link element, check
>     that the UNAPI? formats response is correct and stop
>   - If there's no link element, indicate the error and stop
> - Check that the following works:
>   - The UNAPI? formats response is correct (xml pattern and 300 code)
>   - The UNAPI?uri=URI response is correct (xml pattern and 300 code)
>   - For each format listed in UNAPI?uri=URI, verify that the
>     response headers are as advertised (esp. mime-type)
> - Check that the following fail correctly:
>   - Some bad UNAPI request (e.g. UNAPI?format=FORMAT) should return
>     400
>   - Make up a bad URI (info:bad-uri/BAD!-BAD!-BAD! :) and
>     UNAPI?uri=URI should return a 404
>   - For a good URI (one you discover in a unapi-uri span) try a
>     format that isn't listed; should return a 415
>
>
>> I could start out with a simple command line app, and then put it
>> behind a web app if you want.
>
> Any working start on any of this would be way cool.  Style points for
> AJAX whiz-bang and slick CSS layout will not be included in the final
> judging (we can always add that later :P).
>
>  -Dan
>
>
>