AuroraMiddleware/gtk
1
0
Fork 1
mirror of https://gitlab.gnome.org/GNOME/gtk.git synced 2024-09-21 06:20:29 +00:00
Code Issues Projects Releases Wiki Activity
9a7e69a990
gtk/testsuite/a11y
History
Matthias Clasen 7d35351c7a Update expected results
2014-11-23 18:53:06 -05:00
..
state Skip focus tests in make check 2014-08-10 07:08:39 -04:00
a11ychildren.test.in Fight deprecation warnings in test 2014-06-28 00:41:26 -04:00
a11yderive.test.in Fight deprecation warnings in test 2014-06-28 00:41:26 -04:00
a11ymisc.test.in Add a test for popover accessible parents 2014-07-30 23:14:49 +02:00
a11ytests.test.in Fight deprecation warnings in test 2014-06-28 00:41:26 -04:00
a11ytext.test.in Fight deprecation warnings in test 2014-06-28 00:41:26 -04:00
a11ytree.test.in Fight deprecation warnings in test 2014-06-28 00:41:26 -04:00
a11yutil.test.in Fight deprecation warnings in test 2014-06-28 00:41:26 -04:00
a11yvalue.test.in Fight deprecation warnings in test 2014-06-28 00:41:26 -04:00
about.txt tests/a11y/about: Fix expected text 2014-10-22 21:17:37 +01: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 a11y tests: Add a test for GtkActionBar 2014-02-22 12:31:18 -05:00
assistant.txt Update expected output for assistant a11y test 2014-04-10 15:50:51 -07:00
assistant.ui
buttons.txt Update expected output in a11y tests for buttons 2014-08-16 13:01:50 -04:00
buttons.ui a11y tests: add image buttons 2014-02-22 12:31:18 -05:00
calendar.txt
calendar.ui
children.c Don't use stock APIs in the testsuite 2013-06-24 19:53:08 -04:00
colorchooser.txt Update expected output for a11y tests 2014-07-21 19:21:02 -04:00
colorchooser.ui GtkColorSwatch: Set an accessible role 2014-01-04 18:52:46 -05:00
combos.txt GtkLabelAccessible: Implement AtkHypertext 2014-01-04 10:54:03 -05:00
combos.ui
derive.c
entries.txt Adapt to spinbutton changes 2014-08-14 19:39:07 -04:00
entries.ui
expander.txt GtkLabelAccessible: Implement AtkHypertext 2014-01-04 10:54:03 -05:00
expander.ui
headerbar.txt More a11y test updates 2013-09-16 23:29:42 -04:00
headerbar.ui Add GtkHeaderBar to the a11y tests 2013-06-30 22:33:12 -04:00
hello-world.txt
hello-world.ui
iconview.txt
iconview.ui
infobar.txt GtkInfoBar: Set a more accurate accessible role 2014-01-04 17:44:14 -05:00
infobar.ui
label.txt Update expected results of a11y tests 2014-10-27 20:03:51 -04:00
label.ui a11y tests: Add a test for multi-link labels 2014-01-04 10:54:03 -05:00
link.txt Update expected results of a11y tests 2014-10-27 20:03:51 -04:00
link.ui Small improvement to GtkLinkButton a11y 2013-09-21 20:51:21 -04:00
listbox.txt GtkLabelAccessible: Implement AtkHypertext 2014-01-04 10:54:03 -05:00
listbox.ui Add a GtkListBoxRow accessible 2013-09-21 20:51:22 -04:00
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
menu.ui Don't use stock APIs in the testsuite 2013-06-24 19:53:08 -04:00
menubutton2.txt Update output of a11y tests 2014-04-28 22:55:44 -04:00
menubutton2.ui a11y tests: Add a test for menubuttons with model 2014-02-22 12:31:19 -05:00
menubutton3.txt Update output of a11y tests 2014-04-28 22:55:44 -04:00
menubutton3.ui a11y tests: Add a tests for menu buttons with popovers 2014-02-22 12:51:11 -05:00
menubutton.txt Improve menubutton a11y 2013-12-20 13:31:08 -05:00
menubutton.ui Add a menubutton to the a11y tests 2013-12-20 13:31:08 -05:00
menus.txt Adjust the a11y testsuite to match expected output 2013-06-25 12:39:19 -04:00
menus.ui Adjust the a11y testsuite to match expected output 2013-06-25 12:39:19 -04:00
messagedialog.txt Update output of a11y tests 2014-04-28 22:55:44 -04:00
messagedialog.ui
misc.c Add a test for popover accessible parents 2014-07-30 23:14:49 +02:00
mnemonic.txt GtkLabelAccessible: Implement AtkHypertext 2014-01-04 10:54:03 -05:00
mnemonic.ui
notebook.txt Adjust the a11y testsuite to match expected output 2013-06-25 12:39:19 -04:00
notebook.ui Don't use stock APIs in the testsuite 2013-06-24 19:53:08 -04:00
paned.txt a11y tests: Update expected output 2014-05-02 20:53:02 -04: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 testsuite/a11y: Don't check minimum increment 2013-07-24 02:54:25 +01:00
progress.ui
range.txt testsuite/a11y: Don't check minimum increment 2013-07-24 02:54:25 +01:00
range.ui
README
scale-drawvalue.txt testsuite/a11y: Don't check minimum increment 2013-07-24 02:54:25 +01:00
scale-drawvalue.ui
spinner.txt Update expected results for some a11y tests 2013-10-25 16:39:49 -04:00
spinner.ui
stack.txt Update expected output in a11y tests for buttons 2014-08-16 13:01:50 -04:00
stack.ui Add GtkStack and GtkStackSwitcher to the a11y tests 2013-06-30 22:33:12 -04:00
statusbar.txt
statusbar.ui
testfocus.c
text.c testsuite: Add deprecation guards for ATK deprecations 2013-09-16 15:41:15 +02:00
text.txt
text.ui
tooltips.txt Implement support for ATK_STATE_HAS_TOOLTIP 2014-10-22 22:55:13 -04: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 Update expected output for tree.ui 2014-01-14 13:15:19 -05:00
tree.ui Add some treeview a11y tests 2014-01-13 23:51:26 -05:00
util.c
value.c Remove redundant checks for NULL 2014-10-02 19:06:03 +02:00

README 

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.