Validation Process

After getting tired of searching in google for product validation document, i decided to create my own. There are enough substance for software product testing but not for electronic Products.
In validation, process followed is the key to sucessful validation. So I am starting with validation process(common to software and electronic products).
The document will focuss on blackbox and grey box testing.
Process Flow Diagram:


The roles defined above vary from organisation to organisation. Products with less complexity are validated with Team lead and testers where team leads perform the role of test managers.
Complex projects involve test project manager.

Test Planning
The test manager should analyse test scope & requirements and prepare a broad test plan.
The test manager is expected to be domain expert and should contribute in static testing.

The test plan should define

• How the testing will be done.
• Who will do it.
• What will be tested.
• How long it will take (although this may vary, depending upon resource availability).
• What the test coverage will be, i.e. what quality level is required.

The test can be

I. Firmware test (black/grey box).

II.Stress tests.

III.Environmental testing.

IV)Performance of electronic design modules

V) Usability testing.

I.Firmware testing:

i) Module testing that enables to find bugs at early stage

ii) Integration test

iii) Smoke test/sanity test that determines whether full test cycle can be run on the product

iv) Regression test

v) Final Dry Run(FDR) test.

These process may have some variations depending upon the product.