-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Setting up a test environment #781
Comments
Running The vagrant scripts configure a linux VM w/ multiple Redis and Sentinel processes running and expose those processes ports to the host OS. The VM currently isn't meant to run tox or py.test, but it probably could if you don't have another option. |
Thanks @andymccurdy. That's pretty much what I tried at first, but no joy. In retrospect, I think some bits of pip and python got cross-linked between python 2.7 and 3.5. I used a different vagrant box that I hadn't worked with before and apparently I killed that instance and setup a new one and In case it helps someone down the road, here's what I did to set things up:
|
Are there instructions somewhere on how to setup a test environment for redis-py? I'm working on a fix for #732. Besides the tests I run for my product, I'd like to run the automated redis-py unit tests before I submit a patch/pull-request.
I've installed tox and tried running it against redis-py, but I'm clearly missing some setup steps to get things configured. Presumably it's something to do with the various scripts in the vagrant directory, but I didn't find any READMEs that looked relevant.
The text was updated successfully, but these errors were encountered: