Adds a variable to skip content site deployment during pipeline runs.
This allows for faster and more focused runs when content site changes are not relevant.
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.
Creates a Dockerfile to run Playwright tests in a containerized environment.
This Dockerfile:
- Uses a Playwright base image.
- Installs dependencies.
- Installs Playwright browsers.
- Installs jq.
- Copies application code.
This ensures consistent and reproducible test execution across different environments.
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
Adds Faker.js, Playwright, dotenv-safe, Luxon, and ortoni-report as dev dependencies.
These additions enhance testing capabilities and provide tools for data generation, end-to-end testing, environment variable management, date/time manipulation, and report generation.
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
This is the edge case when we have only inshop service and change the zip for another inshop only services. appointment-type-question is not triggering because no changes were made to the serviceability-details that is causing Inshop service type to get auto select.
