ravikumar

• Oct 29th, 2006

 

hi,

suppose in some of the cases wr does't identify objects,in that situation we can handle through Vowizard,by assigning standard class properties to that and giving some name we can make WR try to recognise that object.i think its correct.....otherwise plz give me answer.........k bye.........

ravikumar:chinnu.sep14@gmail.com

sudhakar2068

 Profile 

• Oct 31st, 2006

 

 The use of virtual object wizard in winrunner to recognize non recognized objects forcebly test engineers are using this option.

sudhakar kolla,

My email:kollasudhakar2005@yahoo.co.in.

My number:09819859346

charles

• Dec 6th, 2006

 

hi,

 seldom winrunner couldnot recognized some advanced technology objects in the projects.in this time v should prefer virtual object  wizard option in winrunner.Henceforth Tool can recognize those types of objects. 

hari

• Dec 10th, 2006

 

than q ,can u give me an example for type objects which are not identified by winrunner and the objects which  forcebully to use virtual object wizard to find them?

Nilesh W

• Jan 11th, 2007

 

Hi,

Simple Example for Virtual Object Wizard:(VOW)

Take an example of win's Calculator. Record it and observe that are you able to get the script or object. i.e. whether that scipt is in a readable format? Can you able to understand that what operation/calculation you have performored. No. So to recoginize that objects we can use VOW. -[Virual - temperory object]

Thanks

Nilesh

raghavendra

• Jan 22nd, 2007

 

hi,

Some time application has some features and the operations performed on those features will not be scripted appropriately.Inother words these features r not recognised by WR as OBJECTS since they r not really objects.To over come this we have a mechanism called Virtual object configuration . This configuration is successfully done using a facility called "Virtual Object Wizard"

mathan_vel

 Profile Answers by mathan_vel Questions by mathan_vel

• Sep 14th, 2009

 

Application may contain objects that behave like standard objects but
are not recognized by QuickTest. You can define these objects as virtual
objects and map them to standard classes, such as a button or a check box.
QuickTest emulates the user’s action on the virtual object during the run
session. In the test results, the virtual object is displayed as though it is a
standard class object.

QuickTest does not support virtual objects for analog or low-level
recording.