| Age | Commit message (Collapse) | Author |
|---|
|
I used solenv/gbuild/Trace.mk to measure where the time is spent at the
end of an incremental 'make check'. The last 141 seconds is spent
executing UITest_writer_demo alone.
If that test is executed in isolation, it takes 289 seconds. I measured
the cost of all the individual .py suites and arranged them into 8
separate UITests, this way the make -j8 cost is 101 seconds (i.e. 35% of
the baseline). IOW this is supposed to speed up 'make check' with 3m13s,
provided you have the code already built.
Change-Id: I1ffee3a06b8fd84d7b9a0295547900df11f11f68
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/89835
Tested-by: Jenkins
Reviewed-by: Miklos Vajna <vmiklos@collabora.com>
|
|
Change-Id: I76637b76151a33c9f9f4b218aa01b5e813e9da1f
Reviewed-on: https://gerrit.libreoffice.org/32283
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Markus Mohrhard <markus.mohrhard@googlemail.com>
|
|
Change-Id: I90adb3bf9eefcf687e4a76d58aefb9a5775e5e88
|
|
That test just shows features of the test and the use of different UI
objects.
Change-Id: I49e9fa2d42634951ae5a78aa3a9bf79fefacd298
|
|
Change-Id: Id5d5c53b5d51b7c8984c93e8c89b0a71b8c660bd
|
|
Change-Id: I4ba2321deb196f22c95db533266d82c541a95f0a
|
|
Change-Id: I18557ea0a7801ba118fd2486338112d8aa917b75
|
|
We now can call the uitests with make uitest.uickeck
Change-Id: I20c73efd93c7987f3b841cd0e3e7842ee7a5dab9
|
