Yes this is what I mean, but only because it makes it more consistent with
our other tests.  Nose, in its awesomeness, will pick the unittests up and
run them.  How useful it would be to redo these, I leave to your judgement.


On Sun, Sep 1, 2013 at 12:53 AM, Elliott Biondo <notifications@github.com>wrote:

> In pyne/tests/test_mesh.py:
>
> > @@ -0,0 +1,273 @@
> > +from itaps import iBase
> > +from itaps import iMesh
> > +from itaps import iMeshExtensions
> > +
> > +import numpy
> > +import unittest
> > +import os.path
> > +import itertools
> > +from operator import itemgetter
> > +
> > +from pyne.mesh import *
> > +
> > +class MeshTest(unittest.TestCase):
>
> Yes these are from Steve.
>
> By "use nose and functions" do you mean that every test should just be its
> own freestanding function with no classes? In other words, just eliminate
> the unittest dependency?
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/pyne/pyne/pull/150/files#r6101117>
> .
>