I think the answer will be

1- write the query to create the table.
2-insert the values into the table.
3-retrive the values from that table

If i m wrong then posty the correct answer

The Question is not clear.what is write testcase for SQL 
table?..for which table...what are the fields in the 
table..?Before writting we should be clear about the 
requirements...

column definitions
data ranges for values 
referential integrity - primary / foreign keys

verify to create the table
verify  to create the constraints
verify to create the char, varchar2, number......
verify to insert the data into table
verify to update the data into table
verify to delete the data into table
verify to select the data into table
verify to sort the data into table
.
.
.
.
Nag
9989093551

i think release note is the deployement document, which is
the guidelines those are given to the testing team to deploy
the s/w .

I agree with Pradyumna, but a slight modification for that. 
Release notes is given to client along with the build when 
it is ready for the deployment. Release notes consists of 
the deployment details and also the known limitations of 
the build, if there are any critical errors that are still 
not resolved and build is to be released, then those are 
also mentioned in the release notes. Hope this clarifies 
your query.

Kumar.rnv@gmail.com
Broadridge.

For a tester release note is a document in which the dev 
team has mentioned the specification of the release,
The known issues, the critetias, the limitations of that 
build.

and for client release note is the document in which all 
the specification of the application are mentioned.
the precondition, the test data type the show stoppers the 
known bugs are mentioned.

Release note is notyhing but a software release note 
deployed to the testing department whioch consists of .....
built path,
built information
version no 
release manager.
build information data
release date
MOdule name

Hi, Release note is nothing but a document which will be 
given From PM or dev team, when the Build is Ready in Stage 
( May be Ready for Testing or May be Ready for the client 
to do opperation).

The Release notes will be given to the Tester when the 
Biuld is Ready for Testing. The document consists of the 
Modules to be Tested and the Developer Names Assigned to 
the Modules, Refereance documents path, Build path and 
Credentials, Type of Testing to be Performed (if required) 
and Known Issues (if any).

The Release Notes will be given to the Client when the 
Build is ready for client to work on. It may not nessasary 
for Tester to know abt this document. It consists of the 
Modules, Refereance documents path, Build path and 
Credentials and Known Issues if any and may be consisting 
some other information also.

1.In Sanity testing we r just checking the look & fill of 
the GUI according to the client specification or according 
to the mockup screen.
In sanity testing we r not checkin any business logics not 
the flow, we r just checkin the look & fill.
EX: Take the yahoomail login page, there is a logo in top 
middle of the page, in right pane there r 2text boxes are 
there, one check boxis there and one login button is there.
in sanity check we will check wheather all these fields r 
there or not.according to client spec. doc the text colour, 
the text size & the text style is ok or not we will check.

But in smoke testing we r checking all the functionalities, 
wheather the application is working fine or not.
smoke testing is an adhoc type testing.

2.Sorry I dont know how the blind people
can identify GUI of the form.

Dear Suvendu
you interchanged the information at first instance we
perform smoke to check the stability of the build, found
stable we then go for sanity testing, to check the complete
functionalities of the build as per the SRS.

Smoke and Sanity testing are the same. To test that the 
build is migrated successfully and all the needed code is 
migrated successfully. This is followed by system testing.

Hey Mona
I am sorry to say but your answer is wrong. As I mentioned 
in my earlier post smoke testing is done immediately after 
build is received from development team to check the 
stability of the build. Stability means to check whetehr 
all the forms, buttons, links, etc are working. once it is 
done we go for sanity testing i.e to check complete 
functionalities of the module as per the requirement 
mentoned in the SRS and we execute our test cases.

Thanks
Kishore
kishoresharma1@gmail.com

Test case for e-mail
1-go to the addressbar of IE and then write thw url of the
email.
2.when the page comes then input valid value in the field E-mail
3-input valid value to the field password
3click on submit button

After clicking on run button , we will get one screen with 
named as 'Run', in that if we want we can use the default 
location otherwise wecan select any folder to save the log 
files.

1. While doing execution, unexpectedly some of the 
applications are down or environment unavailability.

2. Data issues i.e.,proper data has not been provided for 
executing the test case.

3. Some of the application links are not working which are 
provided in environment sheet.

Yes we can associate the library files with out 
using "Executefile" statement. But you should use AOM method

Example:
Dim qApp 
Dim qLibs 
 
Set qApp = CreateObject("QuickTest.Application") 
qApp.Launch  
qApp.Visible = True 
 
qApp.Open "E:\Test1", False, False ' Open a test 

Set qLibs = qtApp.Test.Settings.Resources.Libraries ' Get 
the libraries collection object 
   qLibs.Add "C:\Utilities.vbs", 1 ' Add the library to the 
collection 

qApp.Test.Save 
qApp.Quit 
Set qLibs = Nothing 
Set qApp = Nothing  

First of all you have to create Quick Test object after 
that open the test with the help of Quick Test Object and 
also create Libraries object after that you can add ".vbs" 
files.

Set fileSysObject=createobject("Scripting.FileSystemObject")
Set
linksFileName=fileSysObject.opentextfile("D:\samplelinkfile.txt",2,true)

Set linkDescObj=description.Create
linkDescObj("micclass").value="Link"
Set noOfLinks=browser("Browser").Page("Yahoo!
India").ChildObjects(linkDescObj)

For i=0 to noOfLinks.count-1
	linkName=noOfLinks(i).getROProperty("name")
	linksFileName.writeline(linkName)
Next
linksFileName.close
Set fileSysObject=nothing

Here i am retrieving all the links in Yahoo home page and
writing the link names in a text files.

If you wish to verify the number of links a web page, you
can use "Standard Checkpoint".
Click on Record button ->Insert Menu -> Check point
->Standard Checkpoint -> Click on any place in the page and
select the page in the Hirarchy and observe the number of
links property/value. If the total number of links are
increased or decreased, then it will show the differences.

Hi Uday,

   its nice answer. keep it.

and also u can use html tag instead of micclass..

like

linkDescObj("html tag").value="A"

  it will perform same functionality.

Yes u have to mention "On Error Resume Next" statement in 
the beginning of the script

Generally, when QTP encounters a run time error during
running the scripts, it shows the error message in a pop up
window and the script execution will stops.

If you wish to display your own error message and you wish
to continue with the script, then we will use Err object.

We have to use "On Error Resume Next" statement before the
runtime error is returned.

The general usage of the Err object is like:

On Error Resume Next

dim fileSysObj
fileSysObj=createobject("Scripting.FileSystemObject")

fileSysObj.folderexists("c:\uday") 'assume this folder
doesnt exist
'QTP shows the error message here itself and stops
execution, if "On Error Resume Next" statement doesnt exists


If Err.Number <>0 then
 msgbox("Here it prints") 'Because of Err object we can give
our own error message
end if

Dim a(10) is array declared 

if we want to change the size of array it should be 
declared with redin as below

ReDim A(10)

to preserve the contents of array we need to use preerve 
keyword as below

ReDim Preserve A(10)

above line is Answer ,,,, by declaring array as above it 
will preserve the valus

Function doesn't return more than one value.  

if you want to get more than one result, we can write 
function for that.  After u will get the value u have to 
split the value.

Example:

Function AddSub(a, b)
    som = a + b
    subt = a - b
    AddSub = som&"/"&subt
End Function

this function returns only one value. But it's having two 
results(i.e Addition and subtraction of two no.s).

After u will get this value. u have to split that one for  
two results by using split function here delimeter is "/".

like this we can add more than one result to the return 
variable(in this example AddSub is the return variable).

Another way to handle more than one return value is using
arrays and also use global variables.

In descriptive progmmaning the objeect's information should
be avialable,
desc. prog takes less tim to execute bcz the object's
information is avialable in the script,but it is very
difficult to mentain(update).but through object repository
we can easily write the script bcz the object's info is
avaialable in that OR.

i think this is the answer

and also..

    writing the script will take more time when writing in 
DP. maintance of the script will be difficult. 
        if some of the object properties are changing from 
build to build u have to update same in script also. but if 
u are using Object Repository u can update those property 
values in Object Repository. its one time change.or u can 
handle this in object repository with reguler expression. 

   like this we can say many examples.

if any queries:
nanda.dreddy@gmail.com

Actions are more specific to tool Example QTP

Functions are generic and part of programing language.

Actions in QTP are used to divide the test into different 
logical units .

Within actions we can write functions .

but witin functions we cant use actions

we call functions in actions .

Major Differences:

Functions: Function returns only one value.  it doesn't has 
Object repository.

Actions:  Actions has Object repository.  It returns more 
than one value (i.e Output parameters).  We can declare 
more than one Output parameter. 

we can call Function in any Actions in QTP test. But Action 
is not like that we have to mention that as reusable action 
in Action Properties. 

we can store Functions in .VBS file. but Action we cann't 
store like this way.