Exforsys

Online Training

about winrunner

This is a discussion on about winrunner within the Testing Tutorials forums, part of the Articles and Tutorials category; When we try to learn the objects of windows inbuilt calculator in winrunner, it does not learn those objects as ...


Go Back   Exforsys > Articles and Tutorials > Testing Tutorials

Register FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 03-24-2005, 05:16 AM
Junior Member
 
Join Date: Feb 2005
Posts: 17
mangalsachin2002
about winrunner

When we try to learn the objects of windows inbuilt calculator in winrunner, it does not learn those objects as standard class objects. Then we have to create virtual objects for those. But why does winrunner (in some systems) accept these objects as standard class and does not need to create virtual objects of these even when u close winrunner and start it again.

thanks group!
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #2 (permalink)  
Old 03-27-2005, 01:00 AM
Junior Member
 
Join Date: Mar 2005
Posts: 12
mallakishore is on a distinguished road
about virtual object to standard class

· There are two ways of creating GUI Map files
1)Global GUI map file.
2)GUI map file per test.
If you are going to write the script in Global GUI map file mode then the GUI file will automatically load into the script when ever you are running the script. If you create virtual objects as standard class object that physical description will be stored in the temporary GUI map file. If you save that script and tries to run the script after reopening of WinRunner it will load the GUI map file automatically and the physical description will not change and WInRunner will recognize the object as the standard class.
But in GUI map file per test mode we have to load the GUI map file before running the script. Hence If you load the GUI map file and configure the virtual objects as standard class object then WinRunner will recognize it as a standard class and if you unload the GUI map file with out saving and tries to run the script again then WinRunner will recognize the object as virtual object only, But if you save that GUI map file then it will recognize that Virtual object as standard class ,even if you run the script after closing WinRunner and start again.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
  #3 (permalink)  
Old 03-27-2005, 06:10 AM
Junior Member
 
Join Date: Feb 2005
Posts: 17
mangalsachin2002
hi mallakishore!

Dear Mallakishore,

There are two things:
1. See u r telling that gui global file loads automatically as u try to run an already saved test. And in case of gui pertest mode u will have to load the gui file before running an already saved test script. Actually it is otherway round. In global mode u will have to load gui file in order to run an already saved test script and in case of pertest mode u need not to load gui map file in order to run an already saved testscript.

2. You did not understand my question. I wanted to ask that normally when u make some object a virtual object, and close winrunner the winrunner does not accept the object as a virtual object when u restart winrunner unless you had saved the old gui file. But in some systems winrunner recognises some objects as standard class objects irrespective of the fact that u had saved the gui file or not before shutting down winrunner. So my question is why does this happen.
Digg this Post!Add Post to del.icio.usBookmark Post in TechnoratiFurl this Post!
Reply With Quote
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -4. The time now is 02:48 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.1.0
Copyright 2004 - 2007 Exforsys Inc. All rights reserved.