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

Test case chaining #3627

Closed
Formartha opened this issue Jun 28, 2018 · 3 comments
Closed

Test case chaining #3627

Formartha opened this issue Jun 28, 2018 · 3 comments
Labels
type: question general question, might be closed after 2 weeks of inactivity

Comments

@Formartha
Copy link

Hi folks,

I got a usercase where I need to chain couple E2E tests together. The must run in a specific order and each will provide output to another test.

The trick is that all off the tests are huge, due to it - they sit under different python modules.

I thought about building a singleton adapter for it, but I tend to think that it's too much of an overhead.

Any ideas or a plugin that can do it?

@pytestbot
Copy link
Contributor

GitMate.io thinks possibly related issues are #1123 (does pytest support to this way to collect test cases?), #3198 (Ignore individual tests), #1521 (High memory usage if tests called by test case name), #2076 (Case Scenario long integration test - including reference data), and #3478 (Print out only the test cases name).

@RonnyPfannschmidt RonnyPfannschmidt added the type: question general question, might be closed after 2 weeks of inactivity label Jun 28, 2018
@avadhanij
Copy link

We use a pytest plugin internally. Through this, we check for a particular marker in the runtest setup hook and check to see if this particular test depended on some other testcase and made sure that testcase had actually passed.

@Zac-HD
Copy link
Member

Zac-HD commented Oct 19, 2018

https://pytest-ordering.readthedocs.io might help.

@Zac-HD Zac-HD closed this as completed Oct 19, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: question general question, might be closed after 2 weeks of inactivity
Projects
None yet
Development

No branches or pull requests

5 participants