Pietro Build 2026 02 04 110131

Customer Digital Testing Pipeline Overview

Introduction to Customer Digital Testing

• The discussion begins with an overview of the customer digital testing processes and pipelines, emphasizing the importance of maintaining demand and addressing issues in test execution.

• There is a concern about team members being pressured for knowledge transfer (KT), which is viewed as unrealistic given the current circumstances.

Issues Identified in Pipelines

• All tests within the pipelines are failing, prompting an investigation into the reasons behind these failures.

• The last successful run of tests was noted on January 27th, highlighting a significant gap since then.

Analyzing Test Failures

• A specific failure in retrieving test plans is identified, indicating that responses from API calls are insufficient for successful execution.

• The speaker attempts to replicate API calls to understand where the breakdown occurs, suggesting a hands-on approach to troubleshooting.

Troubleshooting Steps and Recommendations

Familiarization with Projects

• Team members are encouraged to familiarize themselves with various projects beyond their immediate tasks to enhance overall understanding and capability.

• Emphasis is placed on executing automation locally, regardless of whether tests pass or fail, as this builds practical experience.

Addressing Management Expectations

• Concerns are raised regarding management's expectations for team output without providing adequate support or creating new demands for team members.

• The speaker expresses skepticism about management's awareness of ongoing pipeline issues and suggests that proactive communication is necessary.

Authentication Challenges in API Calls

Token Authentication Issues

• A problem arises when attempting to authenticate API calls due to an invalid token; this highlights potential security or configuration issues within the system.

• The process of generating a new personal access token is discussed as a solution to overcome authentication barriers encountered during testing.

Successful Response Retrieval

• After resolving authentication issues, a successful response containing JSON data related to test cases is obtained, indicating progress towards fixing pipeline failures.

Execution and Configuration of Tests

Initial Setup and Execution

• The speaker discusses the process of running a generated test, emphasizing the importance of ensuring it passes a specific part before proceeding with further execution.

• A suggestion is made to analyze the pipeline for successful execution, highlighting the need for proper project setup in IntelliJ or VS Code for Ruby.

• The speaker explains that tests must be executed via command line after building the project, indicating that this step is crucial for successful testing.

Building the Project

• Instructions are provided on how to build the project using a specific command in the root directory, which involves downloading necessary gems from a Gemfile.

• The speaker mentions navigating through feature files to select tests (e.g., "make a payment") and understanding their execution context.

Test Execution Process

• Environment variables can be set during test execution; examples are given on how to pass parameters when executing tests locally.

• Recommendations include configuring Cucumber settings to use Edge as the default browser for local test executions.

Command Line Execution

• The speaker outlines commands used to execute tests via command line, including environment variable settings and profile selections from cucumber.yml.

• Emphasis is placed on selecting appropriate profiles and specifying feature paths relative to project structure when executing tests.

Troubleshooting and Observations

• The discussion includes troubleshooting steps if initial executions fail, such as checking environment configurations or driver versions.

• As tests run successfully, there’s an acknowledgment of potential errors due to outdated drivers; however, progress indicates that issues can often be resolved through research.

Discussion on Test Failures and Action Items

Addressing Test Failures

• All tests have failed due to an outdated edge driver, indicating a need for updates to resolve the issues.

• A suggestion was made to create a card for tracking this issue, allowing team members to monitor progress and actions taken.

Task Assignment

• The discussion included creating specific cards for different tasks: one for executing custom digital functions and another related to CRM execution.

• Emphasis was placed on the necessity of these cards being created by Douglas, highlighting the importance of structured task management within the team.

Support During Challenges

• There is an acknowledgment that challenges may arise during execution, with an offer of assistance when issues occur. This reflects a collaborative approach to problem-solving within the team.