SUnit bug fix

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

SUnit bug fix

Joseph Pelrine-4
Yes, just when you thought it was safe to go back in the water...Steve
Waring found a bug in SUnit. In the current implementation, if you do
#debugAsFailure on a TestCase with resources (as Jeff's browser does),
the debugger thread gets forked off, and the main thread goes on its'
merry way, resetting the resource. Thanks, Steve, we missed that one!

Anyway, correcting that gave me a chance to clean up another sore spot.
Now, when a test run fails because a resource can't be initialized, the
error thrown informs you about which resource was guilty.

The attached zip file includes the new version of the SUnit package, as
well as a slightly changed version of my SUnit extensions, and a package
demonstrating how to get ahold of the test result during the test run by
using a resource. I use this when running longer, automated tests,
analyzing the test result when the test run is over, .i.e. when the
resource is reset, and sending an email (or other notification) if any
failures occured.

Remember, folks, you saw it here first...

Cheers
--
Joseph Pelrine [ | ]
MetaProg GmbH
Email: [hidden email]
Web:   http://www.metaprog.com

"If you don't live on the edge, you're taking up too much space" -
Doug Robinson


SUnitUpdate.zip (9K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: SUnit bug fix

Joseph Pelrine-4
Having received a number of mails informing me that not all newsservers support
binary attachments to postings, I uploaded a the SUnit update zip file to
www.metaprog.com. You can find it on the downloads page.

Cheers
Joseph

Joseph Pelrine wrote:

> Yes, just when you thought it was safe to go back in the water...Steve
> Waring found a bug in SUnit. In the current implementation, if you do
> #debugAsFailure on a TestCase with resources (as Jeff's browser does),
> the debugger thread gets forked off, and the main thread goes on its'
> merry way, resetting the resource. Thanks, Steve, we missed that one!
>
> Anyway, correcting that gave me a chance to clean up another sore spot.
> Now, when a test run fails because a resource can't be initialized, the
> error thrown informs you about which resource was guilty.
>
> The attached zip file includes the new version of the SUnit package, as
> well as a slightly changed version of my SUnit extensions, and a package
> demonstrating how to get ahold of the test result during the test run by
> using a resource. I use this when running longer, automated tests,
> analyzing the test result when the test run is over, .i.e. when the
> resource is reset, and sending an email (or other notification) if any
> failures occured.
>
> Remember, folks, you saw it here first...
>
> Cheers
> --
> Joseph Pelrine [ | ]
> MetaProg GmbH
> Email: [hidden email]
> Web:   http://www.metaprog.com
>
> "If you don't live on the edge, you're taking up too much space" -
> Doug Robinson
>
>   ------------------------------------------------------------------------
>                       Name: SUnitUpdate.zip
>    SUnitUpdate.zip    Type: Zip Compressed Data (application/x-zip-compressed)
>                   Encoding: base64

--
Joseph Pelrine [ | ]
MetaProg GmbH
Email: [hidden email]
Web:   http://www.metaprog.com

"If you don't live on the edge, you're taking up too much space" -
Doug Robinson