Ad Topics

Models

  • 'Waterfall' Testing
  • 'V-Model' Testing
  • 'Iterative' Testing
  • 'Agile' Testing

Methods

Types

  • Smoke Testing
  • Installation Testing
  • Functional Testing
  • Look & Feel Testing
  • Usability Testing
  • Compatibility Testing
  • Performance Testing
  • Security Testing
  • Conformance Testing
  • Regression Testing

Artifacts

Metrics

Tools

  • Test Management Tools
  • Defect Tracking Tools
  • Functional Testing Tools
  • Performance Testing Tools
  • Unit Testing Tools

Resources

The list of articles above is all we got at this moment. Over the weekends, we are working on the remaining content. Join/Follow/Subscribe us if you want to be notified of our updates.

Verification vs Validation

Verification and Validation: Definition, Differences, Details:

The terms ‘Verification‘ and ‘Validation‘ are frequently used in the software testing world but the meaning of those terms are mostly vague and debatable. You will encounter (or have encountered) all kinds of usage and interpretations of those terms, and it is our humble attempt here to distinguish between them as clearly as possible.

Criteria Verification Validation
Definition The process of evaluating work-products (not the actual final product) of a development phase to determine whether they meet the specified requirements for that phase. The process of evaluating software during or at the end of the development process to determine whether it satisfies specified business requirements.
Objective To ensure that the product is being built according to the requirements and design specifications. In other words, to ensure that work products meet their specified requirements. To ensure that the product actually meets the user’s needs, and that the specifications were correct in the first place. In other words, to demonstrate that the product fulfills its intended use when placed in its intended environment.
Question Are we building the product right? Are we building the right product?
Evaluation Items Plans, Requirement Specs, Design Specs, Code, Test Cases The actual product/software.
Activities
  • Reviews
  • Walkthroughs
  • Inspections
  • Testing

It is entirely possible that a product passes when verified but fails when validated. This can happen when, say, a product is built as per the specifications but the specifications themselves fail to address the user’s needs.

  • Trust but Verify.
  • Verify but also Validate.

2 comments to Verification vs Validation

  • Mohit

    content was good and helpful also

  • Paul Nanouk

    I agree with everything but the questions: you have them reversed. Testing does not answer “are we building the right product” since you are actually testing the actual product. Therefore, you cannot ask at that time, “are we building the right product,” since it is “ipso facto.” You can only answer the question, “did we correctly build the product?” as you have the product/service under test. Verification is where you ask the question about the specifications, designs, etc BEFORE you build the product/service, “are we building the right product/service?” Once built, the product is in existence, “it is too late to ask if you built the right product.” IMHO.
    Paul Nanouk

Leave a Reply

  

  

  


4 − one =

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>