| || |
Product vs Project Testing
What are the differences between a project testing and product testing, from a testers perspective. I want to know the differences right from stage1 till the delivery stage, and even there after, if any. I request you to provide detailed answer.
Re: Product vs Project Testing
Dear astral body,
I am sure that if you read your own question you could come up with the answer in no time. One of the hallmarks of a good tester is to analyze what the components of a specification are. Products, vs. projects?
For all projects related to a product you look at further refinement and additional functionality that needs to be added to the test base. Typical products evolve in stages, and feedback from the user community results in new functionality being added over time. In that case you simply expand on the test base you developed for earlier (less functionality rich) versions.
For projects that cross product boundaries (such as bundled projects) each subset of the project is a product related subset, and as such it will have product specific test requirements. From a project perspective you will have several sets of independent requirements due to the bundling of essentially independent products.