Antoine Musso b829874916 Tests for publishers ... I am trying to build up a very basic testing framework so we can tests our publishers. The idea is to provide a YAML input file and expected XML output, run the parser on the YAML file and compares its output with the fixture XML. That test suite should speed up development of new publishers. TestCaseModulePublisher is declared inside a function so that unittest discovery does not consider it a usable test directly. load_test is responsible for instantiating the test suite. Change-Id: If3260113eb1337ac47c3883b11c600e5a595dae3 [fabre.arnaud@gmail.com: fixed some runtime errors] Signed-off-by: Arnaud Fabre <fabre.arnaud@gmail.com>		2013-07-19 14:31:11 +02:00
..
jenkins-jobs.py	Add jenkins-jobs command line tool.	2013-04-08 14:52:11 +00:00
pip-requires	Add test to determine whether XML output has changed.	2012-09-01 03:52:21 +00:00
run-compare-xml-samples.sh	Do not output XML if job name not specified ('pipeline', 'trigger-builds')	2012-10-30 16:32:39 +00:00
run-compare-xml.sh	Adding ability to specify the JDK to use. This change moves the top level config from builder.py into a separate file called general.py. This change also moves the assigned node work as well as the log rotator work into the general.py file. This change also adds the ability to specify the JDK for the build to use.	2012-12-19 03:18:32 +00:00
test-requires	Tests for publishers	2013-07-19 14:31:11 +02:00
test.sh	Stop referring to openstack/openstack-ci-puppet.	2013-03-01 18:32:53 +00:00