Removes Playwright testing setup, configurations, and related dependencies from the core project.
Introduces a dedicated 'playwright-tests' directory to contain the testing framework, isolating test-related dependencies and configurations from the core application.
This change aims to keep the core project lean and focused on application logic while promoting a more modular and maintainable testing approach.
Implements a custom Playwright reporter to integrate with Jira.
This reporter automatically creates/updates test case and bug subtasks in Jira based on Playwright test results. It also uploads the ortoni HTML report to the parent Jira card.
Key features:
- Creates a regression card if none are found
- Transitions test subtasks based on test results.
- Creates bug subtasks for failed tests.
- Uploads the Ortoni HTML report as an attachment to the Jira card.
- Configurable through environment variables (Jira server, username, API key, project key, etc.).
Also adds axios-retry to handle rate limiting errors from Jira API
Sets up the core infrastructure for Playwright-based automated testing, including:
- Docker support for consistent environments
- Azure Pipelines configuration for CI/CD
- Page Object Model structure for maintainable tests
- Test data, validation, and rule engine implementation
- Test configuration for alerts and other scenarios
Initial commit of the Playwright test framework, including:
- Configuration files for Playwright, Docker, and Sauce Labs
- Test case structure and page object models
- CI/CD pipeline configuration
- Utilities and business logic implementations
This framework will be used for end-to-end testing of the FMG application.
