test_image

Development matplotlib-devel
#1

I must be missing something obvious, but I tried to add a new module
to lib/matplotlib/tests called test_image, which has a single method
so far, test_image_interps. I added the standard decorator and
baseline image, and I can see it being installed in the stdio on the
sage buildbot

http://mpl-buildbot.code.astraw.com/builders/Mac%20OS%20X%2C%20Python%202.6%2C%20x86/builds/109/steps/test/logs/stdio

but I do not see an additional test being run (I still get the usual
26 tests). Is there another step to getting this to be picked up by
the test harness?

JDH

#2

John Hunter wrote:

I must be missing something obvious, but I tried to add a new module
to lib/matplotlib/tests called test_image, which has a single method
so far, test_image_interps. I added the standard decorator and
baseline image, and I can see it being installed in the stdio on the
sage buildbot

http://mpl-buildbot.code.astraw.com/builders/Mac%20OS%20X%2C%20Python%202.6%2C%20x86/builds/109/steps/test/logs/stdio

but I do not see an additional test being run (I still get the usual
26 tests). Is there another step to getting this to be picked up by
the test harness?
  

As described in the "Creating a new module in matplotlib.tests" of the developer coding guide (see line 780 of http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/matplotlib/doc/devel/coding_guide.rst?revision=7664&view=markup ):

Let's say you've added a new module named ``matplotlib.tests.test_whizbang_features``. To add this module to the list of default tests, append its name to ``default_test_modules`` in :file:`lib/matplotlib/__init__.py`.

#3

Thanks, missed that. Since I added test_dates which automagically
worked, I didn't know I needed to add the module anywhere, but I'm
guessing you added that for me. I added test_image to the default, so
it should fire off shortly.

JDH

···

On Tue, Sep 8, 2009 at 10:14 AM, Andrew Straw<strawman@...36...> wrote:

but I do not see an additional test being run (I still get the usual
26 tests). Is there another step to getting this to be picked up by
the test harness?

As described in the "Creating a new module in matplotlib.tests" of the
developer coding guide (see line 780 of
http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/matplotlib/doc/devel/coding_guide.rst?revision=7664&view=markup
):

Let's say you've added a new module named
``matplotlib.tests.test_whizbang_features``. To add this module to the list
of default tests, append its name to ``default_test_modules`` in
:file:`lib/matplotlib/__init__.py`.