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

Posted to issues@commons.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2020/10/07 14:19:00 UTC

[jira] [Resolved] (BCEL-343) Improve JUnit assertions

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

Gary D. Gregory resolved BCEL-343.
----------------------------------
    Fix Version/s: 6.5.1
       Resolution: Fixed

In git master; please verify git master and close this ticket.

> Improve JUnit assertions
> ------------------------
>
>                 Key: BCEL-343
>                 URL: https://issues.apache.org/jira/browse/BCEL-343
>             Project: Commons BCEL
>          Issue Type: Task
>          Components: Build
>            Reporter: Allon Mureinik
>            Priority: Major
>             Fix For: 6.5.1
>
>
> Followup to BCEL-342, based on the discussion in the PR ([https://github.com/apache/commons-bcel/pull/68#issuecomment-703671353)] - now that the project used JUnit Jupiter, it's worth checking if the assertions can be improved to use String suppliers instead of string methods and improve performance.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)