You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (Resolved) (JIRA)" <ji...@apache.org> on 2011/11/11 15:00:51 UTC

[jira] [Resolved] (WICKET-3979) Upgrade Wicket's tests to JUnit4

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

Martin Grigorov resolved WICKET-3979.
-------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.4

All tests are converted to JUnit4.
It is not possible to move ApacheLicenceHeaders mini test framework to a separate module (out of -util/src/test) because it uses classes from -util.
WicketTestCase can't be moved as well because it uses classes from -core.

                
> Upgrade Wicket's tests to JUnit4
> --------------------------------
>
>                 Key: WICKET-3979
>                 URL: https://issues.apache.org/jira/browse/WICKET-3979
>             Project: Wicket
>          Issue Type: Task
>    Affects Versions: 1.5-RC5.1
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>             Fix For: 1.5.4
>
>
> I'd like to upgrade all Wicket tests to JUnit4 to be able to categorize them (JUnit Category - http://kentbeck.github.com/junit/doc/ReleaseNotes4.8.html) - slow and fast tests.
> Currently org.apache.wicket.WicketTestCase (wicket-core) uses our custom org.apache.wicket.WicketJUnitRunner to be able to run both JUnit 3 and 4 based tests. I noticed that we have few more WicketTestCase classes spread in the other modules (copy/pasted). Maybe it will be good idea to introduce new module in testing/ folder which will be used as test dependency from all other modules. This new module will contain the custom JUnit runner, WicketTestCase, the licence test mini-framework, the XML well-formed test mini-framework, ... This way wicket-util:test wont be used as test dependency by others and will contain only its tests.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira