On Mon, Mar 9, 2015 at 1:12 PM, Tollef Fog Heen <[email protected]> wrote:
> > I'd argue that scheduling and collecting the results are different > again. Having varnishtest able to output TAP or similar and then > having something that consumes that and feeds it into a database (and > then a third tool to display/distribute this) sounds like a better > design. (varnishtest already knows a bit about scheduling with -j and > all that.) > I actually didn't know about varnishtest -j. So, yeah. I agree, if we already to scheduling then this doesn't really add that much. There is still the collection issue, but this is a more a system specific issue to _our_ own testrig. And we might want run this tool there locally in order to gather data on how the tests are performing. -- *Per Buer* CTO | Varnish Software AS Cell: +47 95839117 We Make Websites Fly! www.varnish-software.com [image: Register now] <http://info.varnish-software.com/varnish-summits-autumn-2014-registration>
_______________________________________________ varnish-dev mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev
