[jboss-jira] [JBoss JIRA] (WFCORE-1367) Test framework for CLI-based tests can be very slow

[Tomaz Cerar (JIRA)]

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

Tomaz Cerar closed WFCORE-1367.
-------------------------------
    Fix Version/s: 3.0.0.Beta9
       Resolution: Done


Looking at code, there are no timeouts involved anymore.

And it looks like tests run quite fast.

> Test framework for CLI-based tests can be very slow
> ---------------------------------------------------
>
>                 Key: WFCORE-1367
>                 URL: https://issues.jboss.org/browse/WFCORE-1367
>             Project: WildFly Core
>          Issue Type: Bug
>          Components: CLI, Test Suite
>            Reporter: David Bosschaert
>            Priority: Minor
>             Fix For: 3.0.0.Beta9
>
>
> The org.jboss.as.test.integration.management.base.AbstractCliTestBase provides a suitable API for testing CLI-based operations. However, running tests with a relatively large number of CLI operations can take a *long* time, seemingly much longer than necessary. This is probably related to the fact that CLIWrapper.readAllAsOpResult() method always seems to wait until the lineTimeout has expired. 
> Typically the WAIT_LINETIMEOUT value is used for this argument. Shortening the timeout is not an option as I have seen cases where a test would fail when run on a slow machine, but this only happens occasionally.
> It would be *much* better if a timeout was not needed for this and the test would wait until a certain operation was finished.
> This can be observed in org.jboss.as.test.integration.management.cli.JmsTestCase and I also experienced it when writing the org.jboss.as.test.integration.osgi.management.OSGiManagementTestCase.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)