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

write tests specific to universal lock files #3880

Closed
Tracked by #3347
BurntSushi opened this issue May 28, 2024 · 1 comment
Closed
Tracked by #3347

write tests specific to universal lock files #3880

BurntSushi opened this issue May 28, 2024 · 1 comment
Labels
internal A refactor or improvement that is not user-facing

Comments

@BurntSushi
Copy link
Member

After #3831 lands, I should spend some time coming up with a bunch of test scenarios that specifically invoke the resolver without a marker environment. Pretty much all extant tests exercise a code path that invokes the resolver with a marker environment. So we should consider both adding new tests and exploring a way to leverage our existing test suite in a "universal" context.

Ref #3347

@BurntSushi BurntSushi added the internal A refactor or improvement that is not user-facing label May 28, 2024
@BurntSushi
Copy link
Member Author

I think this was closed by #4019.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
internal A refactor or improvement that is not user-facing
Projects
None yet
Development

No branches or pull requests

1 participant