1 $Id: Notes,v 1.1 2006-05-31 12:04:19 mike Exp $
3 Some things that it would be nice to check (varying priorities!)
5 - Response to a second Z39.50 Init
7 - Whether referenceId is properly implemented
9 - Whether attribute-set is inspected and honoured
11 - How SRU servers respond to bad HTTP headers
13 - Malformed queries such as "@and foo"
15 Add plugin architecture for additional tests. Allow each test to
16 specify whether it is CRUCIAL, DESIRABLE or whatever, and the
17 frequency with which it is run.
19 Note results of each individual test (where?) and raise an alert when
20 a test gives a different result from the previous time.
22 Capture more information about what goes wrong at low levels. Does
23 YAZ itself allow an APDU log to be generated or is it still only
24 yaz-client and/or GFS that does this?
26 Make a queue of servers to be queried, and keep the pod "sufficiently
27 full", throwing a new one in as an older one is exhausted.
29 Two weeks to have framework running.
31 Test dependent on other test; use results from previous test as input
32 for this one. One test that is the aggregate of others.
34 Have a pre-cooked set of sample words to use in queries in the hope of
35 finding one or more records; remember which words work well for each
38 Make this into Alvis work by adding a subject-sniffer for the peer
39 network. Use the extended ZeeRex records to produce Alvis D3.1
40 peer-description records using XSLT that Marc will write.