mirrors/llvm-project
0
0
Fork 0
mirror of https://github.com/llvm/llvm-project.git synced 2025-05-17 23:36:04 +00:00
Code Issues Projects Releases Wiki Activity
llvm-project/llvm/utils/lit/tests/xunit-output.py

13 lines
504 B
Python
Raw Normal View History

Add a test-case for lit xunit output llvm-svn: 223307
2014-12-03 23:01:35 +00:00
# Check xunit output
Use not to catch unexpected pass as well as remove old test results As per review feedback, make sure we rm temp files, and make the return code checking for lit more specific. llvm-svn: 332423
2018-05-16 00:33:29 +00:00
# RUN: rm -rf %t.xunit.xml
# RUN: not %{lit} --xunit-xml-output %t.xunit.xml %{inputs}/xunit-output
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>
Support Unsupported Tests in xunit output We were reporting "Unsupported" tests in xunit as passes, however since they are not run, it make more sense to mark them as skipped. The Junit xml standard has support for that, so lets use it. llvm-svn: 332065
2018-05-11 00:25:43 +00:00
# CHECK: <testsuite name='test-data' tests='1' failures='1' skipped='0'>
[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: <testcase classname='test-data.test-data' name='bad&amp;name.ini' time='{{[0-1]}}.{{[0-9]+}}'>
[LIT] replace output escapes wit a cdata block CDATA blocks don't need to have XML stuff escaped. Makes sense to wrap output in them instead of escaping. llvm-svn: 332116
2018-05-11 18:38:02 +00:00
# CHECK-NEXT: <failure ><![CDATA[& < > "]]></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>
Reference in New Issue Copy Permalink