You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@click.apache.org by "Finn Bock (JIRA)" <ji...@apache.org> on 2010/07/07 21:20:52 UTC

[jira] Created: (CLK-708) Configurable loop count in performance unit test

Configurable loop count in performance unit test
------------------------------------------------

                 Key: CLK-708
                 URL: https://issues.apache.org/jira/browse/CLK-708
             Project: Click
          Issue Type: New Feature
            Reporter: Finn Bock
            Assignee: Finn Bock
            Priority: Minor


The testcases AttributeTest and FormTest contains performance tests that loops for 100.000 iterations. This normaly take less than 2 seconds, but when running with cobertura instrumented classes the tests takes more then 100 seconds each. I suggest that the performance tests gets the loop count from a system property and use a default value of 100.000.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Resolved: (CLK-708) Configurable loop count in performance unit test

Posted by "Finn Bock (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CLK-708?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Finn Bock resolved CLK-708.
---------------------------

    Fix Version/s: 2.3.0-M1
       Resolution: Fixed

get loop count from system propety "click.perf.loops".

> Configurable loop count in performance unit test
> ------------------------------------------------
>
>                 Key: CLK-708
>                 URL: https://issues.apache.org/jira/browse/CLK-708
>             Project: Click
>          Issue Type: New Feature
>            Reporter: Finn Bock
>            Assignee: Finn Bock
>            Priority: Minor
>             Fix For: 2.3.0-M1
>
>
> The testcases AttributeTest and FormTest contains performance tests that loops for 100.000 iterations. This normaly take less than 2 seconds, but when running with cobertura instrumented classes the tests takes more then 100 seconds each. I suggest that the performance tests gets the loop count from a system property and use a default value of 100.000.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.