What's this?
============

It's an attempt to come up with a validation suite for ADQL implementations.

The idea is to specify the test cases in a suite of XML files ("levels",
cf. whiteboard-copy) that implementors can easily parse and run
against their implementations.

There's also some defined tables in DDL that's supposed to be fairly 
portable (buildTable.sql).  Those would need to be ingested into the
database behind the ADQL engine.


Test Specifications
===================

Test specifications are organized in testGroups.  These may have a
name attribute for use in informing the user what is running.

A test group contains tests.  The query to run is always the character
content, the expected results are either in attributes or in child 
elements.

The following test types are defined:

cardTest
	These have a res attribute containing an integer.  If the integer is 
	positive, it gives the number of result rows, if it is negative, it
	the expected number of results is |testSet|+res.

intResTest
	These test if a given query (a) return exactly one row (b) this row
	contains exactly one column and (c) the value in this column is
	integer given in res.

charResTest
	These work like inResTest except the value in res is interpreted as
	a string and the value returned is compared against that string.