Updates the environment variable name from NODE_ENV to PLAYWRIGHT_ENV across the project.
This change ensures consistency and clarity in environment variable usage, specifically for Playwright configurations.
Reverts the hardcoded disabling of Jira ticket creation and enables it based on the `IS_REGRESSION` environment variable. This allows test subtasks and bug tickets to be created automatically when tests are not run in regression mode.
Adds the JUnit reporter to the Playwright configuration.
This allows for generating JUnit-compatible XML reports, which can be useful for integrating with CI/CD systems and other tools that consume JUnit reports.
Adds the Ortoni reporter to the Playwright configuration.
This change ensures that Ortoni reports are generated both in CI and local environments, providing comprehensive test result analysis.
Updates the folder path for test reports to be 'ortoni-report' in CI environments, otherwise defaults to 'test-results'.
The conditional logic ensures that test results are stored in a dedicated 'ortoni-report' folder during CI runs, enabling more manageable reports.
The changes related to jiraCreationPermissions are commented out as TODOs and will be changed back in the future.
Adds the playwright-jira-reporter to the project.
Configures both ortoni and jira reporters, including setting up
Jira API authentication and project keys.
The ortoni report filename is now dynamically generated with a date
stamp to prevent overwriting.
Updates the reporter configuration to conditionally include Jira reporter
when running in CI.
Increases the global test timeout to prevent failures on slower environments.
Updates the address in a test case to use correct formatting and abbreviation
to ensure the test passes consistently.
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.
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 to the artifacts folder in the Playwright config.
This ensures that test results are stored in the correct location
within the project structure.
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.
