On tests

Dridi Boukelmoune dridi.boukelmoune at zenika.com
Mon Mar 9 17:48:22 CET 2015


I have this little side project called varnishtest-exec [1] which is
currently a java wrapper that can be integrated in 2 java build
systems (Ant and Maven if you're curious).

Things I'd like to do, and that people actually want [2] is CI
integration, starting with Jenkins (also written in Java).

My current goal is to be able to collect data from reports and display
test trends (success vs failure vs skipped). I'm open to any
suggestions for features, and I could hopefully start working on this
next week.


[1] https://github.com/Zenika/varnishtest-exec
[2] https://github.com/Zenika/varnishtest-exec/issues/2

On Mon, Mar 9, 2015 at 1:20 PM, Per Buer <perbu at varnish-software.com> wrote:
> On Mon, Mar 9, 2015 at 1:12 PM, Tollef Fog Heen <tfheen at fastly.com> 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
> _______________________________________________
> varnish-dev mailing list
> varnish-dev at varnish-cache.org
> https://www.varnish-cache.org/lists/mailman/listinfo/varnish-dev

More information about the varnish-dev mailing list