Files
gtk3/tests/a11y
Mario Sanchez Prada 45ecba2ea0 Update accessibility unit tests to consider password fields.
Updated test/a11y/entries.ui to include a new GtkEntry with
'visibility' set to FALSE, and update expectations.

https://bugzilla.gnome.org/show_bug.cgi?id=681591
2012-08-10 18:09:06 +02:00
..
2012-02-06 16:11:27 -05:00
2011-07-05 16:08:03 -04:00
2012-02-27 17:06:11 +00:00
2011-07-05 16:08:04 -04:00
2011-07-05 16:08:01 -04:00
2011-07-05 16:08:05 -04:00
2012-02-27 17:06:11 +00:00
2011-07-05 16:08:02 -04:00
2011-11-14 09:26:15 -05:00
2011-11-14 09:26:15 -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
2011-07-05 16:08:05 -04:00
2011-07-05 16:08:00 -04:00
2011-07-05 16:08:05 -04:00
2011-07-11 03:10:04 +02:00
2011-07-11 03:10:04 +02:00
2011-07-17 19:38:23 -04:00
2011-07-05 16:08:57 -04:00
2011-07-05 16:08:03 -04:00
2011-07-05 16:10:26 -04:00
2011-07-05 16:08:05 -04:00
2012-03-26 09:26:46 -04:00
2011-07-05 16:08:05 -04:00
2011-07-05 16:08:05 -04:00
2011-07-05 16:08:02 -04:00
2011-07-05 16:08:03 -04: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
2011-07-05 16:08:00 -04: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.