Posts Tagged ‘testrepository’
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 have an implementation of a StreamResult parser and emitter for subunit. Thats 1K new LOC including comprehensive tests, and another 500 lines of […]
Filed under: Uncategorized | Leave a Comment
Tags: Python, Subunit, testing, testrepository, testsupport, testtools, unittest
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 implementation of a new set of classes – StreamResult and friends – that provides: Adaption to […]
Filed under: Uncategorized | Leave a Comment
Tags: performance, Python, Subunit, testing, testrepository, testsupport, testtools, unittest
More subunit needs
Of course, as happens sadly often, the scope creeps.. Additional pain points Zope’s test runner runs things that are not tests, but which users want to know about – ‘layers’. At the moment these are reported as individual tests, but this is problematic in a couple of ways. Firstly, the same ‘test’ runs on multiple […]
Filed under: Uncategorized | 1 Comment
Tags: coverage, junit, Python, Subunit, TAP, testing, testrepository, unittest
Subunit is seven and a half years old now – Conrad Parker and I first sketched it up at a CodeCon – camping and coding, a brilliant combination – in mid 2005. revno: 1 committer: Robert Collins <robertc@robertcollins.net> timestamp: Sat 2005-08-27 15:01:20 +1000 message: design up a protocol with kfish It has proved remarkably resilient […]
Filed under: Uncategorized | 9 Comments
Tags: concurrency, debugging, junit, performance, Python, Subunit, testing, testrepository
I recently added a formal interface to testrepository to enable cross-machine scaling of test runs. As testrepository is still a static scheduler, this isn’t perfect, but its quite a minimal interface, which makes it easy to implement. I will likely evolve it in reaction to feedback and experience. In the long term I’d love to […]
Filed under: Uncategorized | Leave a Comment
Tags: cloud, lxc, openstack, performance, Python, Subunit, testing, testrepository, testsupport, unittest
