How to Procure Test Evidence that Supports Pharmaceutical System Change 

November 16, 2026 · Cam White

What makes for great test data and how can pharmaceutical teams acquire it without creating more work for themselves? We answer those questions here.

Pharmacists working on medicinal test tubes

Pharmaceutical manufacturers are reshaping how medicine is manufactured, managed, recorded. Eli Lilly is building a new manufacturing facility that will have digital systems and automation embedded throughout it. Sanofi is working with Siemens and Capgemini to standardize its production processes and roll out manufacturing execution systems (MES) powered by generative AI. 

These innovations immensely improve operations. But they also alter the established workflows on which production and quality teams rely. As a result, quality and validation teams will need to assess these new systems and their changed workflows.  

A key part of this work is procuring evidence that proves systems and their workflows work as intended. This is equally important whether a company is bringing a new site online or replacing an established process. Below, we examine what makes for great test data and how teams can acquire it without creating more work for themselves. 

Follow the workflow beyond the application 

Before a team even conducts a test, they should define the required evidence at the outset. A key guidepost for this involves being thorough and covering everything a test touches. 

Consider a change to a laboratory information management system, or LIMS. A test might confirm that an approved laboratory result appears correctly on screen. If the workflow also requires that result to reach a quality record, the review needs to account for that handoff.  

Checking the LIMS screen alone would leave the team uncertain about whether the handoff worked. Instead, the test evidence should answer questions like:  

  • Did the result reach the correct record?  
  • Were the value, units and approval status preserved?  
  • Could the appropriate user access it, and were restricted actions still restricted? 

If these questions remain open, the team may need further testing or investigation before releasing the system change. This is why it’s also important to be thorough in the test evidence provided. 

Leapwork helps pharmaceutical and life sciences QA and validation teams automate repeatable regression testing across complex applications with recorded runs and audit trails that support review and validation evidence.
See how we do it.  

Make the record useful to the reviewer 

Useful test evidence tells a clear story: what the test was intended to prove, what actually happened, and the context needed to understand the result. That context can include the scenario, system and version, relevant environment, requirement or risk, and any required review or approval.  

A “passed” label on its own leaves too much for a reviewer to infer. A reviewer should be able to understand a test without having watched it run.  

For the LIMS example, the record needs to show what happened to the result as it moved between systems. Depending on the risk and applicable procedures, useful evidence includes: 

  • The requirement or risk being tested and the expected outcome. 
  • The relevant systems, versions, environment and test data. 
  • The actual result, including what happened at the handoff. 
  • Any exceptions, their assessment and the required review or approval. 

The level of detail should reflect the risk. Agreeing on what reviewers need before testing begins helps teams collect useful records and avoid unnecessary documentation. 

Capture evidence as part of testing 

Once the evidence requirements are clear, teams can decide what to capture during execution and how to manage it afterward. 

For repeatable regression tests, recordings and execution logs can preserve details that would otherwise need to be reconstructed. They can help reviewers inspect the steps performed and help testers investigate an unexpected result. Linking the run to its test purpose, system context and relevant requirement makes that record more useful. 

Evidence gaps often appear between test execution, review, and retention. Teams need a clear process for assessing exceptions, completing required reviews and keeping records accessible. When workflows, configurations or system versions change, the tests themselves need review to confirm they still check the intended behavior. 

Planning these steps together can reduce the work of reconstructing evidence after a test. It also gives testers and reviewers a shared understanding of what must be recorded and who is responsible for assessing. 

Start with one critical workflow 

A practical starting point is one critical workflow affected by frequent change. Define its intended outcome, the handoffs and exceptions that matter, and the evidence a reviewer needs. Then assess whether automation can produce consistent, useful records in the relevant environment, and measure the testing, documentation and review effort involved. 

This gives quality teams a concrete improvement to work toward: less time reconstructing what happened during a test and clearer evidence for the decision to release a system change. 

NecstGen, the Netherlands Center for the Clinical Advancement of Cell and Gene Therapies, offers a practical example of innovating its testing processes for a frequently-changing critical workflow as systems change. 

How NecstGen supports review as systems change 

NecstGen faced a critical workflow challenge as its quality and laboratory systems underwent frequent changes. The organization uses a Salesforce-based Quality and Laboratory Information Management System, or QLIMS, in a GxP environment. Salesforce updates created a recurring need for retesting and regression testing. 

NecstGen used Leapwork Flow to build its initial automated test cases within two weeks. Leapwork’s video recordings provided on-demand witnessing information and reduced manual documentation work. For NecstGen, recorded test runs helped address a recurring need: reviewing its QLIMS as Salesforce changed.  

Leapwork Flow supports visual automation across supported enterprise applications, with video recordings and execution logs that can help teams investigate and review test results. Flow uses visual automation to build and run tests across enterprise applications. Its execution tools include video recordings, data insights, and logs that can help teams investigate and understand results. These records can support review, while the organization’s validation procedures determine how they are assessed and retained. 

Frequently Asked Questions

What should test evidence include in a GxP environment? 

It should identify the test scenario, system and version, relevant environment, intended outcome, actual result, and any required review or approval. Procedures should define how evidence connects to requirements and risks. 

How can teams keep test evidence useful as systems change? 

Review automated tests when workflows, configurations, or system versions change, and confirm each test still serves its intended purpose. Keep each run identifiable so reviewers can understand what was tested and when. 

How can Leapwork Flow support test evidence?  

Flow uses visual automation to run tests and capture video recordings, data insights, and execution logs that can help teams review results. Teams must determine how those records fit their own validation procedures and requirements.  

Sign up for a tailored demo and see for yourself how Leapwork Flow could support repeatable testing and evidence capture in your environment.