← Back to team overview

dolfin team mailing list archive

Re: Dolfin test organization

 

On Mon, Aug 08, 2011 at 06:00:29PM -0400, Garth N. Wells wrote:
>
>
> On 08/08/11 14:11, Anders Logg wrote:
> > On Mon, Aug 08, 2011 at 07:26:24PM +0200, Martin Sandve Alnæs wrote:
> >> Hi,
> >> for example in
> >>   <dolfin>/test/unit/function/python/
> >> there is two files
> >>   function.py
> >>   test.py
> >> where the first one only contains a class Interpolate,
> >> while the second contains the same class with fewer
> >> functions plus a bunch of other classes.
> >>
> >> The same pattern of "foo.py" + "test.py" occurs other places as
> >> well. At a glance it seems to me there is some duplication.
> >>
> >> Is there some idea behind this structure or is it a
> >> remnant of some renaming/cleanup/whatever?
> >
> > It's a remnant and it would be good to decide on a structure to
> > use and stick to that.
> >
>
> The aim is to have a foo.py for each foo.h file (when appropriate). As
> mentioned, test.py is a remnant, although most tests are still in the
> test.py files.

Updated and targeted to 1.1:

https://blueprints.launchpad.net/dolfin/+spec/unit-test

--
Anders


References