Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing recipe #13

Open
tpluscode opened this issue Jul 16, 2019 · 4 comments
Open

Testing recipe #13

tpluscode opened this issue Jul 16, 2019 · 4 comments

Comments

@tpluscode
Copy link
Collaborator

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 and hydra-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.

@alien-mcl
Copy link
Member

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.

@tpluscode
Copy link
Collaborator Author

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?

@alien-mcl
Copy link
Member

Dunno, hts for hypertest? Does it have to be three letters long?

@angelo-v
Copy link
Contributor

I think this should go into the examples repo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants