pls tell me clearly abt thisthe link which u had given is 
not proper and giving errors

Project based is nothing but client requirements.
product based is nothing but market requirements.
Ex.striching shirt is a project based and ready made shirt 
is product based.

PROJECT:Project is developed for client&requirements are
given by clients

PRODUCT:product is developed for market& requirements are
gathering by conducting market survey.

Project based testing: means test engineers will will test
the application for one time. Its one time testing only. In
project based testing we are going to develop the
application for another company purpose and they only will use.

Product based testing: Its repeatitive. Take ex: of
Microsoft windows
win 95/98/ now we r going to vista. all the past features
shoudld tested with also the new enhancements. its
repetitive task. In product based company we r developing
the application for another company and that application
will be used by the endusers.

if i am wrong ..post ur openion.

regards
krishna
arnikrishnaprasad1@gmail.com

product Testing is nothing but after preparing the 
application we will contact to the clients.if client need 
any changes then we will change it according to 
requirements.
But in project based means client only give all the 
customer requirements.According their requirements we will 
test the application.

To know the difference first should know what is project 
and product.

Project - Company will develop project based on client 
requirments. This project will be used by client. Client is 
the owner of this project. 

Product - Company will develop product based on market 
requirments. This product will be used by public. Company 
is the owner for this product. Company has to face profit 
or loss.

Testing - Based on the client requirments & market 
requirments testing will happen.

Every one saying difference between product and project. in 
the testing prospective what would be the difference?

Product based teting involves boththe Quality assurance and 
Quality control but the project baced testing is mainly the 
quality control ...we gather the general requirements for 
the product from the competitive companies product,the 
clients survey and then start making the product with 
definite processs to be followed but as the requirement for 
the project are clear ans so the time frame.so the Testing 
is done as one time task afer whole software is 
inpmlemented....
suggestions are welcome

Objective:
-- Projects based company: Which has been developed for
client only, so whose comes under the client they can only use 
-- Product based company : which has been developed  for all
global , so every one can able to use 

Testing:
-- Testing and it is process based on client in projects 
-- Requirements,Testing and process based on client which
was tested every release to client 

-- Once we had prepared test case and it is process, we can
use multiple time   with Existing  format

-- Let me know if any comments

project based testing:requirements r given by client n 
companies work according to them,client participate 
actively in different phases of software development.
In project based companies client also involved in testing .
 
product based testing: requirements r not fixed it will 
change according to end user.Most of the product based 
companies follow iterative model . testing stategies n 
methodologies r deffer according to their need .

Project Testing: 
1. Generally project testing done based on Client requirements
2. Scope of security testing is limited
3. User acceptance testing is required
4. Will have only one release.
5. unsolved Bugs will be fixed in maintenance stage

Product testing:
1. Testing done based on over all requirements and current
market standards.
2. More security testing is required
3. No User acceptance testing 
4. More compatibility testing will performed.
5. Will have no of releases.
6. unsolved Bugs will fixed in next releases

Project Testing: Here Client provides all requiements, and 
in testng you need to make your testcases on the basis of  
requirements given by client, less chance of customize the 
requirements. There is one final release.
Product Testing:- Here test team can also suggest for 
changes in requiements on the basis of usability. More pre-
releases before final release, so means more testing work.  
May be more than one client with their unique requirements. 
so Need to more emphasize on testing.