Test and Verification Management

Test and verification management are the processes and procedures to suitable critique the product (hardware or software) or processes (production). This is risk identification and mitigation activity as it attempts to quantify quality attributes of the product that may cause concerns with the customer during application. Testing and verification is also part of project management in that the results are often used to confirm contractual obligations are met, and thereby are part of project closure. Testing and verification management contain, planning and control, analysis and design, execution, reporting and closing activities. Hardware testing may include environmental stimuli (multiple simultaneous such as thermal and vibration) as well as testing the product to the extremes of functionality.

Test and verification management - Value Transformation

Testing Closure

In testing closure the objective and specific deliverable items from the testing are compared to the actual achievements and deliverables. The testing documentation is stored in a way that is easily retrievable along with the information on the product iteration the specific test cases were conducted. The test environment configurations are archived so these can also be retrieved at a later date should that be needed. Lessons learned are recorded from which the team will apply at some future date.

Test Execution

During test execution the tests are conducted on the product. Each of the test conditions and test environments are used to conduct the defined tests. Sometimes there will be spontaneous testing conducted, that is not one that was born out of the scope, plan or test analysis, but from what is learned in the process of conducting the test. Test execution will also be responsible for re-testing as perhaps the results of the test were some anomaly based upon the test configuration, or to learn more about the failure to be able to accurately report the details of the conditions that caused the failure. These are clues the developers will use to find the reason for the failure (hardware or software). Test execution address regression testing, that is testing of old parts of the product that have not changed, but require testing since the product has changes – this is largely associated with software.

Test Exit, Metrics and Reporting

Testing produces data from which an informed decision about the product can be made. These metrics will inform the team and other stakeholders the product’s suitability for release or production. Test metrics such as failure rates and severity remove some of the uncertainty from the launch. This phase of the testing produces reports where this information will reside allowing the project manager, stakeholders and executives to decide whether to launch or not based upon the results.

Test Planning and Control

To be able to test requires an understanding of the objectives of the project and customers. This understanding makes it possible to discern specific risks and clarify the scope of the testing to make assessment of those risks possible. Test planning will uncover and define the best test strategy along with discovering the talent and equipment required. Additionally, the planning will evoke key metrics or measurements from which the testing and results will be evaluated.

Test Analyze and Design

In test analysis and design, specific test conditions are identified from which the details of the testing will be created. This will require inputs such as product requirements and drawings, specifications, system descriptions and interfaces to other components and typical and extreme applications of the product. This will generate specific test methods, criterion, and metrics that will lead to detailed test cases along with the input data (test conditions) for the test. There is a strong connection between the product requirements and design documentation and the test details.

Testing Sites

Test and verification management – techniques for ensuring the product design, material and, where applicable, manufacturing processes culminate in meeting the customer’s needs. At the minimum verification serves to confirm or refute the product meets requirements.  However, there are many other approaches to testing iterations of the product through the development process. This includes software testing, which consists of processes and techniques that is coupled with the development effort to ensure the product quality over prototype iterations and the full lifecycle of the product.

    1. https://www.ministryoftesting.com/events
    2. https://astqb.org/
    3. https://www.istqb.org/
    4. https://www.softwaretestpro.com/
    5. https://www.stpcon.com/stpcon-staff/
    6. https://testinginstitute.com/cstpa.php
    7. https://www.associationforsoftwaretesting.org/
This video is a part of the Interview with Leaders in Testing series Jon M. Quigley holds the PMP and CTFL certification and is a principal of Value Transformation LLC a product development training and cost improvement organization. He has more then twenty years of product development experience, ranging from embedded hardware and software through verification and project management. Jon’s LinkedIn profile can be accessed at https://www.linkedin.com/in/jonmquigley His twitter handle is @jonmquigley Jon has submitted a paper for the upcoming Global Testing Retreat Conference at Pune, India on 22nd to 24th April 2016. To know more about the conference, please visit http://gtr.agiletestingalliance.org

The use of decision matrix tools can help us make a better decisions for our project and our organization and improve the outcome of our work.

My How We Change.

How we change. I shared this with those that I usually have to review my writing. They said I should not share this as it seemed very personal.  They said it seemed like it was something somebody would not share. After a short rumination, I decided to share this, writing. It amazes me where I […]

The LinkedIn Elephant

The Organization Organizations, or most successful organizations, are not static.  To remain an ongoing concern the organization will need to adapt to identified opportunities.  This will require growing the talent base, either organically, that is from within, or by finding talent external to the organization.  From an external perspective, how do we know the right […]

Career Change

  Career Change Recently we had a question come to us about how do we transition from one industry or a specific job title to another industry or another area of the company that requires different skills from what we presently have.  Perhaps a way to avoid becoming stale, we may want to explore other […]

The Confluence:

The Confluence: Configuration Management, Change Management, and Project Management Like Puzzle Pieces Configuration management, change management and project management are all connected.  Missing one or more of these in product development can mean exceeding the project budget and schedule at best, and at worst, the launching of a product that is more like a torpedo […]

Requirements, Elicitation and Attributes

More than one way There is not silver bullet or one way to do most things.  The best approach will depend upon the amount of time, talent, tools available, and potential risks associated with the work and level of risk aversion of those undertaking the effort.  The example below, is typical for developing embedded automotive […]

Mere Scrap of Information

Mere Scrap of Information – The Route to the Product I am a guy, and grew up in the 70’s.  My dad was a Vietnam Vet serving in the 7th Special Forces Group.  I grew up watching action movies.  My favorite actor of that era was Clint Eastwood, and one of my favorite movies Fist Full […]

Wire harness development and testing

Wire harness development and testing Slow is painful by Jon M Quigley Vehicle Systems Vehicles have become increasingly electrical over the year, even vehicles that are not electric propulsion.  There are more features, more embedded controllers and greater communication between the electronic controllers.  The range of content is from power electronics, sensor data (analog signals), […]

Regression Testing

By Jon M. Quigley I saw a LinkedIn post yesterday about scope of testing during times of compressed schedule. The position was to test what is new in the software, and of that new, what is the most important, perhaps meaning what if it goes wrong, would be the worst for the client or customer.  […]

Why formalize root cause analysis?

Why formalize root cause analysis?   There are many approaches to determining the root of our problems.  In the automotive world, there are two typical approaches, the 8D or the 8 Discipline, or the A3 (named for the paper size).  We will not go into the details of either of these approaches but you can find […]

Independent Test and Verification

We are composing a glossary of test terms and we take one from that work today and discuss here. A development organization can be structured in many ways. The development and testing can be essentially one department under one management structure, or these two areas, development and test can be separated each with a respective […]

2019 Carolina Collegiate Student Chapter

Building a Cause & Effect Diagram

CMMI Tracking

8D Template

Pugh Matrix

How to Brainstorm


Using Pareto Charts

SPaMCAST 477 – Silence: A Powerful Tool, Muddling Through, Monolithic Monolith


SPaMCAST 552 – Fit For Value, Saying No, Essays and Discussions


SPaMCAST 575 – Messing Up Agile Hybrids, Deming and Book Club, Essays and Discussions


Contact Value Transformation about Test and Verification Management