Rao

• Dec 3rd, 2006

 

In Idle Scenario we will update the script as per the new changes and run the test. This will work out only when u know the AUT is not going to have too many changes in objects. esle we need to go for keyword driven approach by keeping all the objects in the datasheet and updating as and when it requires 

jayant_gajbhiye

 Profile Answers by jayant_gajbhiye Questions by jayant_gajbhiye

• Dec 4th, 2006

 

Thanxxxxxxxxx . but can u again explain me what exactly solution, updating script means how to update from "OK"  to " SUBMIT" button name.

scottso

• Dec 6th, 2006

 

Quick question as part of your basic testing you should be able to predict all outcomes including in this case the "name" of a given button.

Changes to the UI are by themselves a level of  testing... lets call it "layer one" base and defaults. You need to arrange with devlopment a line of communication and share with them the importance of being notified of significant gui changes.  Share with them why from a technical perspective. Going forward run a baic level one base state test and any GUI mismatches should be handled as a standard defect. If you elec not to do this or somethign similar you will end upspendign a great deal of time maintaning or worst writing some Kludge that violates the integrity of the test script

best of luck

harika

• Dec 10th, 2006

 

hai

We can run the script by changing physical discription of the 'ok' button .This can be done by using regular expression.We can change the name of the 'OK' button name as 'submit' by modifying the physical discription of the button in GUI map editor. After changing the name we have to the winrunner to learn the physical discription of the objects of the new window by using Run Wizard.

This what we called the 'Maintaining the test scripts'.

jayant_gajbhiye

 Profile Answers by jayant_gajbhiye Questions by jayant_gajbhiye

• Dec 11th, 2006

 

Thax harika,

changing butoon name  is main issue, why should  we go for regular expression?

As per u r answer we  r doing GUI maping - to  map object to standard class .

then again  we change logical name definatly  but  if both button are push button  what physical proparty we have to modified ?

plz answer...

harika

• Dec 11th, 2006

 

yes

We have to change the logical name of the push button to 'submit' by editing the physical properties of that perticulat button with the help of GUI map editor.Here we are only changing the logical name of the button ,but we are not changing other physical properties.

If you want more information regarding this refer 'Maitaining the test script' chapter in Winrunner tutorial.

srinivas.o

• Dec 13th, 2006

 

Hi,

u can use descriptive programming for that....if u have clear details about that u can send me mail...

Bye

Srinivas

Kaivalya

• Dec 19th, 2006

 

Hi,

Only property will get changed that is I think "Text" so you can change that property in object repository. QTP will recognize this object..

Thanks and Regards,

Kaivalya

kusuma

• Dec 28th, 2006

 

hi,

Any how "ok" button, "submit"button are same just name is changing ok to submit in 1 build to another build . it is  just a matter of changing logical name.

jayant

• Dec 29th, 2006

 

Hello  frds ,

Very simple answer go to gui map editor  in physical proparty change in label name from OK to SUBMIT, Now u r script definatly work...... 

chandra

• Dec 29th, 2006

 

Hi guys,

There are many ways of identifying a GUI object.

Scenario 1: If the name keeps channging but the location is same. You can identify the object by location.

Scenario 2: If the location keeps changing you can identify the GUI object by its MSHandle.

Even if this doesn't work then change some of the optional properties to obligatory properties.

cheers,

Chandra

Narsing

• Mar 21st, 2007

 

Method 1: Give a common logical name for both 'Ok' and 'Submit;

 and modify as regular expression instead of 'Ok' replace with ![a-z] like that regular expression in the physical description.

Then use common logical use in your script where and all u want to work with push button.

Method 2: Give descriptive program instead of logical name (ok/submit),

here no need to change any thing in the physical description.

But use descriptive program:
{ class : push button, class index ; 34 }

In the above description i give for example 34 but u should what u have, right,

If u have any concerns send a mail to me.

Bye:
Narasingarao.D
Sr. Test Engineer.