W3C home > Mailing lists > Public > spec-prod@w3.org > April to June 2017

[Echidna] New feature: dry run

From: Antonio Olmo Titos <antonio@w3.org>
Date: Tue, 18 Apr 2017 17:06:27 +0200
To: Spec-prod <spec-prod@w3.org>
Cc: Denis <denis@w3.org>
Message-ID: <07001401-f392-b1cc-71a9-39fcb892f068@w3.org>

we just deployed Echidna v1.12.0 [1] in production [2].

Apart from other improvements and fixes [3][4], we wanted to call your attention
to a new feature that we hope you will find useful: dry runs [5].

If the new optional parameter “dry-run” is set to “true” (case-insensitive string),
the document will *not* published, and *no* e-mail notification will be sent to
public-tr-notifications. All other usual steps prior to actual publication are
taken, though (the document is retrieved, the user authenticated, metadata
extracted, and Specberus rules applied); errors and warnings may occur normally:

     $ curl 'https://labs.w3.org/echidna/api/request' -d 'dry-run=true' ...

Right now, the only way to check the results of a dry run of Echidna is via the
“status” method of the API [6]:

     $ GET https://labs.w3.org/echidna/api/status?id=<JOB-ID>

Wiki page [7] updated with this info.

We are thinking of letting users pass to Echidna an e-mail address to receive
the results; that may be ready soon. We think the combination of these two
features will help you detect errors on specs sooner and with less overhead.

[1] https://github.com/w3c/echidna/releases/tag/v1.12.0
[2] https://labs.w3.org/echidna/
[3] https://github.com/w3c/echidna/pull/428
[4] https://github.com/w3c/echidna/pull/430
[5] https://github.com/w3c/echidna/pull/424
[6] https://github.com/w3c/echidna/wiki/How-to-use-Echidna#apistatus
[7] https://github.com/w3c/echidna/wiki/How-to-use-Echidna#rehearse-publication-dry-run

Antonio Olmo Titos — web developer, W3C
antonio@w3.org · https://w3.org/People/Antonio
Received on Tuesday, 18 April 2017 15:06:36 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 18 April 2017 15:06:37 UTC