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.

Sign up for GitHub

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

Jump to bottom

Logging of fixture setup #332

Closed
pytestbot opened this issue Jul 12, 2013 · 7 comments
Closed

Logging of fixture setup #332

pytestbot opened this issue Jul 12, 2013 · 7 comments
Labels
type: enhancement new feature or API change, should be merged into features branch

Comments

@pytestbot
Copy link
Contributor

Originally reported by: Wolfgang Schnerring (BitBucket: wosc, GitHub: wosc)

When you have expensive fixtures (e.g. set up whole database), starting a test run often takes a while, without any indication of progress. Thus it would be useful if there was some verbose loglevel that outputs each fixture as it is set up.
@pytestbot
Copy link
Contributor Author

Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):

yes, it'd be nice to have a log of which fixture/setup/teardown functions are invoked and maybe show that during "-vv" (double verbose) output or so. It would also show in which order which setup/fixture functions execute.

@pytestbot pytestbot added the type: enhancement new feature or API change, should be merged into features branch label Jun 15, 2015
@ghostsquad
Copy link

👍

@RonnyPfannschmidt
Copy link
Member

@RedBeardCode is that one solved by --setup-only/plan ?

@RedBeardCode
Copy link
Contributor

@RonnyPfannschmidt, sorry but I'm not into the --setup-only thing. I also don't know how is working on it.

@RonnyPfannschmidt
Copy link
Member

@RedBeardCode oh, sorry then i got that mismatched

@The-Compiler
Copy link
Member

That'd be @sallner and @kvas-it 😉

@nicoddemus
Copy link
Member

Yep. 🎆

I'm closing this as from my POV using --setup* is enough for the OP needs. 😁

@pytestbot pytestbot mentioned this issue Apr 12, 2018
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: enhancement new feature or API change, should be merged into features branch
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@RonnyPfannschmidt @The-Compiler @ghostsquad @nicoddemus @pytestbot @RedBeardCode