Configures the Playwright blob report output directory to '/app/blob-report' within the test job definitions.
This ensures that the blob reports are consistently stored in a designated location within the container,
facilitating easier access and management of test artifacts.
Ensures that the playwright config file path is explicitly set during test execution.
This change resolves potential issues where the config file might not be correctly located, especially in environments with non-standard project structures.
Removes temporary debugging statements from the Playwright test workflow. These logs were used to diagnose issues with report merging but are no longer needed, reducing noise in the CI output.
Executes Playwright after merging reports to guarantee the generation of final reports.
This ensures that the JUnit and other reports are generated correctly after the merging process, leading to more reliable test reporting.
Adds debugging logs to the Playwright test execution within the Docker container to aid in diagnosing issues with report generation and merging. These logs provide insights into directory contents and the state of the environment.
The previous implementation encountered issues with command execution within the docker container. This change wraps the Playwright commands in a bash shell, ensuring proper execution and resolving potential errors during the report merging and related processes.
Specifies that environment variables are exported to ensure
they are accessible within the Docker container context. Also
wraps the execution command in `bash -c` to ensure proper
command execution within the container.
Ensures the shell command is properly executed within the Docker container by wrapping it in quotes. This resolves issues where the command was being misinterpreted or failing to execute as intended.
Removes unnecessary directory listing commands from the Docker container execution within the Playwright test job.
This change simplifies the execution and reduces the noise in the job logs, focusing on the core report merging process. The execution also uses semicolons instead of newlines to separate commands.
Enhances debugging capabilities in the CI workflow by adding `ls -al` command to print the contents of the playwright-tests directory.
Also, corrects the path for listing test results to use a relative path instead of an absolute path, ensuring it works correctly regardless of the environment.
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.
Updates the path to the test results directory in the workflow file to reflect the new location.
This ensures the workflow correctly accesses and reports test results.
Enhances debugging capabilities during test execution by adding logging to capture directory contents. This helps diagnose potential issues related to file access or environment setup within the test environment.
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.
Moves the CASH-836 tag from the HeavyTruck test to the RepairOnly test.
This change ensures that the correct test case is associated with the corresponding issue in the issue tracking system.
Updates the tags for CashRepairInShopPayPal and CashRepairMobileCreditCard test cases to include the '@CASH-836' tag.
Removes the '@CASH-836' tag from the CashReplaceSplitWindshield test case.
Removes redundant path specification in the Playwright test command within the CI configuration.
This change streamlines the test execution process by eliminating unnecessary repetition of the Playwright path, improving readability and maintainability of the CI pipeline definition.
Reduces the total number of shards used for parallel test execution from 4 to 2.
This change aims to optimize resource utilization and potentially improve test execution speed, considering factors such as the number of available agents and the characteristics of the test suite.
Adds the `@CASH-836` tag to `CashRepairInShopAfterPay` and `CashReplaceSplitWindshield` tests.
This addition presumably links these tests to a specific issue or requirement tracked under CASH-836.
Removes unused variables from playwright-test.yml.
Adds the filter value to the workflow output, providing more visibility into the test selection process during CI runs.
This helps in debugging and verifying the correct test subset is being executed.
Updates the grep filter for Jira card numbers to include the "@" prefix, ensuring accurate filtering by test case tag. This ensures that only tests specifically tagged with the Jira card number are executed.
The automated test pipeline now runs without the regression flag enabled.
This change ensures that tests are executed as standard tests, rather than being treated as regression tests.
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.
Moves environment variable definitions to ensure they are available
before the docker container is created, resolving issues related to
undefined variables during container execution. Also, simplifies the
playwright report merging process by streamlining the execution of
commands within the docker container.
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.
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.
Updates the Playwright Dockerfile to streamline the build process.
This change improves the Dockerfile by:
- Using `npm ci` for faster and more reliable dependency installation
- Copying the .npmrc file before copying the code.
- Installing Playwright browsers within the playwright-tests directory.
Adds the `Managed` flow type to the insurance test data.
Specifies an empty payment details object for the insurance flow
to skip the payment method page.
Updates the safelite-playwright-core dependency to version 1.0.26.
This change also imports missing modules from the updated safelite-playwright-core package in relevant files.
Adds a new environment variable to skip content site checks, improving test environment flexibility.
Improves the "nextPage" function in BasePage to handle loader elements and button states more reliably.
Adds support for selecting loss location in CCPolicyInfoPage to reflect claim details accurately.
Updates assertion methods to use Soft assertions for smoother test execution.
Adds a new test case "InsuranceMeemicNearSchoolVerified" to expand test coverage.
Refactors the vehicle lookup test data structure to improve data handling and flexibility.
Consolidates license plate information into a dedicated object within vehicle details.
Updates the safelite-playwright-core dependency to the latest version.
This update likely includes bug fixes, performance improvements, or new features.
Removes unused promoCode variable from OrderConfirmationPage.ts
