Files
gtk/testsuite/a11y
Matthias Clasen 396deb44fa Convert ui files
Run gtk4-builder-tool simplify --3to4 over all ui files.
2019-03-27 21:48:12 -04:00
..
2019-03-16 21:49:24 -04:00
2019-03-27 13:36:24 -04:00
2016-10-18 00:34:41 +02:00
2017-10-18 17:30:20 +02:00
2019-03-16 21:49:24 -04:00
2017-01-19 13:50:17 -05:00
2017-10-18 17:30:20 +02:00
2016-10-16 18:17:21 +02:00
2019-03-27 13:36:24 -04:00
2016-10-18 00:34:41 +02:00
2016-10-18 00:34:41 +02:00
2019-03-16 21:49:24 -04:00
2019-03-16 21:49:24 -04:00
2019-01-23 19:27:35 -05:00
2016-10-18 00:34:41 +02:00
2016-10-18 00:34:41 +02:00
2019-03-16 21:49:24 -04:00
2016-10-18 00:34:41 +02:00
2017-10-18 17:30:20 +02:00
2019-02-21 00:31:17 -05:00
2019-01-23 19:27:35 -05:00
2019-03-27 21:48:12 -04:00
2019-03-16 21:49:24 -04:00
2019-03-16 21:49:24 -04:00
2019-02-08 09:51:45 -05:00
2017-01-20 21:37:04 +01:00
2017-10-18 17:30:20 +02:00
2019-02-19 00:25:59 -05:00
2017-10-18 17:30:20 +02:00
2019-03-16 21:49:24 -04:00
2017-10-18 17:30:20 +02:00
2019-03-16 21:49:24 -04:00
2017-10-18 17:30:20 +02:00
2014-10-02 19:06:03 +02:00
2017-10-18 17:30:20 +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.