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

first we will smoke testing and after that sanity testing 
is done.
Smoke testing:in this we check only that bild is uploaded 
or not.
sanity testing:we also do functional testing.