gtk2/testsuite/a11y
2017-10-18 17:30:20 +02:00
..
state Drop Autotools build 2017-08-14 22:23:09 +01:00
about.txt a11y tests: Update expected results 2017-07-19 15:46:32 -04:00
about.ui
accessibile-name.txt
accessibility-dump.c tests: Include system headers appropriately 2017-07-21 23:36:03 +08:00
accessible-name.txt
accessible-name.ui
actionbar.txt Update a11y test output 2017-05-22 21:42:18 -04:00
actionbar.ui
assistant.txt Update some a11y tests 2017-10-11 20:09:21 -05:00
assistant.ui
buttons.txt Fix unittests 2016-10-18 00:34:41 +02:00
buttons.ui Fix unittests 2016-10-18 00:34:41 +02:00
calendar.txt
calendar.ui
children.c testsuite: Remove GtkEventBox from a11y test 2017-08-02 16:47:39 +01:00
children.test.in Test suite cosmetics 2017-10-18 17:30:20 +02:00
colorchooser.txt Fix the a11y test 2017-10-18 17:30:20 +02:00
colorchooser.ui
combos.txt a11y tests: Update test results 2017-03-31 14:04:59 -04:00
combos.ui
derive.c Update callers 2017-01-19 13:50:17 -05:00
derive.test.in Test suite cosmetics 2017-10-18 17:30:20 +02:00
entries.txt Update some a11y tests 2017-10-11 20:09:21 -05:00
entries.ui Fix a few css/a11y test cases 2016-10-16 18:17:21 +02:00
expander.txt Update some a11y tests 2017-10-11 20:09:21 -05:00
expander.ui
headerbar.txt
headerbar.ui
hello-world.txt
hello-world.ui Fix unittests 2016-10-18 00:34:41 +02:00
iconview.txt
iconview.ui
infobar.txt Fix unittests 2016-10-18 00:34:41 +02:00
infobar.ui
label.txt a11y tests: Update test results 2017-03-31 14:04:59 -04:00
label.ui
link.txt
link.ui
listbox.txt
listbox.ui
lockbutton.txt
lockbutton.ui
menu.txt Update some a11y tests 2017-10-11 20:09:21 -05:00
menu.ui Fix unittests 2016-10-18 00:34:41 +02:00
menubutton2.txt Update some a11y tests 2017-10-11 20:09:21 -05:00
menubutton2.ui
menubutton3.txt Update some a11y tests 2017-10-11 20:09:21 -05:00
menubutton3.ui
menubutton.txt Update some a11y tests 2017-10-11 20:09:21 -05:00
menubutton.ui Fix unittests 2016-10-18 00:34:41 +02:00
menus.txt Update some a11y tests 2017-10-11 20:09:21 -05:00
menus.ui Fix unittests 2016-10-18 00:34:41 +02:00
meson.build Fix test environments 2017-10-18 17:30:20 +02:00
messagedialog.txt
messagedialog.ui
misc.c
misc.test.in Test suite cosmetics 2017-10-18 17:30:20 +02:00
mnemonic.txt a11y tests: Update test results 2017-03-31 14:04:59 -04:00
mnemonic.ui
notebook.txt
notebook.ui
paned.txt a11y tests: Update test results 2017-03-31 14:04:59 -04:00
paned.ui
pickers.txt Update a11y test output 2017-05-22 21:42:18 -04:00
pickers.ui
placeholder-text.txt
placeholder-text.ui box: Remove fill child property 2017-04-25 20:30:37 +02:00
progress.txt
progress.ui
range.txt Update some a11y tests 2017-10-11 20:09:21 -05:00
range.ui
README
scale-drawvalue.txt Update a11y test output 2016-03-05 10:40:06 -05:00
scale-drawvalue.ui
spinner.txt
spinner.ui
stack.txt a11y tests: Update expected output 2016-06-01 14:18:46 -04:00
stack.ui
statusbar.txt Update expected output of statusbar a11y test 2017-10-18 17:30:20 +02:00
statusbar.ui
testfocus.c Remove gtk_widget_show_all 2017-01-20 21:37:04 +01:00
tests.test.in Test suite cosmetics 2017-10-18 17:30:20 +02:00
text.c
text.test.in Test suite cosmetics 2017-10-18 17:30:20 +02:00
text.txt
text.ui
tooltips.txt Update a11y test output 2016-03-05 10:40:06 -05:00
tooltips.ui
tree-performance.c
tree-relationships.c
tree.test.in Test suite cosmetics 2017-10-18 17:30:20 +02:00
tree.txt
tree.ui
util.c
util.test.in Test suite cosmetics 2017-10-18 17:30:20 +02:00
value.c
value.test.in Test suite cosmetics 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.