Re: Overview of ETS 3.0 tests

On Fri, Jul 18, 2008 at 11:29, Ilan Schnell <ischnell@...> wrote:
> Bryce, yes, I've had this problem with other tests as well, so I fixed the
> imports in such a way that nose finds them, e.g.:
> https://svn.enthought.com/enthought/changeset/20042
> It is strange that nose is not able to find simple local imports, even when
> you run it in the same directory.  On the other hand nose is trying to do
> so many other "clever" things that it was necessary to run it as a
> subprocess
> in the according test directory.  Let's hope future versions of nose fix
> these
> issues, but for now we have to deal with it.

I don't know about that. I reverted that change, and that test file
worked fine when running from any directory. Same with the
BlockCanvas/integrationtests/. I'm using nose 0.10.3 on OS X and
Ubuntu, at least.

One alternative to test_all.py is simply to explicitly specify the
test directories in the setup.cfg. For example, for Mayavi

  [nosetests]
  tests=tests/,enthought/tvtk/tests/

Note that the _port_ directories under BlockCanvas should be omitted.
They contain nonessential things that still refer to the geo package
or otherwise need to be updated. Most of the remaining
BlockCanvas/integrationtests/ failures stem from the fact that it
simply hasn't been ported to use nose, yet. It does custom collection
for unittest. Anyways, the numeric_context code it's testing is
obsolete, so it's not really important.

--

-- 
Robert Kern

"I have come to believe that the whole world is an enigma, a harmless
enigma that is made terrible by our own mad attempt to interpret it as
though it had an underlying truth."
 -- Umberto Eco