You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Evan Ward (JIRA)" <ji...@apache.org> on 2013/09/16 20:47:07 UTC

[jira] [Commented] (MATH-1026) Separate Optimization Problem from Algorithm

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

Evan Ward commented on MATH-1026:
---------------------------------

I'm back. :)

I understand the desire for small patches. But any patch on the test cases would have been large because of all the code that was copied and pasted between the methods. Instead of thinking of it as more differences to review, think of it as fewer lines of code to review. Previously, the test cases had to perform the same setup. Now the common setup is encapsulated in just a handful of methods and each test case only needs to perform its test-specific setup. Since developer time is roughly proportional to lines of code, this saved several hours.

If you would prefer JUnit to directly execute each test case we can relatively easily switch to that behaviour. Either way the same functionality is tested.

What do I need to do to move this forward?
                
> Separate Optimization Problem from Algorithm
> --------------------------------------------
>
>                 Key: MATH-1026
>                 URL: https://issues.apache.org/jira/browse/MATH-1026
>             Project: Commons Math
>          Issue Type: Improvement
>            Reporter: Evan Ward
>         Attachments: opt.tar.gz
>
>
> See discussion on the mailing list starting with: http://www.mail-archive.com/dev@commons.apache.org/msg39681.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira