History log of /external/lldb/test/unittest2/result.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
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/result.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/result.py