Windows showing as dlg and not a shell
I feel this is probably a problem from the java side of things (and/ or SWT) but I'm hoping someone can help me understand. I have a software written in java with lots of shells on shells. Recent...
Forum Discussion
There are some points that you have to consider with test automation
1) GUI automation is most suite to regression test with a matured product(which means GUI are almost frozen)
2) When you map objects (name mapping) think about future changes. So carefully map stable high level useable objects,
rest of them call in runtime using find Child or similar methods
3) try to call one mapping only in one place(Say Script A). All relevant tests refer script A. that is what you call framework
4) Test complete speeder than most applications. Think about timing. when TC trying to operate application object, if it is not fully formed, there will be infamous error "Object not found"
Perhaps I didn't explain my question well enough.
I'm mostly wondering if other java automators have seen this problem. Dialogs don't allow you to do the same things a Shell allows you to do and I'm wondering if anyone else has randomly had their software change windows in this way.
My name mapping is not compeltely messed up, I can just no longer customize NEW windows I want to use. They are all listed under "dlg" and are not identified as unique windows. All previous tests are functioning just fine.
I mostly use keyword tests at this point in time because we were making it as simple as possible for a few select support people to create tests as needed. When we implement this regression suite into our automated release process, I will convert them all to script and use the framework suggestion.
