Skip to content

Pytest hook evaluation order diagram or list #3113

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

Closed
Drew-Ack opened this issue Jan 12, 2018 · 5 comments
Closed

Pytest hook evaluation order diagram or list #3113

Drew-Ack opened this issue Jan 12, 2018 · 5 comments
Labels
good first issue easy issue that is friendly to new contributor type: docs documentation improvement, missing or needing clarification

Comments

@Drew-Ack
Copy link

Referencing #3109 can we get a list or diagram that shows hook evaluation order?

@pytestbot
Copy link
Contributor

GitMate.io thinks the contributor most likely able to help you is @RonnyPfannschmidt.

@pytestbot pytestbot added the type: bug problem that needs to be addressed label Jan 12, 2018
@nicoddemus
Copy link
Member

If one executes pytest --debug, pytest will generate a pytestdebug.log file which shows the hook evaluation order, among other things. Is that what you mean @Drew-Ack?

@nicoddemus nicoddemus added type: question general question, might be closed after 2 weeks of inactivity and removed type: bug problem that needs to be addressed labels Jan 15, 2018
@Drew-Ack
Copy link
Author

I didn't realize that option was so thorough.
I was hoping more for a general diagram that could be included into the pytest documentation that would list the hook order. A diagram like the android lifecycle diagram here
Android Life Cycle Diagram

@nicoddemus
Copy link
Member

I was hoping more for a general diagram that could be included into the pytest documentation that would list the hook order.

Oh I see. Indeed that would be useful, thanks for the suggestion!

@nicoddemus nicoddemus added type: docs documentation improvement, missing or needing clarification good first issue easy issue that is friendly to new contributor and removed type: question general question, might be closed after 2 weeks of inactivity labels Jan 15, 2018
@Drew-Ack Drew-Ack reopened this Jan 15, 2018
@nicoddemus
Copy link
Member

Closing as a duplicate of #3261; normally we would keep the oldest issue around and close new ones as duplicates, but #3261 has a richer discussion going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue easy issue that is friendly to new contributor type: docs documentation improvement, missing or needing clarification
Projects
None yet
Development

No branches or pull requests

3 participants