Clik here to view.
Various releases
Recently I’ve been working on the Python unittest API in my spare time, with a long term goal of making it possible to safely and sensibly glue many different plugins together into the core. Two...
View ArticleClik here to view.
bzr selftest uses testtools
the emperor has new clothes bzr has just changed the base class for its test suite from ‘unittest.TestCase’ to ‘testtools.TestCase’. This change has cleaned up a bunch of test logic, deleted a...
View ArticleClik here to view.
Announcing testrepository
For a while now I’ve been using subunit as part of my regular development workflow. I would pipe test results to a file, use subunit to report on failures from that file, and be able to inspect all the...
View ArticleClik here to view.
Maintainable pyunit test suites
There’s a test code maintenance issue I’ve been grappling with, and watching others grapple with for a while now. I’ve blogged about some infrastructural things related to it before, but now I think...
View ArticleClik here to view.
Subunit and nose
Looks like someone has come up with a nose plugin for subunit – excellent! http://www.liucougar.net/blog/projects/nose-subunit In their post the author notes that subunit is not easy_installable at the...
View ArticleClik here to view.
testrepository iteration for python projects
Tesetrepository has a really nice workflow for fixing a set of failing tests: Tell it about the failing tests (e.g. by doing a full test run, or running a single known failing test) Run just the known...
View ArticleClik here to view.
Less SPOFs: pyjunitxml, testscenarios
I’ve made the Testtools committers team own both the project and the trunk branch for both pyjunitxml and testscenarios. This removes me as a SPOF if anything needs doing in those projects – any...
View ArticleClik here to view.
First experience implementing StreamResult
My last two blog posts were largely about the needs of subunit, but a key result of any protocol is how easy working with it in a high level language is. In the weekend and evenings I’ve done an...
View ArticleClik here to view.
Simpler is better – a single event type for StreamResult
StreamResult, covered in my last few blog posts, has panned out pretty well. Until that is, that I sat down to do a serialised version of it. It became fairly clear that the wire protocol can be very...
View ArticleClik here to view.
subunit version 2 progress
Subunit V2 is coming along very well. Current status: I have a complete implementation of the StreamResult API up as a patch for testtools. Thats 2K LOC including comeprehensive tests. Similarly, I...
View ArticleClik here to view.
Subunit and subtests
Python 3 recently introduced a nice feature – subtests. When I was putting subunit version 2 together I tried to cater for this via a heuristic approach – permitting the already known requirement that...
View ArticleClik here to view.
Revisiting the Fixture API – handling leaky resources
Fixtures are one of the innovations I’m most happy with. A Fixture is an enhanced context manager. The enhancements are: There’s an API for gathering debugging information from the fixture (rather than...
View ArticleClik here to view.
Testrepository roadmap 2015/16
Testrepository has been moderately successful – its very good at some of the things it aspired to (e.g. debugging sporadic test failures in parallel environments), but other angles have not really been...
View Article