| || |
Low Level Temporary Method Needed
I know that I need some API tools to correctly communicate with an application under test.
QTP records nothing, but it is putting some things in the OR if I use the spy or OR or use dp with awful properties such as x,y.
I need a way to show what it would look like if QTP was recognizing object correctly for a demo.
Of all of the horrible choices, would you go with x,y co-ordinates in the OR, Low level recording, analog, virtual objects?
Its just for a temporary workaround to show what it will look like once I get the Infragistics and API tools installed and working so I can do this correctly.
I would probably go with virtual objects because it will be the most similar to the final product you're hoping to create. It will, of course, take a bit of time up front to create the objects. That's assuming you'll be doing the demo on the same machine you're doing the development on. I'd be skeptical of moving around a lot with any of the options you've got.
Agreed, map some virtual objects.
And presuming you are presenting this to development. Show them what the object spy is capable of detecting for identification properties.
Maybe show it side by side against a public website or some other app installed on your machine.
Last edited by NoUse4aName; 02-05-2014 at 06:14 AM.
Dennis and NoUse.*,
I will try the Virtual Objects.