Message213492
I've sped up "wait for something to happen" tests in other contexts and
found the best solution to be a polling loop so that success is as fast as
possible and failure may be slow.
For example, rather than just having a 10 second timeout, it's often better
to have a 500 ms timeout, and keep trying again until the overall 10 second
deadline has expired.
This means the worst case tolerance for slow systems can be increased
without hurting test speed on fast systems (assuming you don't break the
test).
I haven't looked at Victor's cases here to see if any of them are amenable
to that approach, though. |
|
Date |
User |
Action |
Args |
2014-03-13 22:42:18 | ncoghlan | set | recipients:
+ ncoghlan, pitrou, vstinner, ned.deily, r.david.murray, neologix, zach.ware, serhiy.storchaka |
2014-03-13 22:42:18 | ncoghlan | link | issue20910 messages |
2014-03-13 22:42:18 | ncoghlan | create | |
|