Thanks for the suggestion.
I have an Object checkpoint, which finds this new window, recognizes it and the checkpoint passes. I also added an If Object Exists step.
However, it is still shown as an unexpected window in the log, and further actions all fail.
During playback it syas, 'Waiting until the window is activated' & then 'Waiting until the overlapped window becomes visible'. This is where the failures occur.
I have not use object checkpoint so i cannot help with what it does, i do everything vbscript coding.
if you can take a picture of the Name Mapping of the window it might shed some light.
Do becareful if you are uing Keyword testing, some application will generate an index value to identify what the window's current position is inside a collection of the same type of window.
and if that is the case when using IF Object exist .. it will likely name map the index, so the next time it tries to find the window it won't be able.
What I normally do:
Run the application manually and bring up the window i want to interact with.
open up a test keyword and use 'IF object exist' or 'FInd Object' , which will generate the Name Mapping
Go into the name mapping and find what Test Complete was able to pull out of, drill down the treeview until i get to teh end of it which you should be able to use highlight option and it should blink on the window you are working with.
If that is the case, then find a property in that name and make sure its uniqueness and the value to the property that does not chagne.
an example:
Property: "NativeCLRObject.Name"
Value: "FileGrid"
then script your test to find that particular value from the processes of yoru application
one you get teh object you can interact with that object, or findChild to get other items in that object.. ie buttons
objNonModal.FindChild("wnCaption","&OK").Click
again i dont know if this will help as i dont knwo what your app or test looks like nor the object's property you are dealing with. Just suggestion on how I deal with any non-modal windows within our app
I am using keyword testing. I was able to get to the window in question by finally using some keyboard actions (tab) and then changing the identification points slightly. It was a window within a window.
Thanks a lot for your suggestions.
Look into "Script Extension" - extending the keyword test to match your application environment.
- edit -
i m actually trying to extend the property check to match our application., and if it works well i can expand it into other area of the software that i can jsut drag/drop and select what i want it to check.
it'll look something like this.
Parent Group
Object
Property
PropertyValue
