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

New report hook to display messages after collection is finished #2622

Closed
nicoddemus opened this issue Jul 27, 2017 · 1 comment
Closed

New report hook to display messages after collection is finished #2622

nicoddemus opened this issue Jul 27, 2017 · 1 comment
Assignees
Labels
topic: reporting related to terminal output and user-facing messages and errors type: enhancement new feature or API change, should be merged into features branch type: feature-branch new feature or API change, should be merged into features branch

Comments

@nicoddemus
Copy link
Member

Introduce a new hook called by the terminal plugin after collection has been completed and before starting to run tests.

This allows plugins that modify the collection to more accurately report what will actually be executed, for example the --lf option from the cache plugin (see comment on #2621).

@nicoddemus nicoddemus added type: feature-branch new feature or API change, should be merged into features branch topic: reporting related to terminal output and user-facing messages and errors labels Jul 27, 2017
@nicoddemus nicoddemus self-assigned this Jul 27, 2017
nicoddemus added a commit to nicoddemus/pytest that referenced this issue Jul 27, 2017
@RonnyPfannschmidt
Copy link
Member

closing as fixed by #2623

@nicoddemus nicoddemus added type: enhancement new feature or API change, should be merged into features branch and removed type: enhancement new feature or API change, should be merged into features branch labels Sep 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
topic: reporting related to terminal output and user-facing messages and errors type: enhancement new feature or API change, should be merged into features branch type: feature-branch new feature or API change, should be merged into features branch
Projects
None yet
Development

No branches or pull requests

2 participants