* Accept integers for threshold
In documentation is written that threshold should be integer.
But it fails with integer to generate XML.
Only case when it pass is for 0, because XML formatter consider it as
empty body and do not format it.
* Fix documentation for missing threshold field, plus test.
In documentation it says that missing threshold is set to 0, but apparently
it is set to Null (empty field), and it has different behaviour than for 0
value.
Change-Id: I326cbadd955c4c28f315fa72293d9a54a116b140
This is valid for each defined xUnit type publisher on the job. Default
is false.
Change-Id: Idff3c8ba6a4e4291ec483b2eb4a999dcbeea7291
Signed-off-by: Lucas Dutra Nunes <ldnunes@ossystems.com.br>
From the plugin advanced configuration:
"Give the report time margin value (default to 3000) in ms, before
to fail if not new (unless the option 'Fail the build if test
results were not updated this run' is checked)."
The configuration defaults to 3000 if no value is passed.
Change-Id: I372d9cc100ecd824516bac864daac0af41e367f5
Signed-off-by: Lucas Dutra Nunes <ldnunes@ossystems.com.br>
Python 3 enables hash randomization by default, additionally tox 1.7
turns on the same randomization for earlier versions of python by
default. Need to ensure that order of iteration over the yaml data and
resulting XML has deterministic order for testing.
Adapts https://gist.github.com/enaeseth/844388 which ensures data read
by yaml will have its order retained in a predictable manner across
multiple python versions.
Additionally it seems more sensible to ensure that the order of
generated XML snippets corresponding to the input yaml files are
consistently in the same order as the entries in the source files.
Closes-Bug: #1333349
Change-Id: I6bf6d298a2609cc6ddbbc6b02b7f1a04413a5c89
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>
Dong Ma