Extending subsequent tests with dogtail tests?

Miklos Vajna vmiklos at collabora.com
Fri Mar 8 10:32:57 UTC 2019


The current practice is: if 'make check' passes (which is more or less
enforced by Jenkins) and the change looks good to a reviewer, the change
goes in. And then releases are based on time, so it's really rare that
there are "blocker" bugs which would delay a release.

The ideal for any new kind of testing (including accessibility) is that
it's integrated into 'make check', and whatever those tests cover are
not OK to be broken anytime.

If the proposed a11y tests are part of make check, then it's easy to
promise that they won't be broken; otherwise it's just a best effort
thing without any guarantees.

At least that's how I understood what Markus wrote, and I agree with


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: Digital signature
URL: <https://lists.freedesktop.org/archives/libreoffice/attachments/20190308/e2bea2af/attachment.sig>

More information about the LibreOffice mailing list