Adds support for different application types (Vue and .NET) and improves server readiness checks.
This change introduces a new `applicationType` parameter to the Playwright test template, allowing it to handle both Vue and .NET applications. It improves the reliability of the test execution by implementing a readiness check mechanism that waits for the server to be fully up and running before starting the tests. This ensures that the tests are not run against an unavailable server, which can lead to false negatives.
The changes include:
- Parameterization of application type (vue or dotnet)
- Server readiness check implementation
- Docker build arguments can now be passed through
Configures the pipelines to utilize regression testing, increases the total shards for automated testing, and corrects the logic for retrieving the branch name to extract the JIRA card number.
Introduces a new stage in the pipeline to run Playwright tests specifically for pull requests.
This ensures that UI tests are executed and pass before merging pull requests, preventing regressions.
The automated testing is now configured to run regression tests.
Uses the source branch from the build context to extract the JIRA card number.
Migrates automated testing configurations to new pipeline structure.
This change streamlines the test execution process by leveraging templates and parameters for increased flexibility and maintainability. It introduces a dedicated template for Playwright tests, enabling easier configuration and reuse across different testing scenarios.
The previous monolithic pipelines are replaced with modular components, improving readability and reducing redundancy. This also allows for better control over test execution, including shard management and result aggregation.
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.
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
