[jira] Resolved: (WICKET-226) WicketTester version which does not depend on junit

["Janne Hietamäki (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Janne Hietamäki resolved WICKET-226.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.3

> WicketTester version which does not depend on junit
> ---------------------------------------------------
>
>                 Key: WICKET-226
>                 URL: https://issues.apache.org/jira/browse/WICKET-226
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket
>    Affects Versions: 1.2.5, 1.3, 2.0
>            Reporter: Joni Freeman
>             Fix For: 1.3
>
>         Attachments: WICKET-226-patch.txt.gz
>
>
> WicketTester has a dependency to junit (mostly in its assert* methods). It would be nice for WicketTester to be more generic, so that it would be possible to use it with other unit test tools. The assert methods could, for instance, be methods which return Result object. Result contains a message and boolean evaluation. Example:
> class Result {
>     private boolean evaluation;
>     private String message;
> }
> void assertRenderedPage(Class expectedReneredPageClass) -> Result  wasRenderedPage(Class expectedReneredPageClass)
> A junit specific JUnitWicketTester could extend the generic base class and provide junit style assertions as they are now implemented in WicketTester using the base class methods.
> void assertRenderedPage(Class expectedReneredPageClass) {
>     Result result = wasRenderedPage(expectedReneredPageClass);
>     Assert.true(result.evaluation(), result.message());
> }

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.