commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedikt Ritter (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SANDBOX-379) [BeanUtils2] Implement describe() on DefaultBeanAccessor
Date Fri, 03 Feb 2012 09:49:54 GMT

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

Benedikt Ritter commented on SANDBOX-379:
-----------------------------------------

As I said above, {{describe()}}, {{populate()}}, {{clone()}}, etc are the endpoints of a fluent
call. So I thought putting them together in one test is a good idea.

{quote}
It would be more obvious creating a serie of DescribeTestCase
{quote}

Okay, so do we create a test case for every method on {{BeanAccessor}}? I think that would
be a good idea. I don't like huge test classes. And a test class for all methods on {{BeanAccessor}}
would be gigantic (as you mentioned).
                
> [BeanUtils2] Implement describe() on DefaultBeanAccessor 
> ---------------------------------------------------------
>
>                 Key: SANDBOX-379
>                 URL: https://issues.apache.org/jira/browse/SANDBOX-379
>             Project: Commons Sandbox
>          Issue Type: Improvement
>          Components: BeanUtils2
>    Affects Versions: Nightly Builds
>            Reporter: Benedikt Ritter
>         Attachments: SANDBOX-379.txt
>
>
> Implement the above mentioned method an corresponding unit tests

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message