On Tue, Sep 8, 2009 at 10:14 AM, Andrew Straw<straw...@astraw.com> 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`. 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 ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
