Replaces direct matrix value access with a function call to obtain the shard number.
This approach enhances flexibility and maintainability by abstracting the source of the shard number.
Uses the matrix context for the shard number in the Playwright test workflow.
This change ensures the correct shard number is used when running Playwright tests in parallel.
Updates the variable used to access the source branch name in pull requests.
The previous variable was deprecated or no longer functioning as expected.
This change ensures the workflow can reliably retrieve the branch name for
extracting JIRA card numbers.
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.
Ensures the JIRA card number is available as an environment variable during the playwright merge-reports process. This allows the reports to be tagged with the correct JIRA ticket.
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.
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.
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.
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.
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.
