[Libvirt-cim] [PATCH] [TEST] #2 Add stack trace on error to make test case development easier

[Dan Smith]

DK> How or when can we make use of this ?

Since the entire test is run in a try..except block, errors and typos
while writing tests get squashed down to nothing more than an error
message like "IndexError: list index out of range", with no indication
of where that is happening.  Putting a stack trace in the error output
gives you that information.

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms at us.ibm.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 188 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/libvirt-cim/attachments/20080730/df6bf6f0/attachment.sig>