This depends on company

My organisation testing process starts from preparation of 
test plan. my lead will prepare the test plan. Once it is 
reviewed and approved we are going to execute the test 
cases like identifying the test scenarios, designing the 
test cases, executing the test cases where we are going to 
perform different testings based on the customer 
specifications. After successful completion of all test 
cases we will release the build for UAT. Once the end-user 
accepted, release the build for production. Perform 
Installation testing. The developed software to be 
installed into the customer site.

Rajendra ... 
everyone knows that it depends on company but the question 
process followed in ur company.dont give these kind of 
answers in interview.they will through u out of the company.
All the best ..

Rajendra,
U r an idiot.. r u really wrking in any organisation as 
test engineer..

In my organization we will be having KT's on that 
particular project by onsite team by daily basis on 
coference call's and we will be getting BRD's we will go 
through that and depending on the BRD doc's and usecases we 
will be finding test scenario's.
On the other part high level management(PM, TL) they will 
start preparing Test plan.
when the Test plan review and sign off done by client the 
other side we will be finishing for Test scenario's.
These scenarios's will be reviewed by our track lead and 
depending on his comments we will do modifications.
Note: all these doc's will be uploaded in VSS.

Then after RTM (Requirement Tracebility matrix) is done for 
Test scenarios'. Here we will check whether we have covered 
all the scenarios for the requirements(every requirement 
will be having unique ID (for ex: i.e: 2.1.3))this is 
called maping the requirements.

Then after we start writting test cases. after TL review 
and signoff will start executing test cases when the buil 
is deployed in stage environment (there 3 environments: dev-
 for developers, stage- for testing, production- client 
side.). 

In execution stage will be doing smoke testing, system 
testing. when ever we find bug's will log through Quality 
center and post that bug to developer's. when the fix is 
done on that bug it will reflect in the next build. first 
will do Re-testing. if the bug is really fixed then put the 
status as closed if not re-open it and resend it to 
developer.

Then will do Regression Testing(means Rigourously test) the 
application thoroughly to ensure that fix doesn't have any 
impact on the other functionalities.

when all the defects get closed and 100% execution is 
completed then UAT (User Acceptance Test )is done and get 
signoff from business and approval to deploy it in 
production environment (client side). Thus our job is 
finished. after sucessful go live. will be have SESSION'S 
LEARNED among the team members (including PM, TL, Team). 
where will discuss how many bugs we found, which type of 
bugs(priority, severity), how should we take care in 
further release and how quickly we need finish designing 
test cases and execution. and how to deal with development 
and business on phones or thru mails.

all these things will be discussed in sessions learned.

Thanks
ASHISH