You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sébastien Brisard (JIRA)" <ji...@apache.org> on 2012/06/01 07:31:24 UTC

[jira] [Commented] (MATH-795) Refactoring ArrayRealVectorTest, RealVectorTest, SparseRealVectorTest

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

Sébastien Brisard commented on MATH-795:
----------------------------------------

Thanks for the hint. Once I've finished cleaning up what's already in there, I'll take a look at Mahout.
                
> Refactoring ArrayRealVectorTest, RealVectorTest, SparseRealVectorTest
> ---------------------------------------------------------------------
>
>                 Key: MATH-795
>                 URL: https://issues.apache.org/jira/browse/MATH-795
>             Project: Commons Math
>          Issue Type: Improvement
>    Affects Versions: 3.1
>            Reporter: Sébastien Brisard
>            Assignee: Sébastien Brisard
>            Priority: Minor
>             Fix For: 3.1
>
>
> The above mentioned tests contain a lot of duplicate code. Besides, some of the unit tests are no longer _unit_ tests, since they test many different functionalities.
> It is proposed to refactor these tests. The duplicate code should be factored out to the abstract class {{RealVectorAbstractTest}}. Then some tests could be splitted in smaller units.
> Besides readability, the benefit would be to ease the implementation of other kinds of vector. This refactoring should also lead to a natural resolution of MATH-625.

--
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