[jboss-jira] [JBoss JIRA] (WFLY-623) TS: Configurable timeouts

[Jason Greene (JIRA)]

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

Jason Greene moved AS7-2827 to WFLY-623:
----------------------------------------

          Project: WildFly  (was: Application Server 7)
              Key: WFLY-623  (was: AS7-2827)
      Component/s:     (was: Test Suite)
    Fix Version/s:     (was: 7.1.1.Final)

    
> TS: Configurable timeouts
> -------------------------
>
>                 Key: WFLY-623
>                 URL: https://issues.jboss.org/browse/WFLY-623
>             Project: WildFly
>          Issue Type: Sub-task
>            Reporter: Ondrej Zizka
>            Assignee: Ondrej Zizka
>
> 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
> * Database operations
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira