IV&V Testing and Test Witness Services

Independent verification and validation (IV&V) testing confirms that your system meets its requirements and works for the people who use it. We test it ourselves, or witness the developer’s tests, and report what we find.

Independent IT testing since 1988

Colleagues discussing results in an office.

You come away with

  • Test planbased on risk
  • Test reportevery result recorded
  • Defect reportsrated, with evidence

What is IV&V testing?

IV&V testing is testing performed by a team that is independent of the developer, as part of independent verification and validation. Verification testing checks that the system meets its specified requirements. Validation testing checks that it does what its users and the mission need.

IV&V stands for independent verification and validation. The point of the independence is that the people who test the system have no stake in its schedule, so defects are found and reported early, while they are still cheap to fix.

TestPros has provided independent testing since 1988, for government and commercial customers, on systems from mainframes to cloud platforms.

What our IV&V testing services include

  • Test planning: We write a test strategy and plan based on the risk profile of the system.
  • Requirements-based test design: We trace every requirement to a test, so nothing is left unverified.
  • Independent test execution: We run the tests ourselves, manually and with automation.
  • Test witnessing: We observe the developer’s or a third party’s tests and confirm they were run as planned.
  • Defect reporting: We document each defect with evidence, a severity, and the requirement it affects.
  • Retest and regression: We retest fixes and check that nothing else broke.

We are here to assist you

Tell us about the system and when it has to be tested. We will reply with next steps.

IV&V vs software quality assurance (SQA)

IV&V and SQA are not the same thing, and one does not replace the other. SQA works inside the project. IV&V works outside it.

IV&V compared with software quality assurance
 IV&VSoftware quality assurance
Who does itA team independent of the developerThe developer or program office
Who it reports toThe sponsor or customerThe project manager
What it checksThe product: requirements, design, code, and test resultsThe process: whether the team follows its own standards
The question it answersIs this the right system, built correctly?Are we following our process?
Can it stop a release?It recommends for or against, directly to the sponsorIt raises issues inside the project

User acceptance testing (UAT) is different again. UAT is run by the system’s users to decide whether to accept it. IV&V testing often supports UAT but does not replace it.

IV&V testing types and benefits

We support the test types an IV&V effort calls for, in waterfall, Agile, and DevSecOps projects, with automation where it pays.

Our IV&V testing methodology

  1. Assess the risk

    We rate how critical the system is. IEEE 1012 calls this the integrity level, and it sets how much testing is needed.

  2. Plan the tests

    We write the IV&V test plan: scope, test levels, environments, schedule, and entry and exit criteria.

  3. Trace the requirements

    We map each requirement to test cases and flag requirements that cannot be tested.

  4. Test or witness

    We run component, integration, system, and acceptance tests, or witness the developer running them.

  5. Report defects

    We record every anomaly with evidence and a severity, and send it to you and the developer.

  6. Retest and report

    We retest fixes, run regression tests, and deliver the final IV&V test report.

What you receive

Test evidence that stands up when someone asks how you know the system works:

Sample excerpt. Your report lists every test and its result.

Independent testing or test witnessing?

Our IV&V testing customers have included the U.S. Air Force, the Department of Health and Human Services, the Department of Homeland Security, and the Defense Information Systems Agency.

Certified & independent

TestPros has provided independent IT testing to commercial and U.S. federal, state, and local government customers since 1988. Our services are built on trust, quality, efficiency, and innovation in support of our customers’ missions. In information systems work, we prioritize risk assessment and risk management to protect business continuity.

See our certifications

Trusted clients

View our clients

Frequently asked questions

What does IV&V stand for?

IV&V stands for independent verification and validation. It is sometimes written IVV or IV and V. Verification confirms a system is built to its requirements. Validation confirms it meets the needs of its users.

What is the difference between IV&V and SQA?

Software quality assurance (SQA) is part of the project team and checks that the team follows its process. IV&V is independent of the team, checks the product itself, and reports to the sponsor. Large projects use both.

What is the difference between IV&V testing and UAT?

User acceptance testing is run by the system’s users to decide whether to accept it. IV&V testing is run by an independent team to find defects and confirm requirements are met. IV&V testing usually comes first and often supports UAT.

What is test witnessing?

Test witnessing is when an independent party observes tests run by the developer or a third party. The witness confirms the tests followed the approved procedure, records the results, and reports anything that was skipped or changed.

Which standards apply to IV&V testing?

The main one is IEEE 1012-2024, the IEEE Standard for System, Software, and Hardware Verification and Validation. It defines the testing each integrity level requires. Government projects also follow their agency or state IV&V policy.

Is there an IV&V certification?

No. There is no official certification for IV&V providers. Buyers look for real independence from the developer, a track record on similar systems, and audited quality certifications such as ISO 9001, which TestPros holds.

When should IV&V testing start?

Test planning should start with the requirements, not after the code is written. Requirements that cannot be tested are the cheapest defects to find. Test execution then follows each build.

Does IV&V testing work with Agile and DevSecOps?

Yes. In Agile and DevSecOps projects we test each increment, add automated tests to the pipeline, and report every sprint. The independence is the same. The reporting is faster.

Do you use test automation?

Yes, where it pays. We automate regression and repeatable functional tests so they can run on every build, and keep manual testing for the cases that need a person’s judgment.

How much does IV&V testing cost?

The cost depends on the size of the system, how critical it is, the number of requirements and interfaces, and whether we run the tests or witness them. We scope the work and quote it before anything starts.

Which firms provide IV&V testing for government software projects?

TestPros is one. We have provided independent testing since 1988, hold a prime IV&V agreement with the U.S. Nuclear Regulatory Commission, and can be ordered through our GSA Schedule. See our government contracts.

Can TestPros test a system it helped build?

No. IV&V testing only means something if the tester is independent. We do not provide IV&V testing on systems we developed.

What challenges are you facing?

Tell us about the system and when it has to be tested. We will scope the work and quote it before anything starts.

Contact us