[Libreoffice-qa] minutes of ESC call ...

Michael Stahl mstahl at redhat.com
Fri May 15 02:37:35 PDT 2015

On 14.05.2015 16:47, Michael Meeks wrote:
>         + can't run make check: seems to fail badly with ssh build.
>         + database related stuff seems to require a display.
>         + 'make' says waiting for rest to finish
>             + tons of Java/JUnit not moving / exiting.
>             + concerned wrt. Java etc.
>         + would love gdb backtracing through Java (Michael)
>         + JUnit tests not in-process (Markus)

in case of a crash, you already get the Java backtrace in tinderbox
failure mails: it is printed on the next UNO call, and it's always
something like "com.sun.star.lang.DisposedException: java_remote_bridge"
(unless the test does something stupid and somehow suppresses printing
of the exception backtrace).

but you have to manually combine this Java backtrace with the C++
backtrace printed by gdb.

also at least for the unoapi tests the Java backtrace can be quite
unhelpful if it's one of the overly generic object-oriented tests like
the XPropertySet ones; the printed LOG output is more helpful then.

>         + need a more systematic UX testing thing (Michael)
>         + yes - would like to have something (Markus)
>             + propose talk in the conference
>             + new UX stuff provides nice ways to get it working.
>         + an incremental way to test it.
>         + possible to create a robust way to test UX (Michael)
>             + do the 80/20 rule (Norbert)
>             + something reliable & simple needed (Markus)

i'd hope the A11y interfaces could be useful for UI testing - that
should make the tests relatively robust against cosmetic changes to the
UI, and a11y needs testing anyway.

e.g. something like this looks promising:

More information about the Libreoffice-qa mailing list