You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@wicket.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/08/30 19:45:00 UTC

[jira] [Commented] (WICKET-6583) Upgrade Tests to Junit5

    [ https://issues.apache.org/jira/browse/WICKET-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597835#comment-16597835 ] 

ASF GitHub Bot commented on WICKET-6583:
----------------------------------------

Github user renoth commented on the issue:

    https://github.com/apache/wicket/pull/287
  
    I have returned from vacation and created https://issues.apache.org/jira/browse/WICKET-6583 i will begin the upgrade over the next weeks. Comments and suggestions very welcome.


> Upgrade Tests to Junit5
> -----------------------
>
>                 Key: WICKET-6583
>                 URL: https://issues.apache.org/jira/browse/WICKET-6583
>             Project: Wicket
>          Issue Type: Task
>          Components: wicket
>            Reporter: Johannes Renoth
>            Priority: Minor
>
> Since Junit 4 is no longer actively developed Wicket should upgrade to Junit 5 in a future release.
> To be able to use the new Junit 5 there should be an upgrade from Junit 4 to 5. Also the hard dependencies of WicketTester and other test classes to Junit 4 should be refactored out.
>  
> Quick overview of migration from 4 to 5: 
> https://www.baeldung.com/junit-5-migration
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)