Jemmy timeouts have changed (see issue 27160) to
default 60 s, it prolong not only timeouts, but
the test runtime too!
It would be very useful to have something like
default timeouts, that should be easy to set on
the start each of test.
It would be nice to have default timeouts set on
the performance requests :
not exactly the same time, but for example 10
times more (limit 0.1 s -> timeout 1 s, ...)
If this is an issue for thousands os tests executed at once, we can
try to load a customized set of timeouts by JellyTestCase. I am
attaching a list of timeouts. Can someone suggest values for
particular timeouts? I already did - 60000 :-)
Created attachment 7908 [details]
list of related timeouts
Created attachment 7988 [details]
Estimation of jelly timeouts.
Implemented proposal of Alexandre Iline:
--- snip ----
In the JellyTestCase there is be an opportunity to load timeout values
from file defined from outside through system properties (which could
be set in xtest's xml files). We have two properties:
jelly.timeouts_file (to load from file) and jelly.timeouts_resource
(to load by classloader). jelly.timeouts_resource value has bigger
_Before_ reading timeouts from either of those variables,
JellyTestCase takes timeout values from default timeouts resource
which could be, for example, "org/netbeams/jellytools/timeouts". This
will aloow users to specify only those timeouts which are different
from Jelly defaults.
As default jellytools timeouts was used a set where maximum is 30 s.
Created attachment 8140 [details]
default jellytools timeouts
it seems like this way saves about 1 hour on each test machine , good