$ cat shreyas.json
{
  "name": "Shreyas Bhagat",
  "title": "Software Quality Assurance Engineer",
  "location": "India",
  "experience": "3+ years in Healthcare & Insurance domains",
  "philosophy": "A negative thinker who takes software testing seriously",
  "specialties": ["Manual Testing", "Automation", "API Testing", "Database Testing"],
  "currentFocus": "Backend Automation, AI-assisted testing, workflow automation with N8N",
  "funFact": "I play Football! ⚽"
}

By the numbers:

What I bring to the table:

• 🧑‍💼 Led a team of 3+ QA engineers — task allocation, test planning, code reviews and mentoring
• 🎓 Onboarded and trained 3+ junior QA engineers on framework usage and best practices
• 📋 Reviewed and signed off test cases written by junior team members
• 🔧 Designed and maintained Selenium + TestNG + Maven framework — 165+ automated tests, zero flaky tests in production
• ⏱️ Reduced regression cycle from 1 day → ~3 hours via Azure DevOps pipeline
• 🌐 Validated 20+ REST/SOAP APIs using RestAssured and Postman
• 🗄️ Executed database validation across SSMS to ensure end-to-end data integrity
• 🔄 Contributed across 30+ Agile sprints — planning, standups, retrospectives, demos

Privacy-first tool that generates structured manual test cases using local Llama 3.2 — no cloud APIs, your data never leaves your machine

End-to-end manual QA of an open-source e-commerce platform covering the full user journey

Key Highlights:

• 📝 200+ test cases covering registration, login, cart, checkout & admin panel
• 🐛 37 bugs reported with severity, priority & steps to reproduce
• 📦 Deliverables: Test Plan · RTM · Bug Reports · Test Summary Report

Comprehensive manual testing of a net banking application (Guru99) based on SRS v1.3

Key Highlights:

• 🏗️ Scope: Account management, fund transfers, transaction history & user roles
• 📋 Requirement-based test case design from formal SRS v1.3 documentation
• 📁 Deliverables: Unit & Integration test cases · Bug tracker · RTM · SRS

Robust, scalable UI automation framework built from scratch for the Magento 2 Luma e-commerce theme

Key Highlights:

• 🏗️ Page Object Model with custom ActionDriver Selenium wrapper (waits, hover, scroll)
• 📊 Data-driven testing via Apache POI reading .xlsx test scenarios
• 🔍 End-to-end checkout, user registration & product search test suites
• 📋 Extent HTML reports with failure screenshots + Log4j2 logging

Page Object Model framework integrated with Jenkins CI/CD, built for a Healthcare domain application

Key Highlights:

• 🏗️ Architecture: Page Object Model (POM) with Factory pattern
• 📊 Reporting: Extent Reports + TestNG HTML reports
• 🔁 CI Integration: Jenkins pipeline with email alerts on failure
• 🧪 Test types: Smoke · Regression · Cross-browser · Parallel execution

🔒 Code is private due to company policy. The real code pattern from this framework is shown in the section below — happy to walk through the full architecture in an interview.

The actual design pattern from my automation framework. Not pseudocode.

// LoginPage.java — Page Object with explicit waits and fluent return types
public class LoginPage {

    private WebDriver driver;
    private WebDriverWait wait;

    @FindBy(id = "input-email")           private WebElement emailField;
    @FindBy(id = "input-password")        private WebElement passwordField;
    @FindBy(css = "input[value='Login']") private WebElement loginButton;
    @FindBy(css = ".alert-danger")        private WebElement errorMessage;

    public LoginPage(WebDriver driver) {
        this.driver = driver;
        this.wait = new WebDriverWait(driver, Duration.ofSeconds(10));
        PageFactory.initElements(driver, this);
    }

    public DashboardPage loginAs(String email, String password) {
        wait.until(ExpectedConditions.visibilityOf(emailField));
        emailField.sendKeys(email);
        passwordField.sendKeys(password);
        loginButton.click();
        return new DashboardPage(driver);
    }

    public String getErrorMessage() {
        wait.until(ExpectedConditions.visibilityOf(errorMessage));
        return errorMessage.getText();
    }
}

// LoginTest.java — TestNG test class consuming the page object
public class LoginTest extends BaseTest {

    @Test(description = "Valid login should redirect to dashboard")
    public void validLoginTest() {
        LoginPage loginPage = new LoginPage(driver);
        DashboardPage dashboard = loginPage.loginAs(
            Config.get("valid.email"),
            Config.get("valid.password")
        );
        Assert.assertTrue(dashboard.isLoaded(), "Dashboard did not load after login");
    }

    @Test(description = "Invalid credentials should display error message")
    public void invalidLoginTest() {
        LoginPage loginPage = new LoginPage(driver);
        loginPage.loginAs("wrong@email.com", "wrongpass");
        Assert.assertTrue(
            loginPage.getErrorMessage().contains("Warning: No match"),
            "Expected error message was not displayed"
        );
    }

    @Test(description = "Empty credentials should not redirect to dashboard")
    public void emptyCredentialsTest() {
        LoginPage loginPage = new LoginPage(driver);
        loginPage.loginAs("", "");
        Assert.assertFalse(
            driver.getCurrentUrl().contains("dashboard"),
            "Should not redirect with empty credentials"
        );
    }
}

Open to collaborations, new opportunities, or just a chat about software quality!