On Wednesday, May 16, 2012 8:00:25 PM UTC-7, Ryan McGuire wrote:
I gave Doug commit rights to the blogofile repos on github yesterday, I think he's got a good plan for moving forward. If there's anything I can do to help things along, let me know.
Thanks for the commit access on the repos, and for the endorsement of my plan.
I'm not having very much luck getting the test suite in the plugins branch to work. I wonder if you have any recollections, suggestions, or magical incantations you can share.
Running the tests via python setup.py test fails because 3to2 can't build the package. Initially 3to2 failed to refactor 2 of the tests in tests/browser/test_chrome.py, so I dropped those. Then it failed in setup.py, so I decided to set multi-version testing and tox aside for the moment and focus on getting the tests to run just under Python 3.2.
Oddly, using py.test
as the test runner, I get different results, 16 failures, 3 passes, and 5 tests with errors, and the typical traceback is https://gist.github.com/2728853
I haven't tried nose as the test runner yet.
I suspect the problem in both cases is that the test aren't finding some of the fixtures, but I figured I might as well ask if you have any clues to offer before I bang my head against this too hard. I guess I can also ask the dumb question: was the plugins test suite passing for you when you left off work on it? I see several commented out tests with notes about them not working, so I presume the rest did, but maybe that's a bad assumption.
Any suggestions welcome...