diff options
| author | Dylan Baker <dylan@pnwbakers.com> | 2016-05-05 15:45:56 -0700 |
|---|---|---|
| committer | Dylan Baker <dylan@pnwbakers.com> | 2016-05-06 12:13:49 -0700 |
| commit | 6406b9fce11d1a0508dbb186d7210ecb8d911d99 (patch) | |
| tree | b32436598fe9fddbb0f999bc34ee0ef33a6f22c3 | |
| parent | 5ddb65a0dd5e05769d9d23adf97289208e5846cc (diff) | |
framework/backends/junit: Fix invalid JUnit output
In commit b0d05323e code was added to produce clearer error messages for
tests who's status changed from crash to fail and vice versa. There is a
not so subtle bug in that patch, it adds a "crash" element, but that
element should be an "error" element.
This patch fixes that bug.
cc: Kenneth Graunke <kenneth@whitecape.org>
Reviewed-by: Mark Janes <mark.a.janes@intel.com>
Signed-off-by: Dylan Baker <dylanx.c.baker@intel.com
| -rw-r--r-- | framework/backends/junit.py | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/framework/backends/junit.py b/framework/backends/junit.py index 8263d98bf..4b3d87e76 100644 --- a/framework/backends/junit.py +++ b/framework/backends/junit.py @@ -168,9 +168,9 @@ class JUnitBackend(FileBackend): elif expected_result == 'failure': err.text += \ "\n\nERROR: Test should have been failure but was crash" - res = etree.SubElement(element, 'crash', + res = etree.SubElement(element, 'error', message='expected failure, but got ' - 'crash') + 'error') else: res = etree.SubElement(element, 'error') |