3: Product and Project Software

Product and Project Software

So what’s the product and project software?

PRODUCT
Product development is done assuming a wide range of customers and their needs. This type of development involves customers from all domains and collecting requirements from many different environments.
Software Product is not done for a single client and it is released as a product of the company.

PROJECT

Software Project is done for specific clients of your company. For this some of the testing may be done at client's side.

Project Development is done by focusing a particular customer's need, gathering data from his environment and bringing out a valid set of information that will help as a pillar to development process.

Test Environment

Design | Development | Staging | Production

Staging It is the phase where the production is made operational and the errors are identified in the SUT (System under Test), Application under Test (AUT)

Test Team Hierarchy

Any idea about the test team hierarchy?

Testing principles

Principle 1: Testing shows presence of defects Testing can show that defects are present, but cannot prove that there are no defects. Testing reduces the probability of undiscovered defects remaining in the software but, even if no defects are found, it is not a proof of correctness.

Principle 2: Exhaustive testing Testing everything (all combinations of is impossible inputs and
preconditions) is not feasible except for trivial cases. Instead of exhaustive testing, we use risks and priorities to focus testing efforts.

Principle 3: Early testing Testing activities should start as early as possible in the software or system development life cycle and should be focused on defined objectives.

Principle 4: Defect clustering A small number of modules contain most of the defects discovered during pre-release testing or show the most operational failures.

Principle 5: Pesticide paradox If the same tests are repeated over and over again, eventually the same set of test cases will no longer find any new bugs. To overcome this 'pesticide paradox', the test cases need to be regularly reviewed and revised, and new and different tests need to be written to exercise different parts of the software or system to potentially find more defects.

Principle 6: Testing is context Testing is done differently in different dependent contexts. For example, safety-critical software is tested differently from an e-commerce site.

Principle 7: Absence-of-errors Finding and fixing defects does not help if fallacy the system built is unusable and does not fulfill the users' needs and expectations.