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

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

Open
humbienri opened this issue Mar 23, 2020 · 1 comment
Open

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

humbienri opened this issue Mar 23, 2020 · 1 comment

Comments

@humbienri
Copy link

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
Copy link
Author

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.

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

1 participant