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

[ENH] Investigate where mocking can be used in unit tests to improve flakiness, speed up test suite #816

Open
peytondmurray opened this issue Apr 30, 2024 · 0 comments

Comments

@peytondmurray
Copy link
Contributor

Context

Currently there are many unit tests which are not very isolated. For example many tests reach out to conda-forge, and are therefore at risk of producing false failures for any number of network-related issues that are unrelated to the code being tested.

This issue is to plan and potentially track the work needed to mock out external dependencies, better isolating the unit tests to the code that we actually want to test.

One suggestion has been to run our own package repository locally, making it unnecessary for conda-store to make requests to conda-forge.

Value and/or benefit

The test suite is currently flaky. This should help reduce flakiness and has the potential to greatly speed up testing, as waiting on external resources takes a lot of time.

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New 🚦
Development

No branches or pull requests

1 participant