auto-added

automation/playwright/readme.md

@@ -0,0 +1,71 @@
+Playwright E2E Testing — Anonymized Case Study
+
+This is an anonymized excerpt from an enterprise E2E automation project.
+
+The original project is proprietary and cannot be published.
+The code has been sanitized to remove company-specific data, credentials, URLs and internal implementation details.
+
+Stack
+
+* Python
+* pytest
+* Playwright
+* Allure
+* Axe / axe-core
+
+Covered scenarios
+
+Authentication
+
+* valid credentials
+* invalid username
+* invalid password
+* empty fields
+* invalid characters
+* boundary/long input
+* error state validation
+
+Password recovery
+
+* valid login/email
+* invalid email
+* unknown user
+* form validation
+* email notification
+* security questions
+* cooldown/retry behavior
+
+Accessibility Testing
+
+Accessibility checks were automated using Axe / axe-core as part of the E2E test suite.
+
+Covered UI states include:
+
+* login page
+* password recovery form
+* security questions
+* validation/error states
+* dark theme
+
+The accessibility checks are executed against different application states rather than only the initial page, helping detect accessibility regressions introduced by dynamic UI changes.
+
+Security questions
+
+* unique questions validation
+* valid answers
+* invalid answers
+* duplicate question detection
+* retry/cooldown timer
+
+Testing approach
+
+* Page Object Model
+* parametrized tests
+* positive/negative testing
+* UI validation
+* accessibility testing with Axe
+* asynchronous email verification
+* business-rule validation
+* explicit assertions
+* dynamic UI state validation
+* E2E validation across multiple application components