A spec MUST have a request and response minimally?

kiranz / just-api

:boom: Test REST, GraphQL APIs

https://kiranz.github.io/just-api/

MIT License

813 stars 35 forks source link

A spec MUST have a request and response minimally? #26

Open humbienri opened 4 years ago

humbienri commented 4 years ago

Hi again,

I am wondering...is it (or not) possible to separate a request from a response and have them reside in separate YML files? I am guessing not but wanted to confirm.

I specifically call it not a Spec because that term insinuates that it is a test. When it comes to intradependencies across suites...does the response part of a dependency also get executed and that spec is being called from another suite?

Thanks again!

humbienri commented 4 years ago

I did some experimenting and can confirm that when leveraging intra-suite dependencies only the request part, that is the REST API call, gets "used" or leveraged.

I did so by checking the expected Status Code in the dependency spec. So it seems to me that my idea of splitting the request call from the response validation is not really necessary to lower the overhead of running these tests.

Thank you.