gtk2/testsuite/a11y
Alexander Larsson a3be0ec5f0 Don't use xsettings or xft defaults in testsuite
This adds a GDK_DEBUG=default-settings flag which disables reads
from xsettings and Xft resources, and enables this for the testsuite.

This is one less way to get different testresults depending on the
environment. In particular, it was failing the css tests for me
due to getting the wrong font size because i have a different dpi.
2020-02-03 15:11:35 +01:00
..
state a11y testsuite: Stop using gtk_widget_show_now 2018-02-04 23:23:15 +01:00
about.txt testsuite/a11y/about: Fix exp. output per 31066a69 2019-06-14 18:05:06 +01:00
about.ui
accessibile-name.txt
accessibility-dump.c A11y: Add support for AtkTableCell 2018-12-14 19:25:27 +00:00
accessible-name.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
accessible-name.ui
actionbar.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
actionbar.ui Update a11y tests 2019-05-07 02:21:30 +00:00
assistant.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
assistant.ui a11y tests: Update assistant ui file 2019-02-08 09:51:45 -05:00
buttons.txt Update a11y tests 2019-05-07 02:21:30 +00:00
buttons.ui testsuite/a11y: Update GtkGrid definitions in UI files 2019-04-05 00:24:49 +01:00
calendar.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
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 Update a11y tests 2019-05-07 02:21:30 +00:00
colorchooser.ui
combos.txt Update a11y tests 2019-05-07 02:21:30 +00: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 a11y tests 2019-05-07 02:21:30 +00:00
entries.ui Fix a few css/a11y test cases 2016-10-16 18:17:21 +02:00
expander.txt Update a11y tests 2019-05-07 02:21:30 +00:00
expander.ui
headerbar.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
headerbar.ui Update a11y tests 2019-05-07 02:21:30 +00:00
hello-world.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
hello-world.ui Fix unittests 2016-10-18 00:34:41 +02:00
iconview.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
iconview.ui
infobar.txt Update a11y tests 2019-05-07 02:21:30 +00:00
infobar.ui
label-static.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
label-static.ui gtkbuilder: add accessibility role declaration 2018-03-19 18:07:06 +01:00
label.txt Update a11y tests 2019-05-07 02:21:30 +00:00
label.ui
link.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
link.ui
listbox.txt Update a11y tests 2019-05-07 02:21:30 +00:00
listbox.ui
lockbutton.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
lockbutton.ui
menubutton2.txt testsuite: Fix some a11y output 2019-05-28 20:25:15 +00:00
menubutton2.ui
menubutton3.txt testsuite: Fix some a11y output 2019-05-28 20:25:15 +00:00
menubutton3.ui
menubutton.txt Adapt tests 2019-05-18 13:06:33 +00:00
menubutton.ui testsuite: Remove menu tests 2019-12-29 20:31:57 -05:00
meson.build Don't use xsettings or xft defaults in testsuite 2020-02-03 15:11:35 +01:00
messagedialog.txt Update a11y tests 2019-05-07 02:21:30 +00:00
messagedialog.ui
misc.c testsuite: Stop using g_test_bug() 2019-05-12 17:28:18 +02:00
misc.test.in Test suite cosmetics 2017-10-18 17:30:20 +02:00
mnemonic.txt Update a11y tests 2019-05-07 02:21:30 +00:00
mnemonic.ui
notebook.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
notebook.ui a11y tests: Update ui files 2019-02-21 00:31:17 -05:00
paned.txt Update a11y tests 2019-05-07 02:21:30 +00:00
paned.ui Convert ui files 2019-03-27 21:48:12 -04:00
pickers.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
pickers.ui testsuite/a11y: Update GtkGrid definitions in UI files 2019-04-05 00:24:49 +01:00
placeholder-text.txt Update a11y tests 2019-05-07 02:21:30 +00:00
placeholder-text.ui a11y tests: Clean up the placeholder-text test 2019-03-16 22:46:34 -04:00
progress.txt Update expected output of a11y tests 2016-03-04 23:51:39 -05:00
progress.ui
range.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
range.ui testsuite/a11y: Update GtkGrid definitions in UI files 2019-04-05 00:24:49 +01:00
README
scale-drawvalue.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
scale-drawvalue.ui
spinner.txt Update expected output of a11y tests 2016-03-04 23:51:39 -05:00
spinner.ui
stack.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
stack.ui a11y tests: Update stack ui file 2019-02-08 09:51:45 -05:00
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 testsuite: Stop using g_test_bug() 2019-05-12 17:28:18 +02:00
text.test.in Test suite cosmetics 2017-10-18 17:30:20 +02:00
text.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
text.ui
tooltips.txt a11y tests: Update expected results 2019-03-16 21:49:24 -04:00
tooltips.ui
tree-performance.c
tree-relationships.c Replace gdk_threads_add_idle* with g_idle_add() 2018-02-03 12:06:58 +01:00
tree.test.in Test suite cosmetics 2017-10-18 17:30:20 +02:00
tree.txt Update a11y tests 2019-05-07 02:21:30 +00:00
tree.ui
util.c
util.test.in Test suite cosmetics 2017-10-18 17:30:20 +02:00
value.c testsuite: Stop using g_test_bug() 2019-05-12 17:28:18 +02:00
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.