Ket Shah, the problem is that without seeing your application, it would be hard for us to tell you how to convert those to descriptive programming.
The code you provided is clearly referencing the object repository. Within the object repository, each of those logical names has one or more description properties - you can see them by opening your object repository and looking at the specific object.
But there is no way for any of us to know what those description properties are.
That WinButton might use "nativeclass" and "text" as description properties. The text is probably "Yes". The nativeclass might be something as simple as "Button". I'm just guessing here - only you can know for sure.
So, if my guesses are right, the DP for that button would be:
Note: that is only the DP for the button (and it might be wrong - I used the nativeclass of a button in my OR, but it's not a web application - no idea if your nativeclass would be the same). You might also want to do the DP for the browser and the dialog as well.
I hope that gets you started.
"The last 10% of any software project will take 90% of the budgeted time. The first 90% will take the other 90%"
you are using two property/value pairs in DP. I am very new to DP..as a matter of fact used it very rarely only when the occassion demanded it and always used one property/value pair..ex... WinButton("text:=yes")
Is it a better practice to use more than one? Thanks Blake [img]/images/graemlins/smile.gif[/img]