| 21416a1d09aad1e25401e54578c3343bb0f0c25f |
|
23-Feb-2013 |
Enrico Granata <egranata@apple.com> |
<rdar://problem/12362092>
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)
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@175942 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/unittest2/runner.py
|
| a182573e1a56ac5f68c0f0a38e6da906dc93b238 |
|
09-Feb-2013 |
Enrico Granata <egranata@apple.com> |
The new progress bar mode was losing us information compared to the old dots 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!
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@174784 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/unittest2/runner.py
|
| bc0c5a6c53350736969f9e0c0a7a9d41742f54c9 |
|
09-Feb-2013 |
Enrico Granata <egranata@apple.com> |
<rdar://problem/13176279>
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)
git-svn-id: https://llvm.org/svn/llvm-project/lldb/trunk@174777 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/unittest2/runner.py
|
| 75e28f942c1b9f9c6d5a0d5f2efd037cbbc9fc74 |
|
06-Aug-2010 |
Johnny Chen <johnny.chen@apple.com> |
o Added unittest2 which has added the new features in unittest for Python 2.7
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.
git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@110397 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/unittest2/runner.py
|