id summary reporter owner description type status component version severity resolution keywords cc stage has_patch needs_docs needs_tests needs_better_patch easy ui_ux
21793 Require specific versions of test suite's Python dependencies? JustinTArthur nobody "Currently, there are several tests that depend on 3rd party libraries that we haven't assimilated into the source code directly. These tests are simply skipped/passed when a developer or tester's environment is missing one of these libraries.
The question is:
Do we want to specify the preferred versions of these dependencies in [https://github.com/django/django/tree/master/tests/requirements test/requirements/*.txt]?
Additionally:
Do we want to have the CI environment(s) use those text files for the automated testing we do? (they currently don't according to [https://github.com/timgraham timo])
I vote for at least adjusting those text files to refer to the same dependency versions as our CI environments are currently using for the sake of giving contributors a consistent regression testing process (their passing-on-local test less likely to fail-on-continuous-integration).
We may also have a day when a developer's local test suite goes red, not because Django has regressed, but because one of the test's dependencies has changed in API or behavior. This could be desired behavior? I don't know.
Ticket inspired by a #django-dev conversation with [https://github.com/timgraham timo] on 2014-01-16 with regards to [https://github.com/django/django/pull/2173 pull request 2173], which adds a dependency to a specific version of a 3rd-party library." Cleanup/optimization new Testing framework master Normal testing,test suite,continuous integration,ci,dependencies,pip,pypi Accepted 0 0 0 0 0 0