feat: Migrate Selenium + TestNG (Java/Maven) to Playwright (TypeScript)

[devin-ai-integration]

Summary

Complete migration of the test automation framework from Selenium + TestNG (Java/Maven) to Playwright (TypeScript).

What changed

Page Object Model preserved:

• BasePage.java → pages/base.page.ts — WebDriver + FluentWait replaced by Playwright Page with auto-wait
• GooglePage.java → pages/google.page.ts — @FindBy(name="q") → page.locator('[name="q"]')
• FacebookLoginPage.java → pages/facebook-login.page.ts — @FindBy(id=...) → page.locator('#...')

Tests converted:

• GoogleSearchTest.java → tests/google-search.spec.ts
• FaceBookLoginTest.java → tests/facebook-login.spec.ts

Framework infrastructure eliminated (replaced by Playwright built-ins):

• ExtentReports → Playwright HTML reporter
• Log4j → Trace viewer + console output
• WebDriverContext (ThreadLocal) → Playwright fixtures (automatic per-worker isolation)
• PageinstancesFactory → Direct new Page(page) construction
• ReportListener / LogListener → Built-in reporter config
• MailUtil / TestProperties → CI-level notifications / env vars

Optimization configured:

• Cross-browser testing: Chromium, Firefox, WebKit
• Parallel execution: fullyParallel: true
• Trace collection: on-first-retry
• Screenshot on failure: only-on-failure
• Video recording: on-first-retry

Documentation:

• MIGRATION_PLAN.md — Component analysis, risk assessment, language decision rationale
• MIGRATION_RUNBOOK.md — Pattern conversion reference, gotchas, framework comparison, team recommendations

Language decision: TypeScript over Java

Playwright TypeScript was chosen because the built-in test runner eliminates ~600 LOC of framework infrastructure (WebDriverContext, ExtentReportManager, listeners, factories). See MIGRATION_PLAN.md Section 3 for full rationale.

Code reduction

• Before: 16 Java files + 4 XML configs (~700 LOC framework)
• After: 5 TypeScript files + 1 config (~120 LOC framework)
• External deps: 6 Maven → 3 npm

Review & Testing Checklist for Human

• Run npm install && npx playwright install --with-deps then npm test to verify tests execute across all 3 browsers
• Review MIGRATION_PLAN.md for accuracy of the existing framework inventory
• Verify Page Object locators match the target sites (Google search input [name="q"], Facebook #email / #pass)
• Check MIGRATION_RUNBOOK.md pattern conversion tables for completeness — add any project-specific patterns your team uses
• Review playwright.config.ts settings (timeouts, retries, parallel workers) and adjust for your CI environment

Recommended test plan:

1. Clone the branch and run npm install && npx playwright install --with-deps
2. Run npm test — expect 6 tests (2 specs × 3 browsers). Google search test should pass; Facebook test verifies URL after invalid login.
3. Run npm run test:headed to see browser execution visually
4. Run npm run report to view the HTML report

Notes

• The original Java/Maven files (src/, pom.xml) are preserved in the repo — they were not deleted to allow side-by-side comparison during review. They can be removed in a follow-up PR.
• The Facebook login test was originally an intentional failure (Assert.assertTrue(false)). The migrated version tests meaningful behavior instead (verifying the URL remains on facebook.com after invalid credentials).
• No Postgres, ALM, or database integrations were found in the original codebase, so none needed migration.

Link to Devin session: https://partner-workshops.devinenterprise.com/sessions/660fda71a9ee47718f4fba4cc27c9bf3
Requested by: @bsmitches

---

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring