In terms of testing both terms looks same and generally people get confused when interviewer ask them to differentiate. These terms are totally different and the people who is leaning testing should know about the difference because this is the common question asked in the interviews.
Verification: Verification is the process to evaluate the documents which will be use in the development of the software. These documents are Requirement Specification, Design Documents, Database Table Design, ER Diagram, Test cases, Tractability Matrices. In verification we review only these documents so these process called the static process. The objective of this process to determine that the software is built as per the design and the requirement documents.
Verification process does not include the execution of the code. Verification uses method like inspection, review, walkthroughs etc.
This process is need because if any error occur in any document then that error will be increase in the software development then it is too costly to fix it in development phase. This is the low level exercise of bug fixes and done before the validation.
This process is need because if any error occur in any document then that error will be increase in the software development then it is too costly to fix it in development phase. This is the low level exercise of bug fixes and done before the validation.
Validation: Validation is the process to evaluate the software during and the development phase to ensure that the software meeting the client requirement or not. The objective of the validation to ensure that software meet's the user need and the specification were correct in the first phase.
In validation we done all type of testing like Functional Testing, Smoke Testing, Regression Testing etc so in this process we need to execute the code so this validation process called Dynamic Testing.
Validation process occur after the verification process.
Comments
Post a Comment