summaryrefslogtreecommitdiffstats
path: root/lldb/test/unittest2/runner.py
Commit message (Collapse)AuthorAgeFilesLines
* Move third party libraries to lldb/third_partyZachary Turner2015-10-221-203/+0
| | | | llvm-svn: 251046
* Refactor test runner to print sub-test-case pass/fail rate.Zachary Turner2015-05-281-19/+16
| | | | llvm-svn: 238467
* Added a simple legend to the unit test 'dots' output, to aid understandability.Richard Mitton2013-09-251-0/+5
| | | | llvm-svn: 191398
* <rdar://problem/12362092>Enrico Granata2013-02-231-4/+4
| | | | | | | | The decorators @expectedFailure (plain and special-case like i386, clang, ...) are modified to optionally take a bugnumber argument If such an argument is specified, the failure report (or unexpected success report) will include the information passed in as part of the message This is mostly useful for associating failures to issue IDs in issue management systems (e.g. the LLVM bugzilla) llvm-svn: 175942
* The new progress bar mode was losing us information compared to the old dots ↵Enrico Granata2013-02-091-44/+16
| | | | | | | | | | mode in that we would have no way of knowing about test failures (short of peeking into the test result directory.. and you're not supposed to peek!) Added a new line of information that reports the count of tests that pass, fail or have other things happen to them. Again no flag to have the dots back. If you care, let us know! llvm-svn: 174784
* <rdar://problem/13176279>Enrico Granata2013-02-081-0/+23
| | | | | | | | The LLDB test suite now shows a progress bar instead of dots when not in verbose mode If you crave the dots, make your Terminal window smaller than 10 columns :-) (or ask for a flag to have the dots come back on demand) llvm-svn: 174777
* o Added unittest2 which has added the new features in unittest for Python 2.7Johnny Chen2010-08-051-0/+206
backported to Python 2.3+. Some of the features desired include better verbose reporting in unittest2.TextTestRunner and decorator support for skipping tests and expected failures. http://pypi.python.org/pypi/unittest2 o Modified the existing .py tests to use unittest2 and decorated TestSTL.test_step_into_stl(), which is known to always fail currently, with @unittest2.expectedFailure. llvm-svn: 110397
OpenPOWER on IntegriCloud