Relocates CI and Docker configuration files to the root directory.
This change simplifies the project structure by placing these essential configuration files at the top level, making them more accessible and easier to manage.
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
Updates the path for storing test results in the Azure Pipelines configuration.
This ensures that test reports and JUnit results are correctly located
and copied during the automated testing process.
Updates the Azure pipeline configuration to reference the relocated Dockerfile.
This ensures the pipeline correctly identifies and builds the Docker image, preventing build failures.
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.
