- From: Tomasz Pluskiewicz <tomasz@t-code.pl>
- Date: Thu, 20 Jun 2019 09:13:26 +0200
- To: "public-hydra@w3.org" <public-hydra@w3.org>
Hello Hydra At Zazuko, we have recently started drafting a testing DSL dedicated to Hypermedia APIs. At this point it naturally focuses on Hydra but technically any hypermedia API could be tested in a similar manner. The difference from other HTTP API test tools I know is the focus solely on links and form (operations). The tests should operate like a dynamic client, where next steps are determined by nothing else but the resource representations, ie. “follow your nose”. Why DSL? We’d like to offer a rich IDE support, although it should not be necessary. It will be “compiled” to a more technical form, later to be processed by a test runner. Please have a look at this gist [1]. I’d like to hear your thoughts. I know that not everything is entirely clear ATM; I will be happy to answer any questions. As first implementation I extend the code behind hydra analyser [2], [3] to consume the description and run tests against an API. Best, Tom [1]: https://gist.github.com/tpluscode/2f32c7d488ea434960f2a9b1721bbc82 [2]: https://analyse.hypermedia.app [3]: https://github.com/hypermedia-app/hydra-validator
Received on Thursday, 20 June 2019 07:13:56 UTC