HospitalRun - Manual Testing
Manual QA testing project for HospitalRun, an open-source, offline-first hospital management system, focused on validating UI/UX quality and core workflow reliability.
📌 Project Description
HospitalRun is an open-source hospital management system designed to provide offline-first solutions for hospitals in developing countries, and is open for partnerships and contributions from the community. This project focuses on the manual testing of the HospitalRun UI and UX to ensure a smooth, reliable, and efficient user experience across the platform.
Website Overview
The HospitalRun website is a comprehensive hospital management platform designed to simplify administrative and clinical workflows. It offers essential features such as:
Patient Management — registering, viewing, and updating patient records Appointment Scheduling — booking and managing patient appointments Medical Records — maintaining clinical history and documentation Inventory Tracking — managing hospital supplies and stock levels
Built with a modern front-end framework, the platform aims to provide a clean, user-friendly experience for hospital staff working in both online and offline environments.
Core Objectives:
Validate that core hospital workflows (patient management, scheduling, records, inventory) function correctly and reliably Identify UI/UX friction points that could slow down hospital staff in real-world, time-sensitive settings Ensure the platform behaves predictably across positive, negative, and edge-case scenarios Support the open-source project with clear, actionable QA feedback for contributors and maintainers 🛠️ Tech Stack Used Tool / Technique Purpose Manual Testing Validating UI/UX flows and overall usability Exploratory Testing Uncovering edge cases and usability gaps beyond scripted test cases Test Case Design (Positive/Negative/Edge Case) Structured functional coverage Bug Tracking Tool (e.g., GitHub Issues / JIRA) Logging, tracking, and prioritizing defects Browser DevTools Inspecting UI behavior and reproducing issues Screenshots / Screen Recording Supporting evidence for bug reports 🚀 Setup & Installation
This was a manual testing engagement rather than an automation framework, so there's no code to install or run. To reproduce or continue this testing effort:
Access the application Open the HospitalRun website/app in a supported browser (Chrome/Firefox recommended), or set up a local instance from the HospitalRun GitHub repository if testing against a self-hosted build. Review test scenarios Refer to the test case documentation covering: Patient Management (add/edit/search patient records) Appointment Scheduling (create, reschedule, cancel appointments) Medical Records (create/view/update clinical documentation) Inventory Tracking (add stock, update quantities, low-stock scenarios) Execute test cases Follow each test case's steps and expected results. Mark each as Pass/Fail and capture screenshots for any failures. Log defects For any failed test case or UX issue, raise a bug report including: Steps to reproduce Expected vs. actual result Screenshot/recording Severity/priority level Track resolution Follow up on reported issues through the bug tracking tool until verified as fixed. ✨ Key Features & Highlights UI/UX-focused testing — Beyond pure functional checks, testing emphasized usability: how intuitive and efficient the platform is for hospital staff under real-world, time-sensitive conditions. Coverage across core hospital workflows — Patient management, appointment scheduling, medical records, and inventory tracking were all tested for reliability and correctness. Structured bug reports — Every reported defect includes clear reproduction steps, severity classification, and supporting screenshots. Open-source contribution mindset — Feedback was documented in a way that's useful to the HospitalRun community and maintainers, supporting the project's collaborative, offline-first mission.
Author
Rahul Chandeshware GitHub: github.com/Rahulchandeshware