Testing a Product

A test team can be confident that a product has been adequately tested because

1) The test team performed all required up-front planning
2) The Test Plan was approved by all relevant stakeholders
3) All requirements have been covered in test cases
4) All test cases have been executed
5) The test results have met our exit criteria

Testing of the product is said to be completed only when following conditions are met:

1) All the test cases in test suite are executed
2) All the results are mapped and documented with exit conditions
3) If any difference exist between actual and expected results, then it has been informed to the client and feedback from client based on these issues are documented.
4) Product is subjected to load/stress testing
5) The response time of the product is analyzed & documented and verfied with expected response time.
6) A test plan is framed based on future enhancement of the product ( as a proactive step)

When you are working on a project on services side, you are in fact working on an application. so the exit criteria (when to know to stop testing) is no different for a "product." So all the criteria that applies to normal "services" project will apply to product application. Just because the company will sell applications does not mean the testing is entirely different. As a QA/tester you are only concerned about the type of application.