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 2024/04/19 11:13:00 UTC

[jira] [Comment Edited] (CLI-330) Migrate all the Parser Test cases away from Deprecated Optionbuilder

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

Gary D. Gregory edited comment on CLI-330 at 4/19/24 11:12 AM:
---------------------------------------------------------------

Nope, not migration, which implies removal of existing tests. Deprecated APIs must be covered by tests just like any other. The same functionality can be covered in new tests using new APIs but if the code coverage does not increase there might be no point.


was (Author: garydgregory):
Nope, not migration, which implies removal of existing tests. Deprecated APIs must be covered by just like any other. The same functionality can be covered in new tests using new APIs but if the code coverage does not increase there might be no point.

> Migrate all the Parser Test cases away from Deprecated Optionbuilder
> --------------------------------------------------------------------
>
>                 Key: CLI-330
>                 URL: https://issues.apache.org/jira/browse/CLI-330
>             Project: Commons CLI
>          Issue Type: Improvement
>          Components: Parser
>    Affects Versions: 1.7.0
>            Reporter: Sruteesh Kumar Paramata
>            Priority: Major
>              Labels: test-stability
>
> It is better if we migrate all the Parser Test cases away from the deprecated Optionbuilder. This would really help us identify any potential issues with Option class just like [CLI-317|CLI-317]



--
This message was sent by Atlassian Jira
(v8.20.10#820010)