Red Hat Bugzilla – Bug 822257
App creation problems got past scaling tests from the CLI in the cucumber tests - increase timeout or have better timeout messages?
Last modified: 2015-05-14 21:54:01 EDT
The li-test suite should have tests for creating a scaled application (with --scaling) for the major types with the @verify tag to ensure we do not have regressions in scaling code.
My bad - there are scaling tools but they aren't tagged @verify. We should probably add them to @verify (see if you can figure out who disabled it) and we should also get a test in place to cover the break to creating scaled apps that occurred, or ensure we have a better error message to explain why it failed (timeout on our end).
From recent experience, the scaled app creation timeout may have to be as high as 350 or 400s.
Matt has mostly supplanted these tests in the CLI and we're not seeing issues.