On Wed, Feb 18, 2009 at 2:43 PM, James Evans <jreva...@earthlink.net> wrote:
> All,
>
> I have just submitted a first-cut at a unit-test harness. The unit-tests
> do require the use of the 'nose' python module.
> Everything has been placed in the 'test' directory off of the root trunk
> branch. There is a README file with lots of information on
> how to use it. This is in addition to a few test cases already bundled in
> (they make great examples)! The idea is that whenever
> somebody adds a new feature or makes a change they update/add the
> appropriate test case and re-run the harness to make sure nothing
> is broken.
>
> There is most definitely room for improvement with this, but it gives a
> starting point from which discussions and modifications can
> take place.
>
> Any questions or comments?
What is the naming convention for the test harness? I see
filenames_with_underscores, camelCase, CapWords, and it looks like all the
methods in MplTestCase are camelCase, whereas mpl uses only
names_with_underscores. Although it would probably be a lot of busy work to
convert at this point, I think it would be a good idea to follow the
existing mpl naming conventions.
Darren
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
