Removes the explicit URL declaration from the page classes.
The URL validation and navigation are now handled directly within the tests, providing greater flexibility and control over test execution and removing the need to manage URLs within each page object.
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.
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.
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.
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.
