Actually I don't know, Because I put fake experience. I 
never did these things. So, how can I tell you about those?
-----Fun-----
To trace out whether the process is going on without any 
interruption. By reviewing, we can get an insight what is 
the status of the project, what are different things, are 
there any obstacles while completing our project. If any 
problems are arised, workarounds can be implemented.

For all types of files in testing that is library files,
script files (.vbs files), log files (result windows),
object repository files (.tsr files), and recovery files
have separate folders in companies database named as "Test
Base."  Like this, software developers have database storage
in company called as "Soft Base."

J. Sambasivarao
9948280248
jampani_sivarao@yahoo.com

In some configuration management tool like VSS

Scripts in QTP will be stored in  .mts extenstion

Actions can be reusable or non reusable but functions are
always reusable..

Actions are like every event (like press button, mouse 
click )

 Functions are Functionality of an Application like
    Insert scenario, Update Scenario, Delete Scenario
    like that...

The class whose instances are to be serialized 
should implement an interface Serializable. Then pass the 
instances to the ObjectOutputStream which is connected to a 
FileOutputStream. This will save the object to a file...
         When an object ios serialized, all the included 
objects are also serialized along with the original object.

Serialization is a marker interface to tell the jvm that 
the class extending Serializable interface wants to persist 
or write its state over the output stream. All the 
variables other than transient type can only be persisted.

Generally for recovery scenarios I dont use functions. I 
rather use the keyword or mouse operation which is much 
simple.
However based on the question -  In order to use the 
defined function (RegisterUserFunc) we need to register the 
function such that all the objects/methods descrivbed  in 
the functions are understood.

I may be wrong too...

1. Go to TOOLS -> Recovery scenario manager.
2. Select the trigger event that caused the error(it may be 
a pop up window).
3. Identify the name of the window with the help of 
POINTING HAND.
4. Choose the operation type : KEYBOARD OR MOUSE OPERATION.
5. Select the action with the help of POINTING HAND.(e.g. 
Click on OK button to close the window.)
6. If you want to add another action then keep "Add another 
recovery scenario" check box selected else de select it.
7. In the "Post recovery test run option" select "Proceed 
to next test iteration"
8. Give scenario name & description & click on finish 
button.
9. Save the scenario.
10. Go to TEST->SETTINGS->SCENARIO TAB....and add the saved 
scenario.
11. Click on APPLY & OK button......now your test run 
smoothly.

see... generally we can handle those pop up window exeptions
by writing If then statement and using exist method.

for example...

If window("skdhja").dialog("text:=fahda").exist then
window("skdhja").dialog("text:=fahda").winbutton("text:=OK(or)Cancel").click
window("akdhja").close
else
<write remaining script here..
end if
like this we can handle Pop Up window exceptions...try to
get control on script rather than QTP tool..

If any queries..
nanda.dreddy@gmail.com

If you select “Function call" option we have to select the 
file containing our library functions.
then we will have two radio buttons
1.Select function
2.Define new function
if we select the 'select function' radio button then we 
have to use the following syntax
Function (Object)
‘ recovery information and code goes here
End Function 

Example:
‘ Close the About Notepad window.
Function AboutWindow(Object)
Object.Highlight
Object.Close
End Function 


if we choose 'Define new function' then Create a new 
function by specifying a unique name for it, and defining 
the function in the Function Name box according to the 
displayed function prototype. The new function is added to 
the library file you selected.

Create different userids and passwords in Datatable.
then..
Dialog("Login").Winedit("Userid:").set Datatable
("columnname",dtGlobalSheet)
Dialog("Login").Winedit("Password:").set Datatable
("columnname",dtGlobalSheet)
Dialog("Login").WinButton("OK").Click

We write different userids and passwords in Datatable.
then..
Dialog("Login").Winedit("Userid:").set Datatable.value
("userid",dtGlobalSheet)
Dialog("Login").Winedit("Password:").set Datatable.value
("password",dtGlobalSheet)
Dialog("Login").WinButton("OK").Click

Here "Userid" and "Password" are the Column names of the 
datatable

OK so I was thinking I would just record the login part 
(username and password) and then log off, but how do I make 
this a reuseable action for all the other scripts that were 
already created? I want all the other scripts that use this 
same userid and password to call this action so how do I do 
that?

---Create Instances of Object---
set x= CreateObject(Scripting.FileSystemObject)
set y=x.CreateTextFile("c:\a.xls",true)
x.writeline "welcome"
Used for creating xls/notepad/doc instances, with which we 
can store data into it.

the above should be 
y.writeline "welcome" instead of x.writeline

The FileSystem Object is the object that is used to 
manipulate the filesystem in Active Server. Moving files, 
opening and reading text files, and looking at drive space 
are a few of the many functions of the FileSystem Object.  
The FileSystem Object actually contains five objects: the 
main Filesystem object, the Drive object, the Folder 
object, the File object, and the TextStream object.

Quality control describes the directed use of testing to 
measure the achievement of a specified standard. Quality 
control is a formal (as in structured, not as in wearing-a-
tuxedo fancy) use of testing. Quality control is a superset 
of testing, although it often used synonymously with 
testing. Roughly, you test to see if something is broken, 
and with quality control you set limits that say, in 
effect, if this particular stuff is broken then whatever 
you're testing fails.

Quality control is like testing the End product i..e wht 
ever we have built is right or not as per the customers 
requirments or not.

Quality Control involves independant testing and validation 
of the end product before it is dispatched to the 
customer.After the testing of the product has been 
completed by the testing team , an independant tester from 
the quality team will perform random testing on the product.
This testing is done inorder to confirm that the product 
meets the customer requirements.
After Quality Control testing the product is certified by 
the Quality Head, assuring the customer that the end 
product meets the requirements and also that the end 
product adheres to the Quality Standards of the 
organization.

Quality control is to ensure the right product that is 
designed to meet the customer requirements..

Quality Control is a set of activities designed to evaluate 
a working product.

This is a General question asked in all  the  Interviews

You start testing once you are clear with the requirements 
amd the documnets are ready

You stop testing depending on the following factors

I am continuing The answer You stop testing when
stop testing these are the main factors.

1. Reduce in defects.
2. Increase in Testing cost.
3. Delivary dates.

We need to check that

1) Whether all the Bugs which were Assigned to developers 
have been fixed .
2) All the documents pertaining to testing have been 
prepared.
3) all the bugs which were in Previous releases have been 
retested .

when bug rate falls below a certian level
 when deadlines are reached
 when all the testcases are passed with a certian rate of 
passed testcases
 when testing budget is depleted
  and teamleader says to stop testing
   in all these cases we stop testing

we will start testing when we have software requirement 
specification, enough testcases,  and build

we will stop testing 
i)when all major seviority bugs are solved 
ii)when budget is going to complete
iii)when project time s going to complete

why no hv mentioned abt the Test Plan -Exit Criteria.
while Test Plan is done we use to mention the Exit Criteria 
Right,we shd Indentify that Exit Criteria also to Stop 
Testing know?

When to start:

 1)When build is ready
 2)Environment is setup
 3)Test cases are executed
 4)Resource should be ready

when to stop:

1)Based on no. of test cases executed
2)No. of defect-reach certain low level
3)Based on release date

The following are the list of items that are required to be 
Start the QA Phase.
.Complete Unit/ Integration Testing.
.QA Test Environment SetUp Completed.
.QA Test Plan Preparation Completed and approved.
.QA Test Cases Preparation Completed and approved.

The following are the list of items that are required to be 
Stop the QA Phase.
. All Planned System Test cases have been executed.
. No Critical Bugs.
. Defect log should be updated.
. QA Test Summary Report Completed.
. QA Sign off.

TRM:

Requirement ID
Description
TestData
TestCase ID

Project Name/Requirement/Sub 
Requirement/Description/HLD/LLD/Coding/Unit 
Test/Integration Test/System Test/Automation/User 
Acceptance/Installation and Reference guide/Maintenance 
guide/Remark

any doubts on this carify to 
Selvam, Test Lead.
9840258140

go to requirement tab 
go to view 
click numeration 
this generates ID or numbers to the test cases and 
requirements

that numeration is not same as requirement id n testcase 
id,that r just for clear view.......

real time people please answer to this question......thanx 
in advance

both are configuration management tools. we maintaiall 
scripts in the form of frame work in the tool. total ur 
frame work store in the confi tools with version numbers 
when ever u want u can open

s, we have 1 feature in QTP. i give u the navigation which 
will make non-reusable actuon to reusable action.
  record ur reqd operation->step menu -> action properties-
>select reusable action->click ok

In the Action properties Dialog box at the botton you will 
find a checkbox,written reusable action, one need to select 
that checkbox to make the action reusable.

Using page check points u can check no of links,broken 
kinks in a page.

By using childobject method 


Set linkDescObj=description.Create()
linkDescObj("micclass").value="Link"
Set Links=browser("Gmail: Email from Google").Page("Gmail - 
Inbox -srikrishna").ChildObjects(linkDescObj)
NoOfLinks=Links.count()
msgbox NoOfLinks
For i=0 to NoOfLinks-1
linkName=Links(i).getROProperty("name") 
msgbox linkName
Next

Choose Standard check points either from Active screen or from keyword view, a Object selection properties box will appear from there select page (upper most) and click on OK.