-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
Verbosity and --fixtures / --fixtures-per-test #8606
Copy link
Copy link
Closed
Labels
topic: fixturesanything involving fixtures directly or indirectlyanything involving fixtures directly or indirectlytype: proposalproposal for a new feature, often to gather opinions or design the API around the new featureproposal for a new feature, often to gather opinions or design the API around the new feature
Metadata
Metadata
Assignees
Labels
topic: fixturesanything involving fixtures directly or indirectlyanything involving fixtures directly or indirectlytype: proposalproposal for a new feature, often to gather opinions or design the API around the new featureproposal for a new feature, often to gather opinions or design the API around the new feature
Something that's usually interesting to know when checking what fixtures exist in a project is where exactly they are defined. In other words, imagine I'm looking at a test, and I want to know where those fixtures are coming from.
Intuitively, I'd run with
--fixtures-per-test, which shows me the fixture names and docstrings, but I still don't know where they come from. I was today years old when I learned that adding--verbosewill show that information.I think there's nothing particularly verbose about it, though! It's just one line, which will usually fit on the same line as the fixture name anyways! However, something that's very verbose (sometimes) are the docstrings...
What about:
--verboseis given?