Skip to content

Verbosity and --fixtures / --fixtures-per-test #8606

@The-Compiler

Description

@The-Compiler

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 --verbose will 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:

  • Always showing the path to the fixtures
  • Only showing the first line of the docstrings unless --verbose is given?

Metadata

Metadata

Assignees

No one assigned

    Labels

    topic: fixturesanything involving fixtures directly or indirectlytype: proposalproposal for a new feature, often to gather opinions or design the API around the new feature

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions