gtk2/tests/a11y/hello-world.txt

window1
  "window"
  index: 0
  state: enabled resizable sensitive showing visible
  toolkit: gail
  <AtkComponent>
  layer: window
  alpha: 1
  button1
    "push button"
    parent: window1
    index: 0
    name: Hello World!
    state: enabled focusable sensitive showing visible
    toolkit: gail
    <AtkComponent>
    layer: widget
    alpha: 1
    <AtkText>
    text: Hello World!
    character count: 12
    caret offset: 0
    default attributes: left-margin: 0
                        right-margin: 0
                        indent: 0
                        invisible: false
                        editable: false
                        pixels-above-lines: 0
                        pixels-below-lines: 0
                        pixels-inside-wrap: 0
                        bg-full-height: 0
                        scale: 1
                        rise: 0
                        underline: none
                        strikethrough: false
                        bg-stipple: false
                        fg-stipple: false
                        fg-color: <omitted>
                        bg-color: <omitted>
                        wrap-mode: word
                        justification: left
                        size: <omitted>
                        weight: <omitted>
                        family-name: <omitted>
                        stretch: <omitted>
                        variant: <omitted>
                        style: <omitted>
                        language: <omitted>
                        direction: <omitted>
    <AtkImage>
    image size: -1 x -1
    image description: (null)
    <AtkAction>
    action 0 name: click
    action 1 name: press
    action 2 name: release
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`
			`"window"`
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`
			`state: enabled resizable sensitive showing visible`
			`toolkit: gail`
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: window`
			`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!`
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			`state: enabled focusable sensitive showing visible`
			`toolkit: gail`
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			`<AtkText>`
Dump AtkText properties too ...would be nice if these actually _were_ properties. Update the expected output to match. 2011-06-19 18:56:05 +00:00			`text: Hello World!`
More text properties 2011-06-19 19:22:08 +00:00			`character count: 12`
Dump AtkText properties too ...would be nice if these actually _were_ properties. Update the expected output to match. 2011-06-19 18:56:05 +00:00			`caret offset: 0`
tests: Add line breaks when dumping text attributes This improves diff readability a lot when attributes differ. 2011-06-20 12:14:00 +00:00			`default attributes: left-margin: 0`
			`right-margin: 0`
			`indent: 0`
			`invisible: false`
			`editable: false`
			`pixels-above-lines: 0`
			`pixels-below-lines: 0`
			`pixels-inside-wrap: 0`
			`bg-full-height: 0`
			`scale: 1`
			`rise: 0`
			`underline: none`
			`strikethrough: false`
			`bg-stipple: false`
			`fg-stipple: false`
tests: omit fg-color and bg-color values from attributes They depend on the environment, too. 2011-06-20 12:22:49 +00:00			`fg-color: <omitted>`
			`bg-color: <omitted>`
tests: Add line breaks when dumping text attributes This improves diff readability a lot when attributes differ. 2011-06-20 12:14:00 +00:00			`wrap-mode: word`
			`justification: left`
			`size: <omitted>`
			`weight: <omitted>`
			`family-name: <omitted>`
			`stretch: <omitted>`
			`variant: <omitted>`
			`style: <omitted>`
			`language: <omitted>`
			`direction: <omitted>`
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`
			`action 1 name: press`
			`action 2 name: release`