Files
gtk3/tests/a11y
Matthias Clasen fbb1ee02bc Add a test for setting accessible name from gtkbuilder
This is wrongly documented in the GtkWidget docs.
2013-02-10 15:47:08 -05:00
..
2013-02-04 00:57:46 -05:00
2012-02-27 17:06:11 +00:00
2011-07-05 16:08:05 -04:00
2013-02-04 00:57:46 -05:00
2011-11-14 09:26:15 -05:00
2013-02-04 00:57:46 -05:00
2012-11-12 09:21:27 -06:00
2013-02-04 00:57:46 -05:00
2012-02-27 17:06:11 +00:00
2012-03-20 11:34:11 -04:00
2011-07-05 16:08:05 -04:00
2012-11-07 20:21:50 -05:00
2011-07-05 16:08:05 -04:00
2013-02-04 00:57:46 -05:00
2011-07-05 16:08:05 -04:00
2013-02-04 00:57:46 -05:00
2011-07-11 03:10:04 +02:00
2013-02-04 00:57:46 -05:00
2011-07-05 16:08:57 -04:00
2013-02-04 00:57:46 -05:00
2013-02-04 00:57:46 -05:00
2011-07-05 16:08:05 -04:00
2013-02-04 10:50:24 -05:00
2011-07-05 16:08:05 -04:00
2011-07-05 16:08:05 -04:00
2013-02-04 01:03:37 -05:00
2011-07-05 16:08:05 -04:00
2011-07-05 16:08:05 -04:00
2012-01-30 19:12:27 -05:00
2012-02-27 17:06:11 +00:00
2012-02-27 17:06:11 +00:00
2012-02-27 17:06:11 +00:00
2012-02-27 17:06:11 +00: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.