3426dcfec2
Add tests for the GTK3 accessibility platform layer. These tests compare the internal LO representation with what is visible to the platform, and thus the user's accessibility tools. In most cases the tests are fairly trivial as LO's internals are not far off AT-SPI2's expectations. There are however notable exceptions like for example the text attributes, that have a wildly different representation and require more complex checks matching what LO's platform layer does, the other way around. These tests use libatspi2 directly, but as the C API is awful to work with regarding resource management, there are wrappers to handle the complexity using RAII. The resulting API is fairly trivial to use. As these tests require using the GTK3 VCL plugin and for the a11y tree to be visible to AT-SPI2, they are run under XVFB using a separate dbus session through dbus-launch. Working on this has already lead to reporting and/or solving some issues: * https://gerrit.libreoffice.org/c/core/+/151303 * https://gerrit.libreoffice.org/c/core/+/151650 * https://gerrit.libreoffice.org/c/core/+/152456 * https://gerrit.libreoffice.org/c/core/+/152457 * https://bugs.documentfoundation.org/show_bug.cgi?id=155625 * https://bugs.documentfoundation.org/show_bug.cgi?id=155705 * https://gerrit.libreoffice.org/c/core/+/152748 Only a subset of the a11y APIs are covered for the moment, but the current state should make it easy to extend upon. Change-Id: I1a047864ce8dc1f1bc3056ad00159f7fd5e5b7d3 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/153069 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de> |
||
|---|---|---|
| .. | ||
| Jenkins | ||
| CPAndroid.conf | ||
| CPAndroidAarch64.conf | ||
| CPAndroidBranding.conf | ||
| CPAndroidX86.conf | ||
| CPAndroidX86_64.conf | ||
| CPLinux-LOKit.conf | ||
| LibreOfficeAndroid.conf | ||
| LibreOfficeAndroidAarch64.conf | ||
| LibreOfficeAndroidX86.conf | ||
| LibreOfficeAndroidX86_64.conf | ||
| LibreOfficeCoverity.conf | ||
| LibreOfficeFlatpak.conf | ||
| LibreOfficeHaiku.conf | ||
| LibreOfficeiOS.conf | ||
| LibreOfficeiOS_Sim.conf | ||
| LibreOfficeLinux.conf | ||
| LibreOfficeMacOSX.conf | ||
| LibreOfficeOnline.conf | ||
| LibreOfficeOpenBSD.conf | ||
| LibreOfficeOssFuzz.conf | ||
| LibreOfficeVanillaMacAppStore.conf | ||
| LibreOfficeWASM32.conf | ||
| LibreOfficeWin32.conf | ||
| LibreOfficeWin64.conf | ||
| LibreOfficeWinArm64.conf | ||
| README.md | ||
Pre-canned Distribution Configurations
These files are supposed to correspond to the options used when
creating the Document Foundation (or other "canonical") builds of
LibreOffice for various platforms. They are not supposed to
represent the "most useful" options for developers in general. On the
contrary, the intent is that just running ./autogen.sh without any
options at all should produce a buildable configuration for developers
with interest in working on the most commonly used parts of the code.
See https://wiki.documentfoundation.org/Development/ReleaseBuilds for how
TDF builds make use of these switches. (Especially, since --with-package-format
now triggers whether or not installation sets are built, all the relevant *.conf
files specify it, except for LibreOfficeLinux.conf, where the TDF build
instructions pass an explicit --with-package-format="rpm deb" in addition to
--with-distro=LibreOfficeLinux.)
(Possibly the above is a misunderstanding, or maybe there never even has been any clear consensus what situations these files actually are intended for.)
The files contain sets of configuration parameters, and can be passed
on the autogen.sh command line thus:
./autogen.sh --with-distro=LibreOfficeFoo
Contrary to the above, in the Android case the amount of parameters you just must use is so large, that for convenience it is always easiest to use the corresponding distro-configs file. This is a bug and needs to be fixed; also configuring for Android should ideally use sane (or the only possible) defaults and work fine without any parameters at all.