Is Software Testing a Lost Art?

"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 that many software applications, including websites, have bugs? Even the websites of large, well-known companies will sometimes take you to the never-never land of the 400s: 400 Bad Request, 401 Unauthorized, 403 Forbidden, 404 Not Found, the most common error on the internet.

Website errors can happen for many reasons, but the most common cause is inadequate testing before new features or updates are released. This same issue is frequently seen in many laboratory information system (LIS) applications (the pathology software widely used by medical laboratories), where inconsistent or incomplete pre-release testing can lead to avoidable problems.

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 Laboratory Billing System Users

The proper functioning of an organization’s LIS software and laboratory billing system is critical to the accuracy and safety of lab operations and finances. As a user or buyer of laboratory information systems and lab billing products, it is the customer's responsibility to ensure that their lab vendors incorporate best practices for diagnostic lab software testing.

The Four Core Stages of Software Testing

The lab vendors should complete several stages of testing before clearing a software program for use, such as:

Unit Testing: Focuses on specific units or components of the software to determine whether each is fully functional and to verify that the application performs as designed.

Integration Testing: Combines all units within a program and tests them as a group in sequence to replicate real-world business requirements. In this stage, testers look for interface defects between the module's software functions.

System Testing: Entails testing the entire application as a complete, integrated system, verifying that the team has met all specified requirements and that the system functions in accordance with quality standards. To ensure unbiased results, independent testers who were not involved in the software's development should conduct system testing.

Acceptance Testing: Determines whether the system is ready for release. The user tests the system to confirm it meets their business needs. Once the software passes acceptance testing, the team can deliver it to the production environment.

The Critical Role of Regression Testing in Maintaining Laboratory Information System Software Integrity

The four stages above cover the development of new applications, but they don't address what happens when teams make changes to already-operating systems, such as laboratory information system software. When lab vendors make improvements or fixes to functioning LIS systems, those changes can introduce new problems. What's often missing is regression testing, a major cause of undiscovered bugs in LIS software.

What Is Regression Testing?

Lab vendors perform regression testing to determine whether recent updates to the LIS have introduced new defects in existing laboratory information system functions. It runs after every change to ensure that updates don't introduce unintended breaks, addressing a common issue all developers face: the emergence of new or old bugs in new code.

Don’t Settle for “Fixed”: How to Ensure Your Medical LIS and Lab Billing Solutions Are Truly Reliable

Have you ever taken your car to the mechanic, only for the problem to persist when you drive away? That's often because the mechanic found a problem and stopped there, without confirming it was the root cause, checking for additional issues, or considering whether the fix introduced a new problem.

What Can You Do as a Laboratorian?

Start by confirming that your lab vendor, whether a laboratory information system or RCM management company, adheres to good manufacturing and testing practices. You can conduct a quick internet search to find excellent references on laboratory software testing best practices, or continue reading to find out how LigoLab, a leading developer of advanced clinical and pathology lab reporting software, leaves no stone unturned before releasing its software solutions.

LigoLab’s Laboratory Information System Software Testing and Quality Control Plan 

A Standard Set in 2006

Since its founding in 2006, LigoLab has been setting the standard for how laboratory information system companies develop clinical and pathology lab software that builds true partnerships with customers. Widely recognized for its innovative all-in-one laboratory information system with advanced integrated laboratory billing solutions, LigoLab consistently delivers new features and enhancements that streamline laboratory workflow management, always pairing rapid development with rigorous software testing.

"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 Laboratory Information System Software Development Quality Control 

LigoLab’s development team adheres to five quality control protocols to support the reliable and successful release of new versions of its laboratory information system platform.

1. 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 begins, establishing a strong foundation before a single line of new code is engineered.

2. Automated Regression QA, White Box Testing

LigoLab initiates automated regression testing that runs on every build, ensuring new developments don'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 the team fully scripts the test, it remains consistent and repeatable, eliminating any variation from one run to the next."

Robotic regression testing is also valuable because it helps developers catch UI artifacts that pure code testing alone might miss.

3. Manual QA, Black Box Testing

The support team and a QA department member conduct manual QA 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, 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 run to the next and serves as the final layer of quality control before release.

4. Version Control

LigoLab's development process includes version control over the laboratory information system software. It optimizes change management, ensures the team deploys precise modifications, and makes it easier for the development team to track potential causes of issues.

5. Agile Development Model

The development process features biweekly sprints and daily scrums to ensure the timely delivery of all development items, keeping the team aligned, accountable, and moving efficiently.

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 emphasized 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.

Three Dedicated Software Environments

As part of its standard LIS model for licensing, LigoLab provides and manages three dedicated LIS software environments for every customer: Testing, Training, and Production.

1. All new features are first developed, validated, and automatically rolled out to customers via their testing environment. 
2. The training environment allows customers to train, test, and validate updates to specifically controlled versions. 
3. 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 Laboratory Information System Shortcuts 

With information systems and data management software testing, there's no room for shortcuts, and that has always been the LigoLab way. Yes, LigoLab spends more time and resources on the development cycle than the industry norm. Still, the extra attention to detail ensures quality code, future-ready pathology lab report software, and long-term scalability.

"Our philosophy benefits our customers and LigoLab 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 laboratory information system with advanced and embedded laboratory billing solutions can transform your operations.

Don’t Wait: Contact a Product Specialist and Schedule a Demo Today!

Frequently Asked Questions About Software Testing, Laboratory Information Systems, and Quality Control

Why is software testing so important for laboratory information systems and data management?

Laboratory information systems and data management solutions impact the accuracy and safety of operations. Bugs or untested changes can lead to errors in specimen tracking, lab billing denials, compliance failures, and patient safety risks. Rigorous testing ensures the clinical and pathology software performs reliably under real-world conditions before it reaches a live environment.

What are the four main stages of software testing for LIS systems?

The four core stages are unit testing, which checks individual components; integration testing, which verifies that modules work together correctly; system testing, which evaluates the full application against quality standards; and acceptance testing, which confirms the software meets the lab's specific business needs before going live.

What is regression testing, and why does it matter for laboratory information systems?

Regression testing runs after every code change to verify that updates haven't introduced new defects in existing functionality. It's particularly critical for laboratory information systems because even small fixes or improvements can inadvertently break other parts of the system, creating bugs that may go undetected without proper regression protocols.

What are LigoLab's five quality control protocols for laboratory information system software development?

LigoLab follows five protocols: development code audits requiring sign-off from both a senior developer and an architect; automated regression QA using robotic white box testing on every build; manual QA through black box testing by the support and QA teams; version control to manage and track all code changes; and an agile development model with biweekly sprints and daily scrums.

What is the difference between white box and black box testing?

White-box testing, also called automated regression QA, tests software at the code level using scripted robots that simulate user interactions. It is consistent and repeatable. Black-box testing involves a human tester with no knowledge of the underlying code who evaluates the user experience. LigoLab uses both in combination for maximum coverage.

How does LigoLab involve customers in the software testing process?

LigoLab provides every customer with three dedicated LIS software environments: Testing, Training, and Production. The team first deploys new features in the testing environment, then validates them in the training environment before pushing updates to production. Customers are encouraged to test their workflows thoroughly before approving any major version update.

How can lab customers evaluate whether their current LIS company has adequate testing practices?

Labs should ask their LIS software vendor to describe their development and testing processes in detail, specifically whether they perform regression testing, which QA stages they follow, how they manage version control, and how customers are involved before updates go live. Comparing those answers against best practices such as LigoLab's five-step protocol is a useful benchmark.