llvm-project/llvm/utils/lit/tests/xunit-output.py

# Check xunit output
# RUN: %{lit} --xunit-xml-output %t.xunit.xml %{inputs}/xunit-output || true
# RUN: FileCheck < %t.xunit.xml %s

# CHECK: <?xml version="1.0" encoding="UTF-8" ?>
# CHECK: <testsuites>
# CHECK: <testsuite name='test-data' tests='1' failures='1'>
# CHECK: <testcase classname='test-data.test-data' name='bad&amp;name.ini' time='{{[0-1]}}.{{[0-9]+}}'>
# CHECK-NEXT: 	<failure >
# CHECK-NEXT:&amp; &lt; &gt; "
# CHECK-NEXT:</failure>
# CHECK: </testsuite>
# CHECK: </testsuites>
Add a test-case for lit xunit output llvm-svn: 223307 2014-12-03 23:01:35 +00:00			`# Check xunit output`
[LIT] Move xunit tests tests into their own location, and and add failures Failures will increase coverage. llvm-svn: 332056 2018-05-10 22:51:28 +00:00			`# RUN: %{lit} --xunit-xml-output %t.xunit.xml %{inputs}/xunit-output \|\| true`
Add a test-case for lit xunit output llvm-svn: 223307 2014-12-03 23:01:35 +00:00			`# RUN: FileCheck < %t.xunit.xml %s`

			`# CHECK: <?xml version="1.0" encoding="UTF-8" ?>`
			`# CHECK: <testsuites>`
[LIT] Move xunit tests tests into their own location, and and add failures Failures will increase coverage. llvm-svn: 332056 2018-05-10 22:51:28 +00:00			`# CHECK: <testsuite name='test-data' tests='1' failures='1'>`
			`# CHECK: <testcase classname='test-data.test-data' name='bad&name.ini' time='{{[0-1]}}.{{[0-9]+}}'>`
			`# CHECK-NEXT: <failure >`
			`# CHECK-NEXT:& < > "`
			`# CHECK-NEXT:</failure>`
Add a test-case for lit xunit output llvm-svn: 223307 2014-12-03 23:01:35 +00:00			`# CHECK: </testsuite>`
[LIT] Fix failing LIT tests Summary: I spend some time trying to get the LIT test suite passing. Here are the changes that I needed to make on my machine. I made the following changes for the following reasons. 1. google-test.py: The Google test format now checks for "[ PASSED ] 1 test." to check if a test passes. 2. discovery.py: The output appears in a different order on my machine than it did in the test. 3. unittest-adaptor.py: The output appears in a different order on my machine than it did in the test. 4. The classname is now formed differently in `getJUnitXML(...)`. I'm not sure what is causing the output order to differ in discovery.py and unittest-adaptor.py. Does anybody have any thoughts? Reviewers: ddunbar, danalbert, jroelofs Reviewed By: jroelofs Subscribers: llvm-commits Differential Revision: http://reviews.llvm.org/D9864 llvm-svn: 239663 2015-06-13 06:55:44 +00:00			`# CHECK: </testsuites>`