HealthITPrep
CPHIMS guide Concepts Features Pricing FAQ
Sign in Start free
العربية

Software testing types: from unit testing to user acceptance

By Adel Moustafa, CPHIMS® · Updated 22 October 2026

The levels of testing a health information system passes before go-live, the tests that check speed and limits, regression after every change, and how version control differs from change control.

In short: testing climbs in levels: unit testing checks one component, integration testing checks that components and interfaces work together, system testing checks the whole system against the requirements, and user acceptance testing (UAT) lets the users confirm it fits their real work. Regression testing repeats tests after a change to make sure nothing that worked is broken. Load testing checks behaviour under expected traffic; stress testing pushes beyond it to see how and where the system fails.
The four levels Side by side Regression Load and stress Other tests Version and change control Common mistakes Summary Sources

What are the levels of testing?

  1. Unit testing: the smallest piece, a function or a screen component, tested on its own, usually by the developer or the analyst who built it.
  2. Integration testing: pieces tested together, above all the interfaces between systems: does an admission in registration reach the lab, and does the lab result come back to the right patient's chart?
  3. System testing: the complete system tested against the requirements, functional and non-functional, by the project's testers. End-to-end (integrated) testing follows a whole workflow across systems, from registration to order, result and bill.
  4. User acceptance testing (UAT): the people who will use the system run real scenarios with realistic data and confirm it supports their work. Their sign-off is usually a condition for go-live.

The four levels side by side

LevelWhat is testedUsually done byThe question
UnitOne componentThe developer or builderDoes this piece work?
IntegrationComponents and interfaces togetherDevelopers and interface analystsDo the pieces work together?
SystemThe whole system against the requirementsThe project's test teamDoes it do what was specified?
User acceptance (UAT)Real workflows with realistic dataThe future usersDoes it fit the way we work?

What is regression testing, and when is it needed?

Regression testing re-runs tests that passed before, after any change: a fix, an upgrade, a new interface, a configuration change. It answers one question: did the change break something that used to work? In health IT it matters after every vendor upgrade, because a change in one module can affect order sets, alerts or interfaces elsewhere. Teams keep a set of regression scripts, and automate them where they can.

How do load testing and stress testing differ?

  • Load testing: simulates the expected number of users and transactions, including the normal peak (the morning rounds, the start of a clinic), and checks that response times stay acceptable.
  • Stress testing: pushes far beyond the expected load, or removes resources, to find the breaking point: how the system fails, what fails first, whether data stays intact, and whether it recovers on its own. Before a campaign that may bring a wave of patients to the portal, a stress test shows what happens if the wave is larger than planned.
  • Volume testing: large amounts of data, such as years of results in one chart or a big report.

What other tests matter for a clinical system?

  • Usability testing: clinicians try tasks while the team watches for confusion and extra clicks.
  • Security testing: vulnerability scans and penetration tests, where a tester attempts an attack the way an attacker would, with permission.
  • Failover and recovery testing: switch to the backup system on purpose and restore from backups, to prove the disaster recovery plan works.
  • Parallel testing: run the same cases through the old and the new system and compare the results, common for billing and lab calculations.

Tests run in a test environment separate from production, with test data that is synthetic or de-identified, and every defect is logged with its severity. Go-live is decided on agreed criteria, for example "no open critical defects", not on a date alone.

How does version control differ from change control?

  • Version control (for example with Git) records every version of code or configuration: who changed what and when, lets several people work at once, flags a merge conflict when two people edit the same lines, and makes it possible to go back to an earlier version.
  • Change control (change enablement in ITIL) decides whether a change may go into the live system: it is assessed, tested, authorised and scheduled.

The first keeps the history of the work; the second governs what reaches production. A team needs both.

What do candidates get wrong?

  • Letting the developers do UAT. Acceptance testing is done by the future users, on their real workflows.
  • Skipping regression after a "small" change. Small changes break distant things; regression testing is how that is found before users find it.
  • Swapping load and stress. Load: expected traffic and normal peaks. Stress: beyond the limits, to see how it breaks.
  • Testing interfaces only on their own. Integration and end-to-end tests follow the data across systems.
  • Using real patient data in test without need. Test data should be synthetic or de-identified, or protected like production.
  • Swapping version control and change control. Version control keeps versions; change control approves what reaches production.

Summary for revision

  • Levels: unit (one piece), integration (pieces and interfaces), system (whole, against requirements), UAT (users, real work).
  • Regression: after every change, re-run what passed before.
  • Load = expected traffic; stress = beyond the limits, how it fails and recovers.
  • Also: usability, security (penetration), failover and recovery, parallel tests; in a separate test environment.
  • Version control keeps the history; change control approves what goes live.

Sources

  • ISO/IEC/IEEE 29119, Software and systems engineering: Software testing; and the ISTQB glossary: test levels and test types.
  • NIST Special Publication 800-115, Technical Guide to Information Security Testing and Assessment.

Related free practice questions

  • Stress testing: how does the system break?
  • Version control versus change control

The site files this concept under the domain Healthcare Information and Systems Management.

Try exam-style questions

A 20-question trial exam with an explanation for every option and a score per domain, drawn from 40 free questions. No payment method needed.

Start the trial exam

Questions about the exam: CPHIMS guide · What is CPHIMS? · Exam cost · Eligibility · Passing score · Renewal · Exam day · How long to study · Is it worth it? · What is CAHIMS?

Concepts explained: HL7 v2 vs FHIR · Capitation vs fee-for-service · Safe Harbor vs Expert Determination · Incident vs problem vs change · Backup types, RTO and RPO · Privacy Rule vs Security Rule · CDS five rights · Lewin vs Kotter · SDLC and go-live strategies · Earned value (SPI, CPI) · Structure, process, outcome · HIE models · Six Sigma vs Lean · Levels of interoperability · Bandwidth vs latency · EMTALA · Risk responses · RACI matrix · Build vs buy · Sunk vs opportunity cost · Data governance

The four domains: Healthcare and Technology Environments · Clinical Informatics · Healthcare Information and Systems Management · Management and Leadership

Written by Adel Moustafa, About us

Written and checked against the sources above on 22 October 2026. An independent site, not affiliated with or endorsed by HIMSS. CPHIMS® is a registered trademark of HIMSS.

CPHIMS guide Compare certifications Free practice questions Concepts explained About us Terms of Use Privacy Policy Refund Policy Contact us

© 2026 HealthITPrep. This site is not affiliated with or endorsed by HIMSS. CPHIMS is a registered trademark of HIMSS.