gtk/testsuite/a11y
2016-01-30 11:04:22 -05:00
..
state Use TAP output for installed tests 2016-01-30 11:04:22 -05:00
a11ychildren.test.in Use TAP output for installed tests 2016-01-30 11:04:22 -05:00
a11yderive.test.in Fight deprecation warnings in test 2014-06-28 00:41:26 -04:00
a11ymisc.test.in Use TAP output for installed tests 2016-01-30 11:04:22 -05:00
a11ytests.test.in Fight deprecation warnings in test 2014-06-28 00:41:26 -04:00
a11ytext.test.in Use TAP output for installed tests 2016-01-30 11:04:22 -05:00
a11ytree.test.in Use TAP output for installed tests 2016-01-30 11:04:22 -05:00
a11yutil.test.in Use TAP output for installed tests 2016-01-30 11:04:22 -05:00
a11yvalue.test.in Use TAP output for installed tests 2016-01-30 11:04:22 -05:00
about.txt Update expected results of a11y tests 2016-01-03 10:56:11 -05:00
about.ui
accessibile-name.txt
accessibility-dump.c a11y tests: Avoid deprecation warnings 2014-05-02 20:59:00 -04:00
accessible-name.txt
accessible-name.ui
actionbar.txt Update expected results 2014-11-23 18:53:06 -05:00
actionbar.ui
assistant.txt Fix up expected results of a11y tests 2015-06-23 17:08:14 -04:00
assistant.ui
buttons.txt Update expected output in a11y tests for buttons 2014-08-16 13:01:50 -04:00
buttons.ui
calendar.txt
calendar.ui
children.c
colorchooser.txt Update expected output for a11y tests 2014-07-21 19:21:02 -04:00
colorchooser.ui
combos.txt
combos.ui
derive.c
entries.txt Adapt to spinbutton changes 2014-08-14 19:39:07 -04:00
entries.ui
expander.txt
expander.ui
headerbar.txt
headerbar.ui
hello-world.txt
hello-world.ui
iconview.txt
iconview.ui
infobar.txt
infobar.ui
label.txt Update expected results of a11y tests 2014-10-27 20:03:51 -04:00
label.ui
link.txt Update expected results of a11y tests 2014-10-27 20:03:51 -04:00
link.ui
listbox.txt
listbox.ui
lockbutton.txt Update expected results of a11y tests 2014-10-27 20:03:51 -04:00
lockbutton.ui
Makefile.am Implement support for ATK_STATE_HAS_TOOLTIP 2014-10-22 22:55:13 -04:00
menu.txt Update expect output of a11y tests 2016-01-08 18:11:07 -05:00
menu.ui
menubutton2.txt Update expect output of a11y tests 2016-01-08 18:11:07 -05:00
menubutton2.ui
menubutton3.txt Update expect output of a11y tests 2016-01-08 18:11:07 -05:00
menubutton3.ui
menubutton.txt Update expect output of a11y tests 2016-01-08 18:11:07 -05:00
menubutton.ui
menus.txt Update expect output of a11y tests 2016-01-08 18:11:07 -05:00
menus.ui
messagedialog.txt Update expected output of a11y tests 2016-01-19 09:19:31 -05:00
messagedialog.ui
misc.c Add a test for popover accessible parents 2014-07-30 23:14:49 +02:00
mnemonic.txt
mnemonic.ui
notebook.txt
notebook.ui
paned.txt Update expected output of a11y tests 2016-01-25 16:01:07 -05:00
paned.ui
pickers.txt Update expected output for the font picker a11y test 2014-08-16 13:02:47 -04:00
pickers.ui
placeholder-text.txt
placeholder-text.ui
progress.txt
progress.ui
range.txt
range.ui
README
scale-drawvalue.txt Update expect output of a11y tests 2016-01-08 18:11:07 -05:00
scale-drawvalue.ui
spinner.txt
spinner.ui
stack.txt Update expected output in a11y tests for buttons 2014-08-16 13:01:50 -04:00
stack.ui
statusbar.txt
statusbar.ui
testfocus.c
text.c Improve text a11y test 2015-10-15 22:35:38 -04:00
text.txt
text.ui
tooltips.txt Update expect output of a11y tests 2016-01-08 18:11:07 -05:00
tooltips.ui Implement support for ATK_STATE_HAS_TOOLTIP 2014-10-22 22:55:13 -04:00
tree-performance.c
tree-relationships.c
tree.txt
tree.ui
util.c
value.c Remove redundant checks for NULL 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.