Open tpluscode opened 5 years ago
I think examples' repo fits better. Sonner or later these examples may evolve into something that actually works, thus it may end up with fully blown working solutions with both code and tests.
BTW, I don't think that .api
file extension is well suited for a test spec. At first glance it may look like some kind of API specification, but not a test scenario.
BTW, I don't think that .api file extension is well suited for a test spec. At first glance it may look like some kind of API specification, but not a test scenario.
Interesting observation. Got any suggestions?
Dunno, hts
for hypertest? Does it have to be three letters long?
I think this should go into the examples repo
I would like to expand the movies example recipes with testing scenarios.
For that purpose, I would like to set up a minimal project using the testing DSL and runner I have been building:
@hypermedia-app/hypertest
andhydra-validator-e2e
(to be released soon in it's early form).Now, the question is whether the testing code itself would reside in the cookbook repo or in the movies API repo.