+1.
On 18 March 2014 16:21, Anders Logg <[email protected]> wrote: > I support switching to whatever is new and better, but don't have any > experience with either. > > -- > Anders > > > On Tue, Mar 18, 2014 at 11:31:21AM +0100, Johan Hake wrote: > > I have some experience of both frameworks and think they are much > superior to > > what we have and I therefore support a future transition. pytest also > let you > > annotate your tests facilitating running only part of your test suit > which > > could be handy. Porting the python tests to pytest, should be > straightforward, > > but it is of course a tedious job. > > > > Johan > > > > > > On Tue, Mar 18, 2014 at 10:38 AM, Garth N. Wells <[email protected]> > wrote: > > > > I've been discussing with Martin the merits of moving to modern unit > > testing frameworks. We both have some experience of googletest > (https:// > > code.google.com/p/googletest/) and Martin has experience with > PyTest (http: > > //pytest.org/). Some motivations for considering a switch are (a) > simpler > > code for C++ and Python tests (particularly for C++); and (b) scope > to > > speed-up by running tests in parallel. Both googletest and PyTest > are on > > the buildbots and are used by uflacs. > > > > I don't think switching is pressing, but it would be helpful to hear > if > > there are any strong views either way. > > > > Garth > > _______________________________________________ > > fenics mailing list > > [email protected] > > http://fenicsproject.org/mailman/listinfo/fenics > > > > > > > _______________________________________________ > > fenics mailing list > > [email protected] > > http://fenicsproject.org/mailman/listinfo/fenics > > _______________________________________________ > fenics mailing list > [email protected] > http://fenicsproject.org/mailman/listinfo/fenics >
_______________________________________________ fenics mailing list [email protected] http://fenicsproject.org/mailman/listinfo/fenics
