LSST is migrating to py.test as the test runner rather than unittest. Like nose, which we have been using in Twinkles and Monitor, py.test will work with tests written in the unittest framework as well. I think this is an attractive option, because of
continued support to tests written in the unittest or nose framework
New features (I believe) not present in nose, that enable writing tests which seem harder to do in nose, but with less boilerplate than unittest, which I often find excessive for simple tasks.
LSST is migrating to py.test as the test runner rather than
unittest
. Like nose, which we have been using in Twinkles and Monitor, py.test will work with tests written in theunittest
framework as well. I think this is an attractive option, because ofSo, I think we have two things to get done