[openstack-dev] per process output from testr parallel?
sean at dague.net
Thu Jan 30 01:34:59 UTC 2014
On 01/29/2014 07:27 PM, Robert Collins wrote:
> On 30 January 2014 10:29, Sean Dague <sean at dague.net> wrote:
>>> would (worker-N) be sufficient? Or do you want *'s/x's specifically?
>> So if we had worker-N we could play with a filter above that layer to do
>> UI formatting.
>> Realistically I had a stream with enough metadata, and preferably a
>> solid parsing lib for that stream (so I don't screw that part up), then
>> we could handle the UI in a filter.
>> Honestly, UX here is going to require the ability to iterate and
>> experiment. In much the same way that we've got a completely
>> disconnected visualization system for zuul from zuul itself, and only
>> rarely do we need to touch zuul proper to improve status.openstack.org.
> Right - thats what subunit *is* - its decoupling :).
>>>> Question #2: where would this be injectable in the stream of testtools /
>>>> subunit / testr / unittest?
>>> Long term I defintely want a richer UI in testr, but right now the
>>> most appropriate thing to do is to prototype the UI you need locally.
>> Sounds great. Again if we had some of the piece parts, I could do the
>> rest of the UI locally, just diving down through the layers made me
>> realize I really needed to figure out where to hook into, as it wasn't
>> entirely clear (at least to me).
> both demonstrates the glue (subunit is the wire protocol, testtools
> has the model level functions) and approximates what you've asked for
> as a first iteration.
Awesome. Thank you!
Samsung Research America
sean at dague.net / sean.dague at samsung.com
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 547 bytes
Desc: OpenPGP digital signature
More information about the OpenStack-dev