Verification and Validation

 

Explain differences between Verification and Validation with examples from your current project?

Ans: Verification means Testing Quality of requirement document, Quality of design, Code review….before AUT is ready is called Verification. Verification purpose is proactively from beginning of the project Ba, Dev, test involve in Requirements Analysis to identify given requirements are

“Testable requirements or not”,

 

Example from my current project for ecommerce web application

Fnp.com one rule says Max limit mandatory for ordering products and Products Max limit change based on date of delivery and Product Category…In this requirement

BA forget to mentions Product Category wise Max limit to purchase …These requirements assigned to me , Immediately  I raised queries 1. How many Product categories available?

          2. Product category wise max and min limits available? 

Without getting this info I can’t create test cases…so BA clarified then only this requirement

Considered for design.

Early testing or proactive testing or verification or review during initial phased of the project helps in

Preventing mistakes associated with requirement before these mistakes enters next phase.

That’s why we encourage BA, Dev, test to perform requirement review, design review, code review before compilation of code before execution of code.

Once Application is ready…even though we have tried to prevent mistakes still few defects might

Have entered to software so to find defects we perform validation or execution or dynamic testing.

During validation we provide inputs to Actual software and we validate “Are we getting correct output”

Any deviation in output we consider as defect in the software and we report defect to developer.

 

Example: Max limit for cakes category for delivery Date Dec 31 was 3 per account….earlier it was unlimited only for that date and category I have tested  as per rule and we found It is not working ..

So immediately we reported defect and developer corrected it .

 

Coming to differences:

1.      Verification starts before code development from the beginning of the project whereas Validation starts after code compilation.

2.      Verification objective is prevention of mistakes, errors, bugs entering to software Validation objective is finding defects through execution of Software.

3.      Verification activities are Requirement review, design review,

 Code review whereas validation activities are Unit testing, Integration testing, System testing, User Acceptance Testing (UAT testing)

4.      Verification is proactive testing for prevention whereas validation is reactive testing for detection of the defects.

5.      Testing must starts before code development with verification activities once code is ready we do validation to find defects.

 

To Summarize Testing= Verification activities + Validation Activities