> For the complete documentation index, see [llms.txt](https://qatesting.gitbook.io/qa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://qatesting.gitbook.io/qa/manual-testing/overview/v-and-v.md).

# V & V

Verification and Validation

<div data-full-width="true"><figure><img src="https://qtxasset.com/quartz/qcloud4/media/image/Sensors%20Magazine-1510201630/TOP_OF_PAGE.JPG/TOP_OF_PAGE.JPG?VersionId=Kxd6Y0UM167EVhk7yIOBFabFLUCR9Q9f" alt=""><figcaption></figcaption></figure></div>

**Verification** focuses on whether we are "*building the product right*" by ensuring it meets <mark style="background-color:yellow;">technical requirements and specs</mark>. 🛂&#x20;

**Validation** focuses on whether we are "*building the right product*" by ensuring it <mark style="background-color:orange;">fulfills the intended purpose and customer needs</mark>. 🅰️

## Examples at different levels

**At a basic level:**

✅Verification: Check all buttons work

➕Validation: Check sign-up form accepts valid inputs

**At a medium level:**

✅Verification: Test features meet specs by testing edge cases

➕Validation: Test search returns relevant results

**At an advanced level:**

✅Verification: Perform API tests and load tests

➕Validation: Do end-to-end testing and usability testing with actual users

## **How are verification and validation testing different?**

Verification 🛂 is more systematic and rigorous, focusing on technical defects. It can be automated.

Validation 🅰️ is more open-ended, subjective, and involves users. It focuses on usability issues. ✏️

🛂 **Verification** focuses more on:

❌Finding technical defects

🔧Ensuring product meets specifications

✅Building the product correctly

**🅰️ Validation** focuses more on:

❌Finding usability issues

🎯Ensuring product meets user needs

✅ Building the right product

🛂 **Verification**:&#x20;

📝 More systematic

✏️ Checks parts in isolation&#x20;

⚙️ Often automated

**🅰️ Validation**:

🧠 More subjective

💭 Involves end users' perspective&#x20;

👥 Focuses on full product experience

🛂 Verification tests the "*how*":

How the product was built.

🅰️ Validation tests the "*what*":

What the product actually does for users.

<table data-full-width="true"><thead><tr><th>Verification</th><th>Validation</th></tr></thead><tbody><tr><td>Evaluates the intermediary products to check whether it meets the specific requirements of the particular phase.</td><td>Evaluates the final product to check whether it meets the business needs.</td></tr><tr><td>Checks whether the product is built as per the specified requirement and design specification.</td><td>It determines whether the software is fit for use and satisfies the business needs.</td></tr><tr><td>Checks “Are we building the product right”?</td><td>Checks “Are we building the right product”?</td></tr><tr><td>This is done without executing the software.</td><td>Is done with executing the software.</td></tr><tr><td>Involves all the static testing techniques.</td><td>Includes all the dynamic testing techniques.</td></tr><tr><td>Examples include reviews, inspection, and walk-through.</td><td>Example includes all types of testing like smoke, regression, functional, systems and UAT.</td></tr></tbody></table>