Next Previous Up Contents
Next: tapquery: Queries a Table Access Protocol server
Up: taplint: Tests TAP services
Previous: Usage

### B.22.2 Examples

Here are some examples of `taplint`:

    stilts taplint http://dc.g-vo.org/tap

  Performs a default validation run against the TAP service based at the given URL.

    stilts taplint tapurl=http://gaia.esac.esa.int/tap-server/tap
                   examplesurl=file://localhost/tmp/examples.xml
                   stages='TME CAP EXA'

  Executes the `EXA`mples stage against the GACS TAP service at ESAC. Most of the service endpoints (tables, capabilities, availability etc) are found at their default locations relative to the given `tapurl`. However, the Examples document is loaded instead from the local file at the URL that has been specified by the `examplesurl` parameter. This makes is possible to test a non-deployed examples document against a deployed TAP service. It may also be used if certain capabilities have been deployed at non-default locations to satisfy multiple security models or for other reasons. You can play similar tricks with the other `*url` parameters like `capabilitiesurl` and `tablesurl`, as listed in the documentation.

  The `TME` (table metadata) and `CAP` (service capabilities) stages have been executed along with `EXA`, since taplint needs to pick up the metadata and capabilities in order to be able to do some of the checks on the examples it finds. If those stage names are not included in the `stages` parameter, the output will include some messages noting that fact, and the tests will be less rigorous.

    stilts taplint tapurl=http://example.com/tap
                   report=EW stages='TMS UWS' truncate=80 maxrepeat=4

  A validation run is done against the named TAP service. Only Error and Warning type messages are output, only two validation stages are performed, lines are truncated to a maximum of 80 characters, and each message is repeated a maximum of 4 times. An invocation like this may be suitable if you find the default operation too verbose.

  The output of this invocation might look like this:

          Section TMS: Check content of tables metadata from TAP_SCHEMA
      E-TMS-CINT-1 Column principal in TAP_SCHEMA.columns has wrong type char not int
      E-TMS-CINT-2 Column std in TAP_SCHEMA.columns has wrong type char not int
      W-TMS-CLUN-1 Unused entry in TAP_SCHEMA.columns table: ivoa.obscore

      Section UWS: Test asynchronous UWS/TAP behaviour
      E-UWS-GMIM-1 Incorrect Content-Type text/xml != text/plain for http://exampl....
      E-UWS-GMIM-2 Incorrect Content-Type text/xml != text/plain for http://exampl....
      E-UWS-GMIM-3 Incorrect Content-Type text/xml != text/plain for http://exampl....
      E-UWS-GMIM-4 Incorrect Content-Type text/xml != text/plain for http://exampl....
      E-UWS-GMIM-x (3 more)

      Totals: Errors: 9; Warnings: 1

Next Previous Up Contents
Next: tapquery: Queries a Table Access Protocol server
Up: taplint: Tests TAP services
Previous: Usage

STILTS - Starlink Tables Infrastructure Library Tool Set
Starlink User Note256
STILTS web page: http://www.starlink.ac.uk/stilts/
Author email: m.b.taylor@bristol.ac.uk
Mailing list: topcat-user@jiscmail.ac.uk