Welcome!

@DevOpsSummit Authors: Yeshim Deniz, Dana Gardner, Elizabeth White, Liz McMillan, Zakia Bouachraoui

Related Topics: @DevOpsSummit, Containers Expo Blog, @CloudExpo

@DevOpsSummit: Blog Feed Post

Verification and Validation: The Difference | @DevOpsSummit #DevOps

In an Agile development process, ideally both verification & validation activities occur as close to simultaneously as possible

Verification and Validation: The Difference
by Jeffrey Martin

I've been asked several times recently about the difference between Verification and Validation in automated testing and for some advice on applying and documenting each kind of testing. Let me first take a minute to define these terms.

Verification Vs. Validation
Verification is testing that your product meets the specifications / requirements you have written. "Did I build what I said I would?"

Validation tests how well you addressed the business needs that caused you to write those requirements. It is also sometimes called acceptance or business testing. "Did I build what I need?"

V&V together make sure that your software has delivered on its purpose in an error-free (ideally) way.

Using V&V in Your Workflow
In a more traditional Waterfall process, with Specifications and Requirements defined at the start, Validation is often performed at the end of the testing cycle. You spend tons of time defining a product, build it, make sure your software was bug-free, and then do user acceptance testing, or submit it to a client / users, perhaps even a Beta release.

In an Agile development process, ideally both verification and validation activities occur as close to simultaneously as possible. This is because you are always updating and refining your User Stories, necessitating constant small V&V loops to enable this continual feedback.

Part of the role of the Product Owner is to define what features should look like ahead of a sprint, elicit any customer feedback needed during development, and speak for the user if necessary. Validation therefore in part falls on the P.O. but is also baked into your Agile process itself. Because you are ideally using short development iterations with continual feedback from users/customers, in reality you are practicing almost Continuous Validation.

Applying Agile Verification and Validation to some industries can be a little intimidating. I've even heard people incorrectly say things like "my industry can't test in an Agile way because of X regulation." For instance, in Medical Devices you need to make sure you are in compliance with FDA regulations / guidance like 21 CFR part 11 and ISO 13485, which have more focused Validation requirements and a lot more focus on risk and documentation. Verification activities are fairly straightforward and often done via automation. Validation can be trickier.

One thing I know several Medical Device or other regulated teams do is Exploratory or Session Testing; this can be a great tool especially with mixed software/hardware devices. Structure and documentation is inherent in the way the FDA views testing, but structure does not mean that it must be pre-scripted.
Give your testers assignments on a sheet in a format similar to

"Explore _______ With ______ To Discover _______"

An example might be: "Explore drug inventory control With a variety of products To Discover if entering the information is intuitive"
Or better yet let them have some fun coming up with a bunch of these themselves. This can work great as a method to uncover defects in unwritten requirements and as a way to test User Experience. If you use the above structure, essentially a Test Charter, record your steps and results, and you have also generated documented Validation tests!

Read the original blog entry...

More Stories By SmartBear Blog

As the leader in software quality tools for the connected world, SmartBear supports more than two million software professionals and over 25,000 organizations in 90 countries that use its products to build and deliver the world’s greatest applications. With today’s applications deploying on mobile, Web, desktop, Internet of Things (IoT) or even embedded computing platforms, the connected nature of these applications through public and private APIs presents a unique set of challenges for developers, testers and operations teams. SmartBear's software quality tools assist with code review, functional and load testing, API readiness as well as performance monitoring of these modern applications.

@DevOpsSummit Stories
Nicolas Fierro is CEO of MIMIR Blockchain Solutions. He is a programmer, technologist, and operations dev who has worked with Ethereum and blockchain since 2014. His knowledge in blockchain dates to when he performed dev ops services to the Ethereum Foundation as one the privileged few developers to work with the original core team in Switzerland.
"We do one of the best file systems in the world. We learned how to deal with Big Data many years ago and we implemented this knowledge into our software," explained Jakub Ratajczak, Business Development Manager at MooseFS, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
All zSystem customers have a significant new business opportunity to extend their reach to new customers and markets with new applications and services, and to improve the experience of existing customers. This can be achieved by exposing existing z assets (which have been developed over time) as APIs for accessing Systems of Record, while leveraging mobile and cloud capabilities with new Systems of Engagement applications. In this session, we will explore business drivers with new Node.js apps for delivering enhanced customer experience (with mobile and cloud adoption), how to accelerate development and management of SoE app APIs with API management.
As Cybric's Chief Technology Officer, Mike D. Kail is responsible for the strategic vision and technical direction of the platform. Prior to founding Cybric, Mike was Yahoo's CIO and SVP of Infrastructure, where he led the IT and Data Center functions for the company. He has more than 24 years of IT Operations experience with a focus on highly-scalable architectures.
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.