myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Udo Schnurpfeil (JIRA)" <...@myfaces.apache.org>
Subject [jira] [Reopened] (TOBAGO-1652) Improve code coverage of enums
Date Mon, 12 Dec 2016 19:01:00 GMT

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

Udo Schnurpfeil reopened TOBAGO-1652:
-------------------------------------

The class TobagoClass needs to be tested better.

> Improve code coverage of enums
> ------------------------------
>
>                 Key: TOBAGO-1652
>                 URL: https://issues.apache.org/jira/browse/TOBAGO-1652
>             Project: MyFaces Tobago
>          Issue Type: Task
>            Reporter: Udo Schnurpfeil
>            Assignee: Henning Noeth
>            Priority: Trivial
>             Fix For: 3.0.1
>
>
> There are some enums which define constants, and have not only one string (by technical
reasons), like TobagoClass. These classes should automatically tested by a UnitTest for consistency.
> org.apache.myfaces.tobago.util.EnumUnitTest is a good utils as parent class for the test.
> By the way. These 2nd constant might be generated by the constructor, but this is often
not possible or the best way.
> E. g. 
> # String constants, that want to be used by annotations (CollapseMode), can't be initialized
by code. 
> # For CSS class names (TobagoClass), in my opinion, it's nice to have a way to use a
string search over the complete Java sources (e.g. "tobago-flexLayout" will find the enum
FLEX_LAYOUT, which can be find by the IDE). If you would generate the CSS name, you must know
internal details of the code to analyse the usage.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message