Contact us
Healthcare Functional Testing for hospital OR workflow platform

702

Test cases executed across iPad and desktop

13

Functional modules validated end-to-end

36

Failures logged in Jira with test-ID traceability

Overview

OP-Puls, developed by a healthcare software company in Switzerland, is a digital information and workflow system for the operating room. It connects instruments, materials, procedures and team communication in one platform, so that surgical and nursing teams get the right information at the right step of an operation. The platform covers OR briefings, department guides (Handbücher), materials and instrument packages, storage locations, reporting, internal chat and news, and user administration, and it is used both on hospital workstations and on iPads inside the OR.

Testvox ran a focused manual functional and regression testing engagement across the Windows desktop application and the iPad application. The goal was to validate the client’s agreed test checklist end to end, with particular attention to role-based access, material and checklist data integrity, and the iPad behaviours that had historically caused platform-specific defects.

Challenges Faced by Client

  • Clinical workflows where data accuracy is non-negotiable: OR briefings, instrument packages, material sets and lot/batch numbers feed directly into how an operation is prepared. A value that fails to save is not a cosmetic issue in this setting; it is a traceability gap.
  • Layered permissions that had to hold in both directions: The platform distinguishes Admin, Nutzer and Technisch roles, and standard users can additionally be granted department-level editing rights (Fachbereichsverantwortlicher). Testing needed to confirm not only that users could do what they were allowed to, but that restricted actions stayed hidden from everyone else.
  • Two platforms that behave differently: The iPad app had a history of platform-specific defects. Touch input, the on-screen keyboard, scrolling, backgrounding and network loss all behave differently from a desktop workstation, so one platform passing was no guarantee for the other.
  • A German-only interface and a lean engagement model: Every label, error message and role name was in German, and the engagement was deliberately scoped for one QA engineer running a single functional round and a single regression round. Accuracy had to come from structure, not from repeated passes.

Testvox Solution

  1. A Checklist Turned Into Atomic, Traceable Test Cases

    2. Testvox treated every point in the client's checklist as one atomic test case, meaning one action verified against one expected result and tracked by its unique test ID. This produced 326 functional test points across 13 modules, from login and navigation through OR briefings, materials, storage locations, chat and user administration, plus 25 documented regression tests covering known problem areas. Every result was recorded with platform, build number and screen-recording evidence, and every failure was logged in the client's Jira with a direct link back to its test ID.

  2. Role-Based Testing With Positive and Negative Checks

    3. Tests were executed under dedicated accounts for each permission profile: Admin, standard Nutzer, and Nutzer with department-level rights. Role-tagged checks ran under the matching account, and negative checks ("this action must not be visible") ran under the standard user and under a department-level user against a department it had no rights to, confirming that permissions held at the boundary and not just on the happy path.

  3. Platform-Specific Depth on iPad and Desktop

    4. Testvox covered 100% of applicable test points on both platforms, sequentially, and targeted the behaviours each platform is prone to. On iPad, that meant keyboard and scroll interaction in search, session persistence, the automatic-logout boundary when the app is backgrounded, and cold-starting the app with no network. On desktop, it meant drag-and-drop uploads, file attachments in chat and long-text entry in briefing fields.

  4. Language-Aware Validation and Disciplined Scope

    5. Because the interface is fully German, test execution was supported by consultation with a German–English translator, so UI labels, messages and expected results were interpreted correctly rather than approximately. Scope was kept equally disciplined: cases the client chose to exclude were marked as such, and behaviours that differed from the checklist without being clear defects were documented separately for the product team to decide on, instead of being logged as bugs.

Result

Complete Coverage in a Single, Lean Cycle

All 702 functional and regression test cases were executed or reviewed across iPad and desktop within the planned single functional round and single regression round, delivered by one QA engineer. The client received a full execution record per test ID and platform, rather than a sample.

Defects Found Where They Matter Most

The 36 failures traced to Jira clustered in areas with real operational weight, including account and password flows, material traceability data such as lot/batch numbers, chat permissions and message handling, and iPad session and offline recovery. Each came with the originating test ID, platform, build and recorded evidence, so the development team could reproduce and fix without back-and-forth.

A Clear Line Between Bugs and Product Decisions

Rather than inflating the defect count, Testvox documented 18 behaviours that deviated from the checklist without being clear defects, such as two OR briefings being created for the same room and time without a warning, or duplicate department names being accepted. These went to the product team as decisions to make, giving the client an accurate picture of quality instead of a noisy one.

Conclusion

Testing a platform that runs inside the operating room means testing more than whether screens load. It means confirming that briefing and material data is saved exactly as entered, that permissions hold for every role, and that the iPad in a surgeon's or nurse's hands behaves as reliably as the workstation at the desk. By turning the client's checklist into a fully traceable, role-aware, cross-platform test run, Testvox gave the OP-Puls team a complete view of product quality across both platforms, a precise defect log ready for fixing, and a clear separation between what needs repair and what needs a product decision.

Related Resources