Files
gtk3/testsuite/a11y
Emmanuele Bassi 2b0a605c5d build: Remove the Autotools build
CI and downstream packagers have been using the Meson build for a while
now, and we checked that it's idempotent to the Autotools build.

Having two build systems in tree doesn't make maintaining and releasing
GTK any easier, even if it's the stable/frozen branch.
2022-12-08 11:57:39 +00:00
..
2022-12-08 11:57:39 +00:00
2019-09-03 22:34:36 -04:00
2019-04-13 12:49:27 +02:00
2019-09-03 22:34:36 -04:00
2014-02-22 12:31:18 -05:00
2020-11-07 22:40:41 -05:00
2019-09-03 22:34:36 -04:00
2019-11-27 13:16:22 -05:00
2016-03-04 23:51:39 -05:00
2016-03-04 23:51:39 -05:00
2013-09-21 20:51:22 -04:00
2021-12-20 17:18:55 -05:00
2013-06-24 19:53:08 -04:00
2021-12-20 17:18:55 -05:00
2021-12-20 17:18:55 -05:00
2021-12-20 17:18:55 -05:00
2021-12-20 17:18:55 -05:00
2016-03-04 23:51:39 -05:00
2016-03-04 23:51:39 -05:00
2021-12-20 17:18:55 -05:00
2016-06-01 14:18:46 -04:00
2015-10-15 22:35:38 -04:00
2016-03-04 23:51:39 -05:00
2021-12-20 17:18:55 -05:00
2018-12-19 21:09:59 -05:00
2014-01-13 23:51:26 -05:00
2014-10-02 19:06:03 +02:00

accessibility-dump is a test runner that can do tests of static
accessibility information. Run it like this:

./accessibility-dump [OPTIONS] TESTFILE [TESTFILES...]

where TESTFILE is a GtkBuilder .ui file. accessibility-dump creates
a textual dump of the accessibility information for the created
widget hierarchy and compares it to a preexisting .txt file.

To create an initial dump, you can use the --generate option with
a single .ui file. You should carefully inspect the output before
blessing it as the official .txt to compare against.

To find out details about a failure, you can use the --verbose
option to see differences between expected and actual output.

When run without any arguments, all the .ui files in the current
directory are tested.