Semaphore Logo clickable link to home page.
Services
Services
Strategic ConsultingSystem ImplementationInformatics SupportScientific Software Development
Domains
Domains
ClinicalResearchLife Sciences
resources
resources
BlogCase StudiesWhitepapersCareers
ABOUT US
Contact
Contact
Quality
Lab Software
Validation

Software Quality:

What Role Does Testing Play?

by

The Semaphore Team

No discussion about software quality would be complete without examining the role of software testing. In the previous post in this series on quality, we mentioned that software testing is a vital part of software quality control (QC). That’s because it’s used to find and prevent defects, ensure performance, and confirm that requirements are met.

‍

“Testing is the procedure of evaluating software quality by utilizing the software with appropriate test cases and to figure out whether the proposed software requirements are fulfilled.” – Manju Khari

‍

In this post, we’ll take a closer look at which types of software need to be tested, when they should be tested, and how testing can help you ensure the quality of your software is high.

Types of lab software that should be tested

Every type of software in the lab needs to be tested. Whether your lab is using an off-the-shelf laboratory information management system (LIMS) with or without customizations, custom software applications, or instrument and system integrations, you’ll need to make sure that you test them all.

When to test software

We recommend testing frequently throughout the development phase, but especially before you go live in your production environment. Software should also be tested anytime a change is made to applications already in production. Lastly, we suggest testing production software periodically to ensure nothing has been broken by regular system updates such as those coming from other software vendors (e.g., LIMS version releases or supporting library releases, which may not be as obvious).

How to ensure testing supports the best quality software

There are several ways you can use testing to make sure software meets your lab’s requirements, is free from error, and fit for purpose:

  • Include non-functional tests to ensure your software is robust, but also flexible, performant, and scalable. This is critical for labs in the process of scaling or wanting to scale in the future. Non-functional tests might include performance, load, stress, volume, and security testing.
  • Automate testing to provide maximum code coverage. Code coverage is a software testing metric that refers to how much of the source code is being tested. In general, you should aim for about 80% code coverage. As Manju Khari notes, an increase in automated testing is proven to show quantifiable improvements in quality assurance. Also, there’s less chance of human error. LIMS workflow test automation is a good example of a common software test automation that clinical labs can take advantage of.
  • Develop a software testing plan. Write an automated testing implementation strategy and risk management plan. An exercise like this can help you identify where you could add automated testing while avoiding common pitfalls — such as automating tests for unstable test objects, introducing too many test cases at once, failing to write test specifications, lack of leadership support for automated testing, or weak definition of project terminology.

Note that it won’t be possible to automate absolutely everything related to software testing. You’ll always need people to manually develop and maintain the tests. But we advise labs to start building now and continue to add automated testing wherever possible. We believe it’s helpful to view the effort expended in building tests as continually ensuring overall quality, rather than simply part of the development effort.

High-quality testing leads to high-quality software & more efficient lab processes

Typically when clinical labs make minor assay revisions, they need to make time to validate them prior to sending the revisions to the production environment. If you use automated software testing, however, you’ll save time during this phase, and you’ll spend less time validating minor revisions overall.

‍

In other words, investing in automated testing during the initial software build pays significant dividends over time, in terms of efficiency and efficacy, as assays evolve. When researchers looked at the trade-offs between automated and manual software testing, they reported that “test automation is a plausible tool for enhancing quality, and consequently, for reducing software development costs in the long run.”

‍

If you’re interested in learning more about the types of testing you could use for different applications and stages of development, see our previous post on software testing. Or, contact us if you have any questions about software quality.

‍

Explore our blog

All Blog Posts

The Importance of Data Integrity in the Laboratory: Adhering to FDA Standards and ALCOA Principles

In today’s highly regulated laboratory environment, maintaining data integrity is not just a matter of good practice—it’s essential for compliance, reliability, and the overall success of lab operations. For lab managers and IT support staff, ensuring data integrity means safeguarding data’s accuracy, completeness, and consistency throughout its lifecycle.

12
min read

Updating Your Lab Workflow? 4 Feature Implementation Scenarios to Consider

When updating lab workflows, not all software changes are created equal. This blog post outlines four common implementation scenarios—ranging from enabling an out-of-the-box (OOTB) feature to developing a fully custom solution—and explains how each impacts cost, effort, and timelines. Whether you’re adding a new assay or integrating an instrument, understanding these scenarios helps labs plan smarter, reduce risk, and align stakeholders. Read on to learn how to choose the right approach for your lab’s needs and how Semaphore Solutions can help guide your next move.

6
min read

Mapping Lab Systems the Right Way: Workflow vs. State Diagrams

Workflow and state diagrams play a crucial role in documenting and visualizing laboratory systems. Both are invaluable for labs implementing a laboratory information management system (LIMS) or adding automations to streamline laboratory operations, reduce errors and redundancies, and ensure regulatory compliance. However, each type of diagram serves a distinct purpose.

7
min read
Semaphore Logo
  • Services
  • Domains
  • Resources
  • About Us
  • Careers
  • Contact Us
  • 1 (844) 744-3577 ext 1
  • 200-844 Courtney St.
  • Victoria, BC V8W 1C4
  • Canada
LinkedIn Social Media Icon Linking to Semaphore Account
  • Cookie Policy
  • Privacy Policy
All Rights Reserved © Semaphore Solutions Inc.