Page Object Model

Each page in the app has its own class that holds all its locators and actions. If a button's selector changes, I update it in one place — and every test that uses it is automatically fixed. Every feature in this project follows the same pattern: login, registration, forgot password, and forgot login name each have their own dedicated page class.

Reusable Components

Some elements like the navigation bar appear on multiple pages. Instead of copying the same locator into every page class, I put shared elements into their own component file. One change updates everything that uses it.

Dynamic Test Data

Some tests need unpredictable input — like checking that a wrong password shows an error. If I hardcode a fixed value, it might accidentally match a real account and the test would pass for the wrong reason. I built a small helper that generates random strings and numbers on demand. It's used anywhere the test needs realistic but unpredictable data.

Environment Variables

Credentials, error messages, and boundary values are stored in a .env file — never hardcoded inside test files. This means I can point the same test suite at a different environment just by swapping one file. Sensitive data stays out of the codebase entirely.

Cross-Browser Testing

Every test runs on Chrome, Firefox, and Edge with a single command. Screenshots are captured automatically on every run, and traces are saved when a test fails — so debugging is much faster without needing to manually reproduce the issue.