You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@zookeeper.apache.org by "Kezhu Wang (Jira)" <ji...@apache.org> on 2024/09/28 15:14:00 UTC
[jira] [Updated] (ZOOKEEPER-4738) Clean test cases by refactoring assertFalse(equals()) with assertNotEquals
[ https://issues.apache.org/jira/browse/ZOOKEEPER-4738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kezhu Wang updated ZOOKEEPER-4738:
----------------------------------
Fix Version/s: 3.10.0
> Clean test cases by refactoring assertFalse(equals()) with assertNotEquals
> --------------------------------------------------------------------------
>
> Key: ZOOKEEPER-4738
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4738
> Project: ZooKeeper
> Issue Type: Improvement
> Reporter: Taher Ghaleb
> Assignee: Zili Chen
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.10.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> I am working on research that investigates test smell refactoring in which we identify alternative implementations of test cases, study how commonly used these refactorings are, and assess how acceptable they are in practice.
> This smell occurs when inappropriate assertions are used, while there exist better alternatives. For example, *{{assertFalse(x.equals( y ));}}* can be refactored using {*}{{assertNotEquals(x, y);}}{*}.
> I would like to get your feedback on this particular test smell and its refactoring. Thanks in advance for your input.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)