Files
gtk/testsuite/a11y
Christoph Reiter c60ea284c5 testsuite/a11y: Fix missing glib schemas
The a11y tests complain that org.gtk.Settings schemas are missing
and fail. This copies the code to build and include the schemas from
the reftests testsuite.
2018-02-15 12:30:57 +01:00
..
2017-07-18 22:55:39 -04:00
2014-02-22 12:31:18 -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
2017-06-20 15:16:19 -04:00
2013-06-24 19:53:08 -04:00
2017-06-20 15:16:19 -04:00
2017-06-20 15:16:19 -04:00
2017-06-20 15:16:19 -04:00
2017-06-20 15:16:19 -04:00
2016-03-04 23:51:39 -05:00
2016-03-04 23:51:39 -05:00
2017-06-20 15:16:19 -04: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
2017-06-20 15:16:19 -04:00
2016-03-04 23:51:39 -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.