Re: Overview of ETS 3.0 tests

Hi Prabhu,
The reason why test_all.py does not pick up the integration tests
is because nose does not pick them up.  test_all.py just runs nose
in integrationtests as a subprocess.  If I go to integrationtests and
run nose manually nothing happens either (at least with nose 0.10.3).
Different version of nose behave differently, and its causing a lot of
trouble, but essentially test_all.py can do whatever it wants.  For
example to run the command line options you can say something like
  retval = subprocess.call(['python', 'test_image_plane_widget.py', '-h'])
  ...
  self.assertEqual(retval, 0)
test_all.py should however run all the test suites, i.e. if one fails
the others should still run and at the end it prints out a summary before
checking if all went well.  Note also that test_all needs to be a unittest,
such that it works when you say: python setup.py test

I assume that:
./enthought/mayavi/tests   are more "internal" tests
./integrationtests         are graphical tests

If this is true, I will move test_csv_sniff.py and the corresponding folder
with test files to ./enthought/mayavi/tests

I hope you had a god trip back to India.

- Ilan

Prabhu Ramachandran wrote:
> Ilan Schnell wrote:
>   
>> Hi,
>> I've complied an overview of the different projects and the failure
>> rates:
>> http://www.enthought.com/~ischnell/ets.txt
>>
>> The first number is always the number of tests run in that folder.
>> I would say that things are not so bad:
>> - BlockCanvas has the most failures, many things are out of data
>> - Traits needs some more work.
>> - Mayavi basically passes the tests, but they are not really meant
>>   to be run by nosetests
>>     
>
> Thanks for this.  I've reorganized the mayavi tests quite a bit and 
> test_all.py no longer picks up the mayavi integration tests.  I have 
> however fixed various test related issues so more of them ought to pass.
>
> The mayavi tests do not play nicely with nose.  I think this can be 
> fixed and have something that works for one of the tests in my working copy.
>
> There is one major issue I do have though.  It is possible to run the 
> tests with different command line options
>
> $ python test_image_plane_widget.py -h
> Usage: test_image_plane_widget.py [options]
>
> Options:
>    -h, --help        show this help message and exit
>    -v, --verbose     Print verbose output
>    -i, --interact    Allow interaction after test (default: False)
>    -s, --standalone  Run test using standalone mode without envisage 
> (default:
>                      False)
>    -o, --offscreen   Always use offscreen rendering when generating images
>                      (default: False)
>
>
> Each of these is useful.  To get these working without conflicting with 
> the nose options is a pain.  One option is to create a config file for 
> the tests.  I don't like this.  I am not sure what the best solution 
> would be?  Thoughts?
>
> Once I have a solution to this I should be able to get nosetests working 
> with all the mayavi tests.
>
> cheers,
> prabhu
>
> _______________________________________________
> Enthought-dev mailing list
> Enthought-dev@...
> https://mail.enthought.com/mailman/listinfo/enthought-dev
>
>
>