Test Cases for Hospital Management System
Test Cases for Hospital Management System (HMS)
Here are various test cases categorized by functionality for an HMS:
1. Patient Management:
Test Case 1: Description: Register a new patient with valid information. Expected Result: Patient registration successful, profile created, and login credentials provided.
Test Case 2: Description: Register a new patient with missing mandatory fields (e.g., name, date of birth). Expected Result: Registration fails with an error message prompting to enter missing information.
Test Case 3: Description: Login to the patient portal with valid credentials. Expected Result: Successful login and access to the patient dashboard.
Test Case 4: Description: Login to the patient portal with invalid username or password. Expected Result: Login fails with an appropriate error message (e.g., "Invalid username/password").
Test Case 5: Description: Search for a specific doctor by name or specialty. Expected Result: System displays a list of matching doctors with relevant details.
Test Case 6: Description: View a patient's medical history after successful login. Expected Result: Patient's medical history is displayed securely with authorized access.
2. Appointment Booking:
Test Case 7: Description: Schedule an appointment with a doctor by selecting a date, time, and appointment type. Expected Result: Appointment confirmed with notification sent to patient and doctor.
Test Case 8: Description: Schedule an appointment with a fully booked doctor. Expected Result: System displays a message indicating doctor's unavailability and suggests alternative dates/times.
Test Case 9: Description: Cancel an existing patient appointment. Expected Result: Appointment cancelled with confirmation message sent to patient and doctor's schedule updated.
Test Case 10: Description: Try to cancel an appointment after the designated cancellation deadline. Expected Result: System displays an error message indicating cancellation is not allowed due to exceeding the deadline.
3. Doctor Management:
Test Case 11: Description: Doctor logs in to the HMS with valid credentials. Expected Result: Successful login and access to the doctor's dashboard.
Test Case 12: Description: Doctor views a list of their upcoming appointments. Expected Result: System displays a list of confirmed appointments with patient details and appointment details (date, time, type).
Test Case 13: Description: Doctor accesses a patient's medical history for a scheduled appointment. Expected Result: Patient's medical history is retrieved and displayed securely for informed consultation.
Test Case 14: Description: Doctor creates a new electronic prescription for a patient after an appointment. Expected Result: Prescription is electronically generated, stored securely, and accessible to authorized personnel (patient, pharmacist).
4. Billing and Insurance:
Test Case 15: Description: Generate a patient bill after a completed appointment. Expected Result: Bill is generated with accurate charges for services rendered, medications prescribed, etc.
Test Case 16: Description: Process a patient's insurance information and verify coverage. Expected Result: System validates insurance details and displays the covered and uncovered portions of the bill.
Test Case 17: Description: Allow a patient to view their medical bill electronically through the patient portal. Expected Result: Patient can access and download a detailed breakdown of their bill.
Test Case 18: Description: Simulate an online payment for a medical bill using a valid credit card. Expected Result: Payment is successfully processed, reflected on the bill, and a confirmation email is sent to the patient.
5. Security Testing:
Test Case 19: Description: Attempt to access the HMS with unauthorized credentials (e.g., random username/password combinations). Expected Result: System denies access and displays an error message.
Test Case 20: Description: Test the system's encryption for sensitive patient data (e.g., medical history) during storage and transmission. Expected Result: Data remains encrypted and unreadable without proper decryption keys.
