Adjusts the PayPal purchase completion logic to handle cases where the "Log in with password" option is immediately visible or requires an initial login step with email.
This ensures a more robust and reliable payment process across different PayPal configurations.
Adds username input and "next" button handling to the PayPal login flow.
This update is necessary to support the new PayPal login screen, which requires entering the username before the password.
Adds a commented-out base URL for a local FMG server instance to the development environment configuration.
This allows developers to easily test against a local version of FMG by uncommenting the appropriate line.
Corrects the premium service package description to align with the updated service offering.
The text "Rain Defense™" is replaced with "Rain repel treatment"
for accuracy and consistency.
Corrects an issue where the service location wasn't being selected properly in certain scenarios.
Specifically, it ensures the 'Enter Service Address' button is clicked only when the address text box is not visible. It also removes the unnecessary 'saveAddressButton' click.
Removes the explicit `outputDir` configuration from the Playwright config.
The default output directory is sufficient and allows for more flexibility in test execution and reporting.
Updates the report configuration to adjust folder paths, logo locations, and the project name, ensuring correct paths and the proper project is referenced in reports.
Updates the default folder path for generated test reports.
This ensures that test results are consistently saved in the
"artifacts/test-results" directory.
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.
Suggests an alternative installation command that includes chromium and its dependencies.
This ensures users have a complete and functional environment for running Playwright tests.
Updates the Azure pipeline configuration to reference the relocated Dockerfile.
This ensures the pipeline correctly identifies and builds the Docker image, preventing build failures.
Updates the path to the artifacts folder in the Playwright config.
This ensures that test results are stored in the correct location
within the project structure.
Updates .env files to use a consistent comment style for base URLs.
This change improves readability and maintainability of the
environment configuration files.
Ensures environment variables are loaded from `.env` files only when not running in a CI environment.
This prevents overwriting variables already present in the CI environment.
Adds an example env file for local development.
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.
