[
https://issues.apache.org/jira/browse/QPIDIT-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kim van der Riet updated QPIDIT-101:
------------------------------------
Affects Version/s: (was: Future)
0.1.0
Fix Version/s: Future
> Create a configurable timeout option for all tests
> --------------------------------------------------
>
> Key: QPIDIT-101
> URL: https://issues.apache.org/jira/browse/QPIDIT-101
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Improvement
> Affects Versions: 0.1.0
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
> Fix For: Future
>
>
> Currently, a hard-wired timeout is used for all tests. However, some tests
> need more time than others. For example, the large content tests need many
> minutes per test to complete, but other tests only need several seconds.
> When these shorter tests fail or get stuck, it is not helpful to wait for a
> ridiculously long time because one test needs it.
> It might be helpful to provide each test with a command-line parameter to set
> the timeout for that test. If not specified on the command-line, each test
> should provide a reasonable default for that test based on the time required
> for slower machines.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
