Skip to content
This repository has been archived by the owner on Mar 26, 2021. It is now read-only.

Reusable tests #60

Closed
andreoav opened this issue Oct 15, 2018 · 5 comments · Fixed by #87
Closed

Reusable tests #60

andreoav opened this issue Oct 15, 2018 · 5 comments · Fixed by #87

Comments

@andreoav
Copy link

I think it is a good idea to be able to extract repeatable tests in dedicated files and import them.

Ex: I want to modularize some tests by domain, and each domain needs to have an initial authentication request that is common to all tests.

@jgroom33
Copy link
Collaborator

Would #57 provide this?

@jgroom33
Copy link
Collaborator

This seems possible in the existing chaining behavior. Can you describe the use case in greater detail?

@andreoav
Copy link
Author

I want to create 2 test suites, one for each specific business domain.
Each suite depends on an authentication token.

I don't want to copy and paste the login request in each suite, so I ask if there is a way to require the login request that is saved in another file.

@jgroom33
Copy link
Collaborator

So you want to do this:

version: 1
require: ../login.strest.yml
...

It's currently possible to execute tests on a directory. So this implementation could potentially exit the directory and run a set of tests.

Are there other use cases?

@jgroom33
Copy link
Collaborator

#86 is another implementation option

@jgroom33 jgroom33 mentioned this issue Oct 25, 2018
jgroom33 added a commit that referenced this issue Oct 25, 2018
* bulk tests via `-b`
* add --version

resolve #86
resolve #60
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants