You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The usage is really neat but I was hoping the following would succeed @test(expected=Exception.class) @testwith({"A B", "A+B", "A!B"})
public void junkNameFails(String junkName) { ...
It doesn't and there is no equivalent so I'm back to try-catch-or-fail()
Same could be said for the timeout option though I suspect it's less commonly used.
Without looking at the code or possibilities in JUnit, it would be preferable to hijack an existing @test annotation (as above) than to simply repeat its functions. That way @testwith stays pure to parameterisation.
i didn't plan to support this feature because there is a lot of arguing that it shouldn't be used.
see: http://alexruiz.developerblogs.com/?p=1530 and https://code.google.com/p/catch-exception/ however, there are some small problems with catch-exception library so i will reconsider this feature. but i don't think it will be added very soon
From [email protected] on July 15, 2013 23:21:41
1.0.0-beta1
The usage is really neat but I was hoping the following would succeed
@test(expected=Exception.class)
@testwith({"A B", "A+B", "A!B"})
public void junkNameFails(String junkName) { ...
It doesn't and there is no equivalent so I'm back to try-catch-or-fail()
Same could be said for the timeout option though I suspect it's less commonly used.
Without looking at the code or possibilities in JUnit, it would be preferable to hijack an existing @test annotation (as above) than to simply repeat its functions. That way @testwith stays pure to parameterisation.
Original issue: http://code.google.com/p/zohhak/issues/detail?id=2
The text was updated successfully, but these errors were encountered: