tag:blogger.com,1999:blog-8055871.post7864899432052006418..comments2024-03-20T02:54:54.722-04:00Comments on Blatherberg: TestNG and Expected Exceptionskonberghttp://www.blogger.com/profile/04616226121996611123noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-8055871.post-69797513345817275942018-02-19T01:46:07.408-05:002018-02-19T01:46:07.408-05:00This comment has been removed by a blog administrator.Jackie Co Kadhttps://www.blogger.com/profile/04015282241330616565noreply@blogger.comtag:blogger.com,1999:blog-8055871.post-51538544172975949332011-11-05T05:11:33.254-04:002011-11-05T05:11:33.254-04:00Rod, that's a clever idea.Rod, that's a clever idea.konberghttps://www.blogger.com/profile/04616226121996611123noreply@blogger.comtag:blogger.com,1999:blog-8055871.post-23699226404882068192011-10-28T05:51:52.851-04:002011-10-28T05:51:52.851-04:00There is an alternative to the statement-level ann...There is an alternative to the statement-level annotations we probably never get.<br /><br />You can use proxies to test for expected exceptions. Have a look at this little helper:<br />http://code.google.com/p/catch-exception/<br /><br />Rodrwoohttps://www.blogger.com/profile/16717118518599452043noreply@blogger.comtag:blogger.com,1999:blog-8055871.post-26099912243393232022007-11-07T10:54:00.000-05:002007-11-07T10:54:00.000-05:00Rob,A better way to implement your setUpIsComplete...Rob,<BR/><BR/>A better way to implement your setUpIsComplete() approach is to make it a method on which the real test depends.Cedrichttps://www.blogger.com/profile/13274064962794267826noreply@blogger.com