Feature #10497
Make timeout configurable via environment variable
100%
Description
The timeout used by selenese to wait for events in the UI should be more easily controllable, maybe via an environment variable or more locally per test or per test-case class. This would allow making it as short as possible by default or at least in a non-interactive execution environment like on the Jenkins server, but setting it to something long when a developer needs the time for debugging.
Related issues
Associated revisions
Revision 598:9a8abb924a1f
(diff)
Fixes #10497: Make timeout configurable via environment variable
History
#1
Updated by Christian Zagrodnick over 8 years ago
Updated by self.selenium.setTimeout(7500) ?
#2
Updated by Wolfgang Schnerring about 8 years ago
Updated by - Category set to API/Selenese
#3
Updated by Wolfgang Schnerring about 8 years ago
- Status changed from New to Confirmed
#4
Updated by Wolfgang Schnerring about 8 years ago
- Priority changed from Normal (P3) to Low (P4)
#5
Updated by Florian Pilz about 7 years ago
Updated by Fände ich gerade auch sehr praktisch, daher push. Oder gibt es das mittlerweile? Default Timeout von 30s ist bei 90s Laufzeit für alle Tests doch recht lang.
#6
Updated by Wolfgang Schnerring about 7 years ago
- Subject changed from Make timeout externally controllable to Make timeout configurable via environment variable
The timeout is externally configurable Selenese.setTimeout (needs to be done in TestCase.setUp, since the Selenese object is recreated for each test run).
We might want to offer a GOCEPT_SELENIUM_TIMEOUT variable for convenience, though.
#7
Updated by Wolfgang Schnerring about 7 years ago
- Status changed from Confirmed to Fix committed
- % Done changed from 0 to 100
Applied in changeset 9a8abb924a1f.
#8
Updated by Wolfgang Schnerring over 6 years ago
- Status changed from Fix committed to Fix released
2.1.0
Re #10497: Move instantiating Selenese object from testSetUp to layer setUp