← Back to team overview

openstack-qa-team team mailing list archive

PyVows proof of concept

 

In reply to: https://lists.launchpad.net/openstack-qa-team/msg00236.html, which didn't came to my mailbox for some reason (attachment?)

I tried pyVows myself. I kinda liked the concept, but I didn't like the way it is reporting to JUnit format XML when using "generative testing": http://heynemann.github.com/pyvows/#-using-generative-testing

In Jenkins, it looked like:

Test Result : Add
-----------------
should_be_numeric 	0 ms	Passed
should_be_numeric 	0 ms	Passed
should_be_numeric 	0 ms	Passed
should_be_numeric 	0 ms	Passed
should_be_numeric 	0 ms	Passed
should_be_numeric 	0 ms	Passed

The parameters to the testing method are important when using generative testing, so I think they should be included in the name of the test. But some funny characters like
()%* I don't remember which
are causing problems in Jenkins. I was investigating some problems with them months ago with some other testing framework. I don't know how to address this problem. It may be worthy to consider making some Robot framework outputs plugin if generative testing is needed, or use Robot Framework

https://wiki.jenkins-ci.org/display/JENKINS/Robot+Framework+Plugin

J.H.


Follow ups