sikuli-driver team mailing list archive

Thread
Date

Re: [Question #212171]: tearDown not called when calling exit() in a unit test

To: sikuli-driver@xxxxxxxxxxxxxxxxxxx
From: Georgi Angelchov <question212171@xxxxxxxxxxxxxxxxxxxxx>
Date: Wed, 24 Oct 2012 15:01:24 -0000
Reply-to: question212171@xxxxxxxxxxxxxxxxxxxxx
Sender: bounces@xxxxxxxxxxxxx

Question #212171 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/212171

    Status: Answered => Solved

Georgi Angelchov confirmed that the question is solved:
Thanks for the answer.

Initially my test had asserts. I changed this to "print message and
exit" because the AssertionError I was getting was not desrciptive in
any way. I found the "print and exit" approach while searching how to
make my test fail gracefully with a meaningfull message.

The "Print message and Assert" approach works as expected though, so
thanks for pointing that out.

Thaks for the link to faq 1804 as well :)

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.