Biomap
Role-based end-to-end automation for a wellness platform, built on reusable data-driven components.
- Client
- Ace Infoway Pvt. Ltd.
- Role
- QA Automation Engineer
- Period
- 2023 — 2026
- roles automated
- 4roles automated
- core modules covered
- 5core modules covered
Overview
Wellness platform · Multi-role web application
Biomap serves four distinct roles — Admin, Relationship Manager, Subject Matter Expert and Client — and each of them sees a different version of the same modules. Automating that naively means writing the suite four times. I built it once, data-driven, and parameterised the role.
01
Scope
- Dashboard, Appointments, Billing, Reports and Inquiries
- Full coverage across the Admin, Relationship Manager, Subject Matter Expert and Client roles
- Reusable, data-driven components so a role became a dataset rather than a duplicated suite
02
Approach
Page Object Model with the role supplied as test data rather than baked into the spec. Adding a role meant adding a data row, and a permission change was verified across every module in one run instead of four.
Stack
Automation
- Selenium WebDriver
- Playwright
- Page Object Model
- Data-driven design
Practice
- Regression suites
- Role-based coverage
- Database validation (SQL)
Process
- Agile / Scrum
- Git
- GitLab
- Jira