[IPython-dev] Testing headaches
Wed Apr 15 17:15:38 CDT 2009
Yes, this is the type of thing that I am actually starting to think about:
* Have a top level test runner that looks at a subpackage (how?) to
see its deps.
* The top level test runner tests the deps.
* If the deps are there, it runs the tests of the subpackage in a
* Iterate though all IPython subpackages. Or we could make it interactive.
This approach would better isolate the testing of different package.
I think having things run in different processes is really important
due to all the nasty stuff we are seeing.
On Wed, Apr 15, 2009 at 2:47 PM, Laurent Dufréchou
> Just a stupid thought. How about a simple top level test script?
> It test if modules are present and if version are OK.
> Depending on the result, it propose a menu that run tests related to
> different parts.
> Ex: wx,twisted present, no qt.
> 0/core test
> 1/wx test
> 2/twisted related test
> Note: missing test:
> - qt test: missing qt-4.5 depedency
> Perhaps this is a dumb approach, but it has the advantage to allows us to
> better handle which test will be run.
> And dumb user like me will know what he is testing. And he/I will not
> complain because test fails stupidly :)
> Another advantage is that you can do more test before launching test to
> check is installed system is conform to what test needs. And thus explain ti
> the user possible cuase of a failure (bad nose version etc....)
> That's the easy part, sure you will say me that some part needs wx+twisted
> :) how do you do in this case...
>> -----Message d'origine-----
>> De : firstname.lastname@example.org [mailto:ipython-dev-
>> email@example.com] De la part de Brian Granger
>> Envoyé : mercredi 15 avril 2009 23:17
>> À : IPython Development list
>> Objet : [IPython-dev] Testing headaches
>> As we settle into the new workflow (code reviews, etc.) one of the
>> biggest things that keeps getting us is that our testing system seems
>> very easy to break in really wierd ways. This is different from not
>> having tests or having tests that simply fail. In our case, we are
>> seeing a number of things that actually break the test suite itself:
>> * Both Ville and Jorgen have seens really odd things in the last few
>> * I am seeing a nasty memory leak that is intermittent on OS X.
>> * Twisted and nose are somehow very unhappy with each other.
>> * Sometimes tests rely on dependencies (wx, twisted, etc.). Those
>> tests get run on systems that don't have the deps and they fail with
>> ImportError. I have tried to add code that tests for dependencies,
>> but these keep creeping in. The problem with this is that the person
>> who finds the problem is not the person who wrote the code or tests.
>> Part of the difficulty with all of these things is that debugging them
>> is HELL. Often times it is difficult to even begin to see where the
>> problem is coming from.
>> I am wondering what we can do to make our testing framework more
>> robust. We need an approach that can run tests in a more isolated
>> manner so we immediately know where such problems are coming from.
>> Also, we need to come up with a uniform and consistent way of handling
>> dependencies in tests.
>> IPython-dev mailing list
More information about the IPython-dev