Industry Insights
Is Software Testing a Lost Art?
July 29, 2025
“You can’t test quality into a product, but proper testing can assure that a product has quality.” - John McMahon.
Is it just me, or have you noticed many software applications, including websites, have “bugs”?
Even the websites of large and well-known companies will sometimes take you to the never-never land of the 400s (400 Bad Request, 401 Unauthorized, 402 Payment Required, 403 Forbidden, 404 Not Found - the most common error code on the internet).
Website errors – the ones reflected by HTTP error codes, specifically, occur for several reasons.
Human errors could lead visitors to encounter 404 errors and non-existent pages. However, the most likely cause is that someone, somewhere, didn’t do sufficient testing of changes or additions to the website.
A lack of consistent and complete testing before release is also commonplace and found on many LIS laboratory information system software applications, the pathology lab software most commonly used by medical labs.
Discover More: What You Need to Know Before Contracting with a Laboratory Information System (LIS) Company
Why Thorough Software Testing Matters for Medical LIS and Lab RCM System Users
So, what does this mean to a user of a medical lab’s LIS system or lab revenue cycle management (lab billing) software?
The proper functioning of your LIS software and laboratory billing system is critical to the accuracy and safety of your lab’s operations. As a user or buyer of the lab information system and lab billing products, it is incumbent on you to ensure that your lab vendors incorporate best practices for diagnostic lab software testing.
Several stages of testing should be completed before a software program is cleared for use. They include:
- Unit Testing
- Integration Testing
- System Testing
- Acceptance Testing
Unit Testing: This focuses on specific units or components of the software to determine whether each is fully functional. The endeavor aims to determine whether the application functions as designed.
Integration Testing: This combines all the units within a program and tests them as a group in a sequence to replicate the real-world business requirements. This stage is designed to find interface defects between the module's software functions.
System Testing: This phase involves testing the entire application as a complete, integrated system. The objective is to verify that all specified requirements have been met and that the system functions according to quality standards. To ensure unbiased results, system testing should be conducted by independent testers who were not involved in the software’s development.
Acceptance Testing: This determines whether the system is ready for release. The user will test the system to see whether the application meets their business needs. Once this process has been completed and the software has passed acceptance testing, the program can be delivered (to the production environment).
The Critical Role of Regression Testing in Maintaining LIS Software Integrity
What’s listed so far is not a complete list. While the list covers the software development of new applications, it doesn’t address what happens when changes are made to already operating applications, such as laboratory information systems.
When “improvements” or “fixes” are made to functioning LIS systems, these improvements can go badly. What is missing is a major cause of undiscovered LIS software “bugs.”
Regression Testing: This testing is performed to determine whether the recent updates and changes to the LIS software have caused new defects in the existing laboratory information system functions.
Regression testing is a type of testing in the software development cycle that runs after every change to ensure that the update doesn’t introduce new unintended breaks.
This form of testing addresses a common issue all developers face: the emergence of old (or new) “bugs” with new code. It can ensure that a software application works as intended after any code changes, updates, revisions, improvements, or optimizations.
Don’t Settle for “Fixed”: How to Ensure Your Medical LIS and Lab Billing Systems Are Truly Reliable
Have you ever taken your car to the mechanic, only to be told the issue is fixed, yet when you drive away, the problem still exists?
Why?
That’s often because the mechanic found a problem and stopped there, without confirming if it was the root cause, checking for additional issues, or considering whether the “fix” may have introduced a new problem.
What can you do as a laboratorian to help ensure that your medical LIS or lab billing system continues to function properly?
Start by confirming that your lab vendors (LIS company or RCM management company) adhere to good manufacturing and testing processes.
Conduct a quick internet search and you’ll find several excellent website references that describe laboratory software testing best practices.
You can also continue reading to find out how LigoLab, a leading developer of pathology lab reporting software for medical laboratories, leaves no stone unturned while ensuring that its software solutions are properly tested before release.
Check out LigoLab’s detailed methods for software development and testing, and then compare what you learn with your existing software supplier or lab vendors under evaluation for partnership.
Editor’s Note: To learn more about Dennis and his consulting services, visit his website at dwinsten.com.
LigoLab’s Laboratory Information System Software Testing and Quality Control Plan
It started in 2006, and ever since, LigoLab has been blazing a new trail, setting the standard for how laboratory information system companies should develop their pathology lab software and create true partnerships with customers.
Widely recognized for its innovative all-in-one laboratory information system, complete with advanced, integrated laboratory billing solutions, LigoLab consistently delivers new features and enhancements that streamline laboratory workflow management. The company excels at digitally transforming clinical labs and pathology groups into modern, efficient, and profitable operations.
At LigoLab, rapid development is always paired with rigorous software testing to ensure reliability and performance.
“It’s important to cover all the bases,” said Gor Kalantaryan, LigoLab’s Chief Operating Officer. “We can be as thorough and fast as possible because our process is automated and not limited to human capabilities.”
Discover More: LigoLab - Shaping the Future of Clinical Labs & Pathology Groups
The 5 Keys to LIS Software Development Quality Control
The LigoLab development team follows five quality control protocols, which help ensure the release of successful laboratory information system software. They are as follows:
Development Code Audits: The team conducts separate code reviews involving a senior developer and an architect. Both must agree and approve the development plan before integration starts.
Automated Regression QA (White Box Testing): LigoLab next initiates automated regression testing that runs on every build. This important step ensures that new developments won’t introduce or reintroduce underlying issues.
“This type of testing happens behind the scenes at the code level and uses robotics to validate the logic that powers the application’s functionality,” explained Kalantaryan. “A virtual robot simulates a user by interacting with the application’s interface, clicking through elements just like a person would. Because it’s fully scripted, the test is consistent and repeatable, thereby eliminating any variation from one run to the next.”
Kalantaryan also noted that robotic regression testing is valuable because it allows developers to catch UI artifacts that may have been missed with only pure code testing.
Manual QA (Black Box Testing): Manual QA is conducted by the support team and a member of the QA department to ensure full coverage.
“This testing involves a human who doesn't know what's happening behind the scenes. He or she is purely there for the user's experience,” continued Kalantaryan. “The tester receives a debriefing about the feature and its intended functionality, and then proceeds to test the feature to see what issues arise during use.”
Unlike automated regression QA, this type of testing isn’t consistent from one test to another and serves as the final layer of quality control.
Version Control: LigoLab’s development process includes version control over the LIS medical software. This optimizes change management and ensures precise changes are deployed. It also makes it easier for the development team to track what may have caused an issue.
Agile Development Model: The development process features biweekly bursts (sprints) and daily scrums to ensure proper turnaround for all development items.
Discover More: Market Differentiation and Unmatched Customer Service - Two Major Reasons Why You Should Consider LigoLab for Your LIS System Upgrade
LIS System Software Testing and Customer Involvement
Kalantaryan continued by detailing the importance of customer involvement when testing LIS system software.
“We very much support customer testing and encourage them to test their workflows as much as possible before going live with a major update,” he said.
As part of its standard licensing agreement with customers, LigoLab provides and manages three dedicated LIS software environments: Testing, Training, and Production.
First, all new features are developed, validated, and automatically rolled out to all customers via their testing environment. Next, the training environment is there for the customers to train, test, and validate specifically controlled version updates. Only after thorough testing and validation, are version updates pushed to the production environment.
Editor’s Note: For an in-depth rundown of LigoLab’s approach to customer support and training, CLICK HERE.
No Room for LIS Software Shortcuts
With LIS software testing, there’s no room for shortcuts.
That is and always has been the LigoLab way.
Yes, LigoLab spends more time and resources on the development cycle than the norm, but the extra attention to detail ensures quality code, future-ready pathology lab software, and scalability.
“Our philosophy benefits us and our customers by addressing issues promptly, preventing problems from worsening over time, thereby avoiding the need for more extensive resources later,” concluded Kalantaryan.
Discover More: Stability and Performance: The Two Most Important Aspects of a Modern Laboratory Operation
Ready to Modernize Your Lab?
Discover how LigoLab’s all-in-one medical LIS & lab billing platform can transform your operations.
