Test Verification vs Validation in Website Testing | LambdaTest

Image for post
Image for post

Verification and Validation, both are important testing activities that collectively define all the mandatory testing activities a tester along with the entire team needs to perform when you are developing a website for either your organization or for the client. For testers, especially those who are new in the industry, understanding the difference between test verification vs validation in website testing may seem to be a bit complex. Because both involve checking whether the website is being developed in the right manner. This is also why I have observed a lot of ambiguity among the teams working on a project.

This article is my attempt to help you clarify the difference between test verification vs validation in website testing. Now, let’s take a deep dive in the following article where we shall get a detailed understanding of what is verification and validation testing. I will be explaining the difference using a cross browser testing scenarios.

Before we get started I would want to highlight the key distinguishment between test verification vs validation. Verification testing involves checking whether the team is following the right approach, it could be related to design, SRS document etc., while Validation testing involves checking whether the finished product satisfies all the needs of the customer. So, like whether it supports all the required browsers and devices.

What Is Test Verification?

Verification testing is the process of finding out whether the work products concluded during the development phase meets the requirements specified by the client. In short, it checks whether the work is going on the right track.

The steps required to start verification testing can be understood by taking a look at the following document.

Image for post
Image for post

Importance Of Test Verification

  • Suppose you are building a single page web application. Verification testing is all about checking whether the webpage has all the components or supports all the browsers mentioned in the SRS. If any anomaly is found in the web application during verification testing it will create a critical bug in the next phases of testing. Hence, test verification is carried out to ensure that the number of bugs is reduced in the later phases.
  • Test verification is the only answer to the very basic question of “Are you developing the website correctly?”
  • In each phase of the development life cycle, verification testing demonstrates completeness, correctness, and consistency of the web application.
  • Verifying the product in the very beginning makes you understand it better. It even reduces the chance of bug occurrence during development as well as validation testing.
  • Reduces the chance of failure and helps in creating a product as per the requirements of the customer.

What Is Test Validation?

Validation testing takes place after the development as well as verification testing is completed. All the popular and mandatory testing procedures like unit testing, system testing, acceptance and integration testing, etc fall under the category of validation testing. The following diagram can be referred to in order to understand how it works.

Image for post
Image for post

Importance of Test Validation

  • Defects which are missed during verification testing can be caught as bugs during validation testing. For example, supporting a minor CSS feature in multiple browsers. This can only be tested once validation testing is carried out.
  • Validation testing is done in multiple phases like load testing, acceptance testing, unit testing, etc. Thus the web application goes through all the mandatory testing phase.
  • Validation testing ensures that after development, the finished product satisfies all the requirements of the customer.
  • Let’s suppose your website is supposed to run perfectly on a specific browser in a specific operating system. However, the concept got misunderstood during verification testing. When the feature is implemented and validation testing is carried out, the tester will be able to understand the functional difference between the actual and expected result.

Digging Deep Into Differences Between The Two

Test Verification vs Validation — What is the Aim?

Image for post
Image for post
src:(https://www.sitepoint.com/usability-testing-goals-knowing/)

Test Verification vs Validation — What it Involves?

Validation, on the other hand, is completely dynamic and checks the quality of the product in multiple environments, both manual and automated testing after development is completed.

Test Verification vs Validation — Difference in Methods

Validation, however, involves the execution of the code along with unit testing and also the execution of the test cases to find out if the code works perfectly in satisfying the requirements of the end user. Since most of the common testing phases like the unit, functional or regression testing can be done with the use of automated scripts, there is plenty of scope for automation in validation testing.

Test Verification vs Validation — Who Does What?

  • The client, as well as the dev team, reviews the business requirement.
  • Design review is done by the dev team.
  • Code reviewing is performed, primarily by the developers.
  • The QA team reviews the test plan.
  • The test plan is again reviewed externally by the QA manager as well as business analyst.
  • Peer reviewing of the test documentation is performed by the QA team.
  • Finally, the business analysts along with the dev team reviews the test documentation.

Validation testing is performed entirely by the QA team which involves both manual as well as automation testers from the organization as well as sometimes from the client side.

Test Verification vs Validation — When Does the Process Get Executed?

  • The team makes sure that the requirements have been correctly gathered. Once they have been finalized, the next step begins — design review.
  • The dev team reviews the design and ensures all the suggested functional requirements can be actually implemented.
  • Coding starts and it is thoroughly reviewed to ensure that it is free from any syntax errors. This is a casual activity and can be performed by the developer.
  • A formal code review is carried out by the developer as well as the architect to check whether it satisfies the best practices and requirements specified.
  • Now the job shifts to the QA team. They create a test plan and reviews it internally to check the accuracy and completeness.
  • The test plan is reviewed by the QA manager as well as the project manager and BA to make sure that testing is in sync with other project activities.
  • After the test documentation is signed off, the team members review each other’s activity internally to ensure that the documentation does not have any mistakes.
  • Once everything is done, the test documentation again goes through a final review by the dev team after which it is shared to all the team members and ready for the next phase, i.e. validation testing.

Now, let us look into what Validation testing involves?

  • Unit testing — Done by the developer once the coding is completed as well as by the tester. Many common defects are caught during unit testing itself.
  • Integration testing — This is the phase where all the individual pieces of code or units are combined and tested as a whole. This evaluates whether the code complies to the required criteria.
  • System testing — This testing phase is carried out on the complete system once the integration is complete. It has multiple sub-categories like functional, load testing, regression testing and other forms of testing which ensures that the application does not have any bugs once it is live. Browser compatibility testing or cross browser testing is an integral part of system testing. It ensures that the website runs perfectly on all the device-operating system-browser combination specified by the client.
  • User acceptance testing — This is the last phase of validation testing. Here, actual users test the application to make sure that all the real world scenarios intended by the user can be handled smoothly by the application. This activity is carried out either by the organization or by the client.

Test Verification vs Validation — What do They Target?

Validation testing targets each component of the website, the modules, security, integrated components as well as the final website once it is ready for Golive.

Test Verification vs Validation — Cost of the Process

Validation testing, on the other hand, cost a lot because it involves manual labor, automation tools, cost of licenses of the testing as well as reviewing tools and in case of a cross browser compatible website, the cost increases since the organization has to purchase multiple devices and operating systems on which testing should be carried out. However, the device and OS cost can be reduced a lot if you are using a cloud-based testing platform like LambdaTest, where you can test your application seamlessly across hundreds of different device-browser-OS combinations simultaneously.

Check how your website looks across

2000+ Browsers AND OS

How Test Verification & Validation Balance the SDLC?

FREE SIGNUP

For example, the customer may ask for a certain feature like a hovering effect on a certain image or button for his cross-browser compatible website. This requirement may pass verification testing but will fail validation testing since certain hover effects of CSS3 are not supported in Internet Explorer 11 or below.

Let Us Evaluate Some Examples

Verification testing

  • Test cases are written to test the feature in multiple browsers, especially the browsers suggested by the client.
  • What if it is found out that while documenting the requirements, there was some mistake in the color code. We don’t want the button to look something like this

In that case, the necessary corrections are made in the document and it is again sent for review.

  • The documents are sent to the respective team members for a final review.
  • Once that is done, the development team starts coding.

Validation testing

Conclusion

Originally published at LambdaTest

Author Arnab Roy Chowdhury

Image for post
Image for post

Written by

Product Growth at @lambdatesting (www.lambdatest.com)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store