fix: bypass actionability checks and set 1080p viewport to prevent ti…

[aakarshitsharma06]

…meouts in headless mode

Summary by CodeRabbit

• Tests
  • Enhanced test automation stability by improving UI interaction reliability across employer login and job-posting flows.
  • Standardized browser viewport configuration for consistent test execution environments.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 6654447c-0d40-4c5c-a2cd-cbeb139e70d2

📥 Commits

Reviewing files that changed from the base of the PR and between e6bae1e and 1ed8522.

📒 Files selected for processing (3)

• pages/AvuaEmployerPage.ts
• playwright.config.ts
• tests/employerLogin.spec.ts

---

📝 Walkthrough

Walkthrough

This PR adds { force: true } to Playwright click actions across the employer page object and login tests to improve interaction reliability. A fixed browser viewport (1920×1080) is configured for consistency. Changes affect login, job-post navigation, form filling, step progression, job publishing, and dashboard navigation without altering test logic.

Changes

Playwright robustness improvements

Layer / File(s)	Summary
Viewport configuration playwright.config.ts	Browser viewport is set to 1920×1080 to ensure consistent test environment dimensions.
Page object force-click pattern throughout job-posting flow pages/AvuaEmployerPage.ts	Login (password tab and sign-in button), job-post page navigation, step 1 form filling (Quill description editor, skills input, skill addition, remote selection), step 2 progression (Continue button, contractor model selection, payment dropdown, hourly selection), step 3 review button, job publishing (fallback Publish button), and dashboard navigation (Jobs tab) all use forced clicks to handle cases where default clicks fail.
Login test cases with forced clicks tests/employerLogin.spec.ts	Test cases TC3–TC7 update password tab, one-time code tab, send sign-in code button, and forgot password link clicks to use { force: true }, while preserving all test assertions and navigation expectations.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• aakarshitsharma06/playwright-avua#1: Both PRs touch the Playwright employer login/job-post automation (notably tests/employerLogin.spec.ts and pages/AvuaEmployerPage.ts), with the main PR updating click invocation behavior ({ force: true }) in the same login/job-post flows that the retrieved PR is fixing/altering.

Poem

🐰 Click, click, force, and flow,
Tests that once were fragile now stand strong!
Viewport fixed, clicks assured to go,
Through login, forms, and jobs all day long. ✨

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chatBot

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}