Have a look at the "xwindow data" post. I don't think you can get that kind of info without wrapping the widget library, or linking into the application.
I'm no expert, so I could be wrong. We got a copy of X-runner a while back, and for it to do anything except bitmap compares, it needed to sit in between your app and the x libs.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, I read the xwindow data post and that clears things up. If I understand correctly, it means X11::GUITest can drive a gui but not "test" to see if the results match a benchmark though.
How does one go about writing gui tests if the properties are not available? For example, consider an input box that is used as a search to subset the items in a listbox. After sending keys to the input box, how does one assess whether or not the listbox contains the expected items?
Thanks.
Jack
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That's what I thought, but I wanted to make sure. We won't be able to use X11::GUITest within our automation framework. Bitmap and text compares work in some cases, but we really need more.
Thanks for chatting with me.
Jack
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm trying to identify properties of a window. For example whether a checkbox is checked or not. Is this possible and if so how is this done?
Ideally, I'd like to be able to specify a windowid and get a list of properties and their values.
Thanks.
Jack
Have a look at the "xwindow data" post. I don't think you can get that kind of info without wrapping the widget library, or linking into the application.
I'm no expert, so I could be wrong. We got a copy of X-runner a while back, and for it to do anything except bitmap compares, it needed to sit in between your app and the x libs.
Thanks, I read the xwindow data post and that clears things up. If I understand correctly, it means X11::GUITest can drive a gui but not "test" to see if the results match a benchmark though.
How does one go about writing gui tests if the properties are not available? For example, consider an input box that is used as a search to subset the items in a listbox. After sending keys to the input box, how does one assess whether or not the listbox contains the expected items?
Thanks.
Jack
your understanding = my understanding.
Blind as a bat I think.
Even finding the list box is tricky if you have forms that are layout managed rather than fixed position.
If you can highlight something and paste is somewhere you might be able to compare text.
Can you do a bitmap compare?
That's what I thought, but I wanted to make sure. We won't be able to use X11::GUITest within our automation framework. Bitmap and text compares work in some cases, but we really need more.
Thanks for chatting with me.
Jack
Support could surely be built into a tool like X11::GUITest, but with a single developer it is unlikely to ever happen. :-(