nose2 vs py.test with isolated processes

Viewed 2974

We have been using nosetest for running and collecting our unittests (which are all written as python unittests which we like). Things we like about nose:

  • uses standard python unit tests (we like the structure this imposes).
  • supports reporting coverage and test output in xml (for jenkins).

What we are missing is a good way to run tests in isolated processes while maintaining good error repoorting (we are testing C++ libraries through python so segfaults should not be catastrophic). nosepipe seems to be no longer maintained and we have some problems with it.

We are trying to figure out whether we should - fix/use nosepipe - switch to nose2 and write nosepipe2. - use pytest or some other testing framework.

We would prefer to use an approach with a good community. It seems our problem (C++ plugins requiring good isolation) might be a common problem but googling I have not found solutions that are maintained. Advice from more experienced heads appreciated.

1 Answers
Related