[jboss-jira] [JBoss JIRA] (AS7-2827) TS: Configurable timeouts

[Ondrej Zizka (Updated) (JIRA)]

     [ https://issues.jboss.org/browse/AS7-2827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ondrej Zizka updated AS7-2827:
------------------------------

    Description: 
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.

We should also divide them into categories, depending on what is expected to take long (consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
For each category, there would be a ratio, 1.0 by default, which would multiply the timeout.

So the timeout would look like:

{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}

Other possibility is to use @Annotations to mark tests belonging to certain group, like @LongRunning or such.

  was:
Testsuite run can take different amount of time on various HW (or virtuals).
All timeouts must be configurable, in the sense of being possible to prolong.

We should also divide them into categories, depending on what is expected to take long (consider slow disks, slow networks, cloud environment)
Few ideas for categories:
* Filesystem I/O
* Processor
* Network I/O
* Memory I/O
For each category, there would be a ratio, 1.0 by default, which would multiply the timeout.

So the timeout would look like:

{code}
something.setTimeout( 1000 * Timeouts.getFSIORatio() );
{code}


    
> TS: Configurable timeouts
> -------------------------
>
>                 Key: AS7-2827
>                 URL: https://issues.jboss.org/browse/AS7-2827
>             Project: Application Server 7
>          Issue Type: Sub-task
>          Components: Test Suite
>            Reporter: Ondrej Zizka
>            Assignee: Ondrej Zizka
>             Fix For: 7.1.0.Final
>
>
> Testsuite run can take different amount of time on various HW (or virtuals).
> All timeouts must be configurable, in the sense of being possible to prolong.
> We should also divide them into categories, depending on what is expected to take long (consider slow disks, slow networks, cloud environment)
> Few ideas for categories:
> * Filesystem I/O
> * Processor
> * Network I/O
> * Memory I/O
> For each category, there would be a ratio, 1.0 by default, which would multiply the timeout.
> So the timeout would look like:
> {code}
> something.setTimeout( 1000 * Timeouts.getFSIORatio() );
> {code}
> Other possibility is to use @Annotations to mark tests belonging to certain group, like @LongRunning or such.

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