Closed GoogleCodeExporter closed 9 years ago
Which methods are you thinking about? I think the relevant methods do offer
timeouts to be set.
Original comment by renasr...@gmail.com
on 22 Aug 2012 at 7:21
I mean that I'd like to be able to override the default timeouts globally so I
don't have to call the long-signature methods repeatedly throughout my code.
Original comment by glenview...@gmail.com
on 22 Aug 2012 at 7:27
You will need to wrap them. You can create your own waitFor methods in a helper
class based on your preferred settings (not just timeouts). That is something I
recommend users to do as it improves the test cases (e.g. waitFor methods that
should not scroll etc)
Original comment by renasr...@gmail.com
on 22 Aug 2012 at 7:37
Right, that's the alternative.. I'd rather see a stateful Robotium where I can
set defaults either with setters or in the Solo constructor. If you've
received other requests for this, maybe you should consider it more seriously.
Original comment by glenview...@gmail.com
on 22 Aug 2012 at 7:49
I will surely accept this if more people ask for it. Lets see if that
becomes the case.
Original comment by renasr...@gmail.com
on 22 Aug 2012 at 8:06
Fair enough, and thanks as usual for the great tool!
Original comment by glenview...@gmail.com
on 22 Aug 2012 at 8:07
Thank you for contributing with good suggestions.
Original comment by renasr...@gmail.com
on 22 Aug 2012 at 8:20
+1 for this feature. We run Robotium in testing machines - which are generally
slower. Changing the default timeout globally would be awesome.
Original comment by rdsub...@gmail.com
on 11 Apr 2013 at 5:01
This has been included in Robotium 4.2.
Original comment by renasr...@gmail.com
on 25 Jun 2013 at 8:32
Original issue reported on code.google.com by
glenview...@gmail.com
on 22 Aug 2012 at 5:52