gtk2/testsuite/a11y/hello-world.txt

window1
  "frame"
  index: 0
  state: enabled resizable sensitive showing visible
  toolkit: gtk
  <AtkComponent>
  layer: widget
  alpha: 1
  unnamed-GtkContainerAccessible-0
    "panel"
    parent: window1
    state: enabled sensitive showing visible
    toolkit: gtk
    <AtkComponent>
    layer: widget
    alpha: 1
  button1
    "push button"
    parent: window1
    index: 0
    name: Hello World!
    state: enabled focusable focused sensitive showing visible
    toolkit: gtk
    <AtkComponent>
    layer: widget
    alpha: 1
    <AtkImage>
    image size: -1 x -1
    image description: (null)
    <AtkAction>
    action 0 name: click
    action 0 description: Clicks the button
tests: Add first shot at an accessibility dump tool The tool works like this: ./accessibility-dump [FILE ...] If no files are given, all files with the extension ".ui" in the current directory are taken. For every file "test.ui", the following steps are performed: 1) test.ui is loaded using GtkBuilder 2) The accessible for the window is loaded 3) The information of accessible is converted into a string using a syntax defined in this test file 4) The generated string is diffed with the file "test.txt" 5) If the diff is empty, the test is a success, if not, the test fails. 6) The diff is output when the test runner is run with --verbose So to add a test named "test", create a file called "test.ui", put it into this directory. Then create the expected output file "test.txt", put it into this directory too. You can create the initial version of this file by invoking "./accessibility-dump --verbose test.ui". The output will contain the expected text and can be copy/pasted into the text file. 2011-06-19 04:11:38 +00:00			`window1`
testsuite: Make a11y tests use regular windows 2020-02-14 18:25:23 +00:00			`"frame"`
Dump more accessibility data This commit adds dumping of parents, attributes and states. The expected dump output has been adjusted to match. 2011-06-19 15:32:43 +00:00			`index: 0`
a11y tests: Ignore "active" flag on toplevel All the a11y tests were failing for me with a window state diff like this: - state: active enabled resizable sensitive showing visible + state: enabled resizable sensitive showing visible I guess the windows in the CI always gets the focus, but not when I run it here. Generally focus seems asynchronous and hard to rely on so I just made the test ignore the active state on toplevels. 2020-02-04 14:01:48 +00:00			`state: enabled resizable sensitive showing visible`
Change the toolkit attribute from gail to gtk Update test results to match. 2011-07-02 22:44:12 +00:00			`toolkit: gtk`
Dump AtkComponent properties Note that the spatial aspects of AtkComponent are all dependent on fonts and other environmental factors, thus we only dump the little bits outside of that. 2011-06-19 23:51:15 +00:00			`<AtkComponent>`
Make a11y testsuite pass 2020-02-18 00:44:07 +00:00			`layer: widget`
Dump AtkComponent properties Note that the spatial aspects of AtkComponent are all dependent on fonts and other environmental factors, thus we only dump the little bits outside of that. 2011-06-19 23:51:15 +00:00			`alpha: 1`
testsuite: Make a11y tests use regular windows 2020-02-14 18:25:23 +00:00			`unnamed-GtkContainerAccessible-0`
			`"panel"`
			`parent: window1`
			`state: enabled sensitive showing visible`
			`toolkit: gtk`
			`<AtkComponent>`
			`layer: widget`
			`alpha: 1`
tests: Add first shot at an accessibility dump tool The tool works like this: ./accessibility-dump [FILE ...] If no files are given, all files with the extension ".ui" in the current directory are taken. For every file "test.ui", the following steps are performed: 1) test.ui is loaded using GtkBuilder 2) The accessible for the window is loaded 3) The information of accessible is converted into a string using a syntax defined in this test file 4) The generated string is diffed with the file "test.txt" 5) If the diff is empty, the test is a success, if not, the test fails. 6) The diff is output when the test runner is run with --verbose So to add a test named "test", create a file called "test.ui", put it into this directory. Then create the expected output file "test.txt", put it into this directory too. You can create the initial version of this file by invoking "./accessibility-dump --verbose test.ui". The output will contain the expected text and can be copy/pasted into the text file. 2011-06-19 04:11:38 +00:00			`button1`
			`"push button"`
Dump more accessibility data This commit adds dumping of parents, attributes and states. The expected dump output has been adjusted to match. 2011-06-19 15:32:43 +00:00			`parent: window1`
			`index: 0`
tests: Add first shot at an accessibility dump tool The tool works like this: ./accessibility-dump [FILE ...] If no files are given, all files with the extension ".ui" in the current directory are taken. For every file "test.ui", the following steps are performed: 1) test.ui is loaded using GtkBuilder 2) The accessible for the window is loaded 3) The information of accessible is converted into a string using a syntax defined in this test file 4) The generated string is diffed with the file "test.txt" 5) If the diff is empty, the test is a success, if not, the test fails. 6) The diff is output when the test runner is run with --verbose So to add a test named "test", create a file called "test.ui", put it into this directory. Then create the expected output file "test.txt", put it into this directory too. You can create the initial version of this file by invoking "./accessibility-dump --verbose test.ui". The output will contain the expected text and can be copy/pasted into the text file. 2011-06-19 04:11:38 +00:00			`name: Hello World!`
a11y tests: Update expected results The changes here are all related to initial focus. 2019-03-17 01:49:24 +00:00			`state: enabled focusable focused sensitive showing visible`
Change the toolkit attribute from gail to gtk Update test results to match. 2011-07-02 22:44:12 +00:00			`toolkit: gtk`
Dump AtkComponent properties Note that the spatial aspects of AtkComponent are all dependent on fonts and other environmental factors, thus we only dump the little bits outside of that. 2011-06-19 23:51:15 +00:00			`<AtkComponent>`
			`layer: widget`
			`alpha: 1`
Make the dumped output a bit more readable By adding sections for each interface. 2011-06-19 23:28:47 +00:00			`<AtkImage>`
Dump AtkImage properties too Update expected output to match. 2011-06-19 19:30:01 +00:00			`image size: -1 x -1`
			`image description: (null)`
Make the dumped output a bit more readable By adding sections for each interface. 2011-06-19 23:28:47 +00:00			`<AtkAction>`
Dump AtkAction properties Adjust expected output to match. 2011-06-19 20:53:16 +00:00			`action 0 name: click`
Update a11y test results to match The newly added descriptions show up in the accessible information dumps. 2013-02-04 05:55:43 +00:00			`action 0 description: Clicks the button`