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

warn when fixtures are imported instead of referenced via a plugin/conftest #1511

Open
RonnyPfannschmidt opened this issue Apr 13, 2016 · 1 comment
Open

warn when fixtures are imported instead of referenced via a plugin/conftest #1511

RonnyPfannschmidt opened this issue Apr 13, 2016 · 1 comment
Labels
type: backward compatibility might present some backward compatibility issues which should be carefully noted in the changelog type: enhancement new feature or API change, should be merged into features branch

Comments

@RonnyPfannschmidt
Copy link
Member

i keep running into people that import fixtures thus ending up with hard to debug duplicates and/or longer test-runs

i think its critical to warn when fixtures are imported directly - if a duplicate is wanted, it should be more explicitly stated
@RonnyPfannschmidt RonnyPfannschmidt added type: enhancement new feature or API change, should be merged into features branch type: backward compatibility might present some backward compatibility issues which should be carefully noted in the changelog status: critical grave problem or usability issue that affects lots of users labels Apr 13, 2016
@RonnyPfannschmidt RonnyPfannschmidt added this to the 2.10 milestone Apr 13, 2016
@nicoddemus nicoddemus modified the milestones: 2.10, 3.0 Jun 26, 2016
@RonnyPfannschmidt RonnyPfannschmidt removed the status: critical grave problem or usability issue that affects lots of users label Jul 15, 2016
@The-Compiler
Copy link
Member

While this is a nice feature, it shouldn't block 3.0. Changing the milestone to 3.1 for now.

@The-Compiler The-Compiler modified the milestones: 3.1.0, 3.0 Aug 5, 2016
@nicoddemus nicoddemus mentioned this issue Feb 15, 2017
Closed
@RonnyPfannschmidt RonnyPfannschmidt modified the milestones: 3.1, 3.2 Jul 21, 2017
@RonnyPfannschmidt RonnyPfannschmidt removed this from the 3.2 milestone Feb 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: backward compatibility might present some backward compatibility issues which should be carefully noted in the changelog 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
3 participants
@RonnyPfannschmidt @The-Compiler @nicoddemus