Bhavani Jinde

Quality Engineer
4years leading teams
6/10Test Automation Frameworks
2years in tech
10people in the team led

Overview

E2E UI Automation Engineer specializing in Playwright + Java testframeworks at a Senior level with focused strengths in reliable failure diagnostics and selector discipline. The strongest proven skill is engineering robust UI evidence and trace capture for failing tests as implemented in BaseTest.java (tracing, screenshots, describePage) and the centralized Locators.java selector strategy. There is limited or no public evidence of contract/API testing, load/perf testing, CI matrix configurations, or formal mutation/property-based tests in the code reviewed.
Phone

Timeline

Software Quality Engineer · Middle
ServiceNow Software Development India Pvt Ltd · Full-Time
Aug 2024 to Present Hyderabad In office
Owned end-to-end quality for data lifecycle and attachment partition features, from requirement review through release sign-off. Drove regression coverage using Playwright with Java and JUnit, and triaged failures in weekly CI/CD pipelines. Extended Java-based automation utilities and used AI/LLM (including MCP) to accelerate test design and support code review and defect triage. Validated large-scale attachment data migration and fixed UI/label integration test defects after QE to Dev transition.
Java
Playwright
JUnit
CI/CD
Jira
Model Context Protocol
LLM
Quality Engineer · Middle
Thrayakshari Pvt Ltd · Full-Time
Oct 2022 to Apr 2024 1 Year 6 Months In office
Led functional and regression testing for core product modules such as Contacts, Campaigns, Templates, Subscriptions, and Performance, focusing on catching issues before production. Authored manual test cases and built targeted UI automation scenarios using Selenium with a Page Object pattern and Cucumber BDD. Triaged, documented, and tracked defects to closure with developers using JIRA, improving release stability.
Selenium
Jira
Associate · Middle
Genpact · Full-Time
Feb 2022 to Jul 2022 5 Months In office
Worked on an image impact annotation project by analyzing textual descriptions and identifying corresponding objects in paired images. Produced accurate labels and markings to meet data annotation requirements supporting downstream data usage.

Technical skills

Java
QA
Selenium
Playwright
Postman
AI/ML
LLM
Model Context Protocol
Claude Code
Prompt Engineering
DevOps
CI/CD
GitHub Actions
Mobile
JUnit
Databases
MySQL
Junior QA Engineer Confidence: Medium Automation Engineer
E2E UI Automation Engineer specializing in Playwright + Java testframeworks at a Senior level with focused strengths in reliable failure diagnostics and selector discipline. The strongest proven skill is engineering robust UI evidence and trace capture for failing tests as implemented in BaseTest.java (tracing, screenshots, describePage) and the centralized Locators.java selector strategy. There is limited or no public evidence of contract/API testing, load/perf testing, CI matrix configurations, or formal mutation/property-based tests in the code reviewed.
Test Automation Frameworks
6/10
Building automated tests
Test automation framework with deliberate architecture: page objects, a single selector file, session reuse, tracing and per-test evidence capture; good selector discipline and conditional waits rather than sleeps.
Evidence
jindebhavani347-art/proton-mail-automation/src/test/java/com/qa/proton/core/BaseTest.java: tracing start/stop, captureScreenshots(), describePage() jindebhavani347-art/proton-mail-automation/src/test/java/com/qa/proton/pages/Locators.java: centralized selector strategy and data-testid preference jindebhavani347-art/proton-mail-automation/src/test/java/com/qa/proton/pages/MailboxPage.java: waitForMessage() with deadline/refresh loop (conditional wait instead of sleep)
Test Coverage & Strategy
5/10
What and how to test
Evidence of structured E2E coverage and test patterns (tagging, parameterized and repeated tests, negative-path assertions) and explicit failure-evidence handling; lacks strong evidence of risk-based prioritization artifacts embedded in code or property-based tests.
Evidence
jindebhavani347-art/proton-mail-automation/src/test/java/com/qa/proton/tests/ComposeTests.java: ParameterizedTest / RepeatedTest imports and use jindebhavani347-art/proton-mail-automation/src/test/java/com/qa/proton/tests/AuthenticationTests.java: negative-path authentication assertions and @Tag usage jindebhavani347-art/orangehrm-playwright-tests/src/test/java/com/consoletest/config/LeaveApply.java: negleavepage() shows explicit negative-path assertion on an error element
API & Integration Testing
1/10
Testing how parts work together
Almost no contract/API testing or schema-driven contract assertions; mostly UI-driven E2E automation; only lightweight integration evidence (metrics capture) is present.
Evidence
jindebhavani347-art/proton-mail-automation/src/test/java/com/qa/proton/utils/Metrics.java: delivery-latency metrics writing (metric collection rather than API contract testing)
Performance & Load Testing
1/10
Testing speed under load
No real performance/load testing artifacts or SLO-driven scenarios; metrics collection exists but there are no k6/locust/gatling style load scenarios or percentile analysis.
Evidence
jindebhavani347-art/proton-mail-automation/src/test/java/com/qa/proton/utils/Metrics.java: file-based metrics emission (evidence of metric capture but not load testing)
Bug Reporting & Analysis
3/10
Finding and describing bugs
Good test failure evidence collection (screenshots, traces, page dumps) which aids bug triage; no public bug reports or linked root-cause analyses are present.
Evidence
jindebhavani347-art/proton-mail-automation/src/test/java/com/qa/proton/core/BaseTest.java: captureScreenshots(), tracing.stopChunk(...) and describePage() for diagnostics jindebhavani347-art/proton-mail-automation/src/test/java/com/qa/proton/core/BaseTest.java: AfterTestExecutionCallback extension that records the current test name and captures evidence on failure
CI Test Integration
3/10
Running tests automatically
Evidence for per-test artifacts and failure artifact handling suitable for CI (traces, screenshots), but no visible CI workflow files, matrix configuration, or selective diff-based test running in code.
Evidence
jindebhavani347-art/proton-mail-automation/src/test/java/com/qa/proton/core/BaseTest.java: traces and screenshots saved under reports (kept on failure) jindebhavani347-art/proton-mail-automation/src/test/java/com/qa/proton/core/SessionManager.java: centralized session and tracing management for test runs
Expertise
SDET & Test Engineering· Junior
Technologies
Java· since 2024 · Junior
Selenium· since 2022
Playwright· since 2024
Postman
Recommendations
  • Extend the framework to include API/contract tests (schema validation or schemathesis/pact-style) and surface contract failures as part of the pipeline.
  • Add CI configuration (matrix, selective test runs by diff, per-test retries/quarantine rules) and enable parallel sharding or containerized nodes to shorten feedback loops.
  • Introduce explicit flake engineering: convert fragile waits into condition-based helpers, create quarantine markers and per-test retry rationale, and add flaky-test telemetry.
  • Add performance/load test scenarios (k6/Gatling/locust) and integrate Metrics output into a time-series store (Prometheus/Grafana) to establish SLOs for delivery latency.
Repositories
The developer's experience in this domain has been verified based on AI analysis of the following repositories:
proton-mail-automation orangehrm-playwright-tests

Job preferences

Work permits
India
Citizenship
India
Employment type
Full-Time
Open to AI agents: they read this profile and start a dialog through Alionalion.io/@bhavani-jinde/mcp
Alion · People, companies and AI agents in one graphalion.io/@bhavani-jinde