A Day in the Life of a QA Working on a Medical App

🩺 A Day in the Life of a QA Working on a Medical App

Working in QA for a medical application isn’t just about writing test cases — it’s about ensuring patient safety, data privacy, and compliance with healthcare regulations. Here's what a typical day looks like for me:

🕘 9:00 AM – Morning Standup

We start the day with a daily stand-up call. The product team, developers, and QAs share updates. For me, this is the time to raise concerns about yesterday’s test results or any blockers in automation runs.

📄 10:00 AM – Reviewing Requirements

Before diving into testing, I read through user stories and FSDs (Functional Spec Documents). In the medical domain, I verify that all HIPAA compliance notes and audit trail requirements are clear.

🧪 11:00 AM – Manual Testing Critical Flows

I start by manually testing critical flows like patient registration, appointment booking, EMR (Electronic Medical Records) viewing, and prescription generation. I focus on edge cases, validation, and field-level security.

💻 1:00 PM – Automation Script Review

Post-lunch, I review the automated Selenium + Java test cases that ran on Jenkins overnight. If any failed, I analyze logs, screenshots, and check whether the failure is due to flaky scripts or actual application issues.

📲 2:30 PM – API Testing with Postman

I test appointment APIs, authentication tokens, and data sync endpoints using Postman. For medical apps, secure transmission of patient data (often in JSON or HL7 format) is critical.

🛡️ 4:00 PM – Compliance & Security Checklist

I perform checks for access control, role-based permissions (Doctor, Nurse, Admin, Patient), and ensure error messages don’t leak sensitive data. I also check that sessions time out securely and that data is encrypted at rest.

📋 5:30 PM – Bug Reporting & Test Case Updates

By end of day, I log all bugs found in Jira, update the test case execution sheet, and document regression impacts if needed. I also prepare for the next day’s test plan and share a status update with the team.

🔚 Final Thoughts

Being a QA in a healthcare app requires technical expertise and a sense of responsibility. One bug can impact real people’s health — so attention to detail and rigorous validation is not optional, it’s mandatory.

If you're working in or planning to join healthcare QA, let me know your experiences or doubts in the comments!

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

Case Study: Testing a Food Delivery App (Real Project Tasks)

📦 Case Study: Testing a Food Delivery App (Real Project Tasks)

In this case study, I’ll walk you through how I tested a real-world food delivery application, covering the different types of testing I performed and the actual modules I worked on.

📱 Application Overview

• Platform: Web and Mobile App (iOS & Android)
• Users: Super Admin, Restaurant Admin, Customer, Delivery Boy
• Tech Stack: React, Node.js, MongoDB, Firebase

🧪 Testing Types Performed

• Functional Testing – Verified core features like order placement, payment, and delivery flow.
• UI Testing – Checked responsiveness, alignment, and element visibility across devices.
• Regression Testing – After each deployment or feature enhancement.
• Cross-Browser Testing – Chrome, Firefox, Safari compatibility for web interface.
• API Testing – Used Postman to validate RESTful endpoints for user login, orders, and menu updates.

🧑‍💻 Modules Tested

• 🔐 User Registration & Login (OTP & Email-based)
• 🍔 Restaurant Menu Management (CRUD operations)
• 🛒 Cart & Checkout Flow (Add, remove items, promo codes)
• 💳 Payment Integration (Razorpay/Stripe sandbox testing)
• 🚴 Order Assignment to Delivery Boys
• 📍 Real-Time Order Tracking (Google Maps)
• 📊 Admin Dashboard Analytics & Reports

📝 Sample Test Case Table

Test Case	Expected Result	Status
The user places an order with a valid payment	The order should be accepted and visible in the order history	Pass
The delivery boy accepts the order	Status changes to "Out for delivery"	Pass
Invalid promo code applied	Display appropriate error message	Pass

🐞 Bugs Found

• Promo code applied multiple times in the cart
• The order tracking map is not loading on iOS
• Menu item image upload fails on slow network
• Delivery boy app crashes on auto logout

🔚 Conclusion

This project helped me gain practical experience in end-to-end QA for a multi-user food delivery ecosystem. It involved API testing, real-time validations, UI cross-checks, and regression cycles. A strong reminder that good testing means thinking like both the customer and the developer.

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

Postman vs Swagger – Which Is Better for QA?

Postman vs Swagger – Which Is Better for QA?

In the world of API testing, Postman and Swagger (now called Swagger UI / OpenAPI) are two of the most commonly used tools by QA professionals. Each tool offers different benefits depending on your project needs, technical skills, and integration with development workflows.

What Is Postman?

• A powerful GUI-based tool for testing REST APIs.
• Supports scripting (Pre-request, Tests), environment variables, and automation.
• Easy to use for manual testing and automation with the Postman Collection Runner and Newman CLI.

What Is Swagger?

• A framework for API design, documentation, and testing using the OpenAPI Specification.
• Swagger UI provides interactive documentation.
• Swagger Editor allows you to define and mock APIs before development.

Postman vs Swagger: Feature Comparison

Feature	Postman	Swagger
Best For	QA Testing and Automation	API Design and Documentation
Ease of Use	Very User Friendly	Requires YAML/JSON knowledge
Automation	Supports via Collection Runner, Newman	Limited built-in automation
API Mocking	Supported via Postman Mock Servers	Supported
Integration	Jira, Jenkins, GitHub, etc.	Mostly with Dev Tools

When to Use Postman?

• You're a QA tester needing quick, efficient REST API testing.
• You need to run test collections and automate regression API testing.
• You work in Agile/Scrum where endpoints change frequently.

When to Use Swagger?

• You are part of the development team responsible for API documentation.
• You want to design APIs before implementation.
• You want developers and testers to visualize endpoints in one place.

Final Verdict

Use both! Postman and Swagger complement each other. Swagger is great for API documentation and early design, while Postman is better for actual testing, validation, and automation.

💡 Pro Tip: Many teams use Swagger to define APIs and Postman to test them.

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

Top 5 Selenium Interview Questions – With Code Answers

🚀 Top 5 Selenium Interview Questions – With Code Answers

If you're preparing for a QA Automation role using Selenium, here are the most frequently asked Selenium interview questions along with practical code answers using Java and TestNG.

---

1️⃣ What is Selenium WebDriver? How do you launch a browser using it?

Answer: Selenium WebDriver is a tool for automating web application testing. It provides a programming interface to interact with web elements.

WebDriver driver = new ChromeDriver();
driver.get("https://www.google.com");

---

2️⃣ How to handle dropdowns in Selenium?

Answer: You can use the Select class to handle dropdowns.

WebElement dropdown = driver.findElement(By.id("country"));
Select select = new Select(dropdown);
select.selectByVisibleText("India");

---

3️⃣ How to handle Alerts in Selenium?

Answer: Selenium provides the Alert interface to handle JavaScript alerts.

Alert alert = driver.switchTo().alert();
System.out.println(alert.getText());
alert.accept();

---

4️⃣ What is the difference between driver.close() and driver.quit()?

• close(): Closes the current active window.
• quit(): Closes all the windows opened by WebDriver and ends the session.

---

5️⃣ How to perform mouse hover action in Selenium?

Answer: Use the Actions class for mouse interactions.

Actions actions = new Actions(driver);
WebElement element = driver.findElement(By.id("menu"));
actions.moveToElement(element).perform();

---

💡 Bonus Tip

Always combine Selenium with TestNG or JUnit for structured automation testing and reporting. Employers prefer candidates who can write modular, reusable test scripts.

📌 Stay tuned for more Selenium QA interview series!

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.

Checklist for Web Application Testing Before Release

✅ Checklist for Web Application Testing Before Release

Before launching your web application, it's essential to go through a comprehensive testing checklist to ensure quality, functionality, performance, and security. Here's a step-by-step checklist every QA should follow.

1. Functional Testing

• All forms are submitting data correctly
• Input field validations work properly
• Navigation links and buttons function as intended
• Error messages and success alerts are user-friendly
• Business logic flows are verified

2. UI/UX Testing

• Layout is consistent across all pages
• No overlapping or broken UI elements
• Responsive design works on all screen sizes (mobile/tablet/desktop)
• Fonts, colors, and branding match the design guidelines

3. Cross-Browser Testing

• Test in major browsers: Chrome, Firefox, Safari, Edge
• Ensure consistency in layout and behavior

4. Compatibility Testing

• Test on different operating systems: Windows, macOS, Android, iOS
• Verify performance and usability on various devices

5. Performance Testing

• Check page load time under normal and heavy load
• Verify backend response time
• Conduct stress and scalability testing

6. Security Testing

• Check for SQL injection, XSS, CSRF vulnerabilities
• Ensure login, registration, and password reset are secure
• Verify HTTPS implementation and SSL certificate validity

7. Usability Testing

• Test for ease of navigation
• Ensure error handling is user-friendly
• Check for accessibility compliance (Alt tags, keyboard navigation)

8. Integration Testing

• Third-party services (payment gateway, APIs) work properly
• Backend and frontend communication is stable

9. Regression Testing

• Re-run critical test cases after recent code changes
• Ensure new features didn’t break existing functionality

🔚 Final Thoughts

Use this checklist before every major release to catch issues early and ensure a smooth user experience. A well-tested application reduces customer complaints and increases trust.

👋 Hi, I'm Suriya — QA Engineer with 4+ years of experience in manual, API & automation testing.

📬 Contact Me | LinkedIn | GitHub

📌 Follow for: Real-Time Test Cases, Bug Reports, Selenium Frameworks.