BMW 2026 01 15 105620

Transition Process and Onboarding Discussion

Overview of the Transition Process

• The meeting discusses the transition process, focusing on user roles and potential difficulties that may arise. Initial escalation points are identified as Sandra and Fábio Zaghin.

• There is a mention of GitHub access and other necessary tools for team members to begin their onboarding effectively. The importance of sharing resources is emphasized.

Frameworks and Tools

• The discussion highlights the use of a legacy framework involving Rubb and Selenium, which is crucial for building environments within the product Bobcat. This framework's relevance in current projects is noted.

• A new project utilizing Playwright (REV) has shifted focus from the legacy framework, indicating a significant change in development strategy within the team.

Installation Requirements

• Team members are instructed to install VS Code and Node.js as part of their onboarding process, with specific instructions on how to do so given BMW's restrictions on external installations. Access through Workspace One Intelligent Hub is required for installation.

• It’s mentioned that admin access will be necessary for installing Node.js, highlighting procedural steps involved in setting up development environments at BMW.

Configuration Steps

• After installing VS Code and Node.js, team members need to clone repositories from GitHub and configure proxy settings to access internal systems effectively. Specific commands are provided for this setup process.

• Clarification about accessing multiple repositories under the team's organization structure on GitHub indicates a collaborative environment where various projects coexist under one umbrella.

Team Structure Insights

• The acronym EFS stands for "FnC America Test Automation," providing insight into the team's focus area within automation testing frameworks at BMW, emphasizing clarity in communication regarding team roles and responsibilities.

F100 Test Automation Overview

Team Integration and Access

• The team will be added to the F100 test automation organization by Rob, facilitating quicker collaboration.

• Current involvement in Bobcat Test Automation is mentioned, with a focus on understanding the PlayWrite framework through simpler tasks.

• Clarification on access management; Elvine is responsible for adding members as there are no security managers present.

Communication Structure

• Suggestion to centralize technical communication through Jean, who can streamline requests and manage hierarchy effectively.

• Vinny's role as a key lead in automation is highlighted, acting as the right hand of Rob, the Tech Holder for BMW automation.

Framework Transition

• Emphasis on transitioning from legacy frameworks to new ones being developed by Zalp while maintaining current operations in parallel.

• A structured approach to managing technical queries through Jean ensures organized communication within the team.

Framework Tools and Requirements

Development Environment Setup

• Discussion about various frameworks used, including NexigenTest which utilizes Selenium for testing purposes.

• Introduction of TypeScript and its simplicity in setup; installation guidance provided for necessary tools.

Java and Other Dependencies

• Requirement of Java (Jdk21), which includes Runtime Environment capabilities, is essential for development work.

• Explanation of environment variables related to Java installation via Workspace One; importance of proper configuration emphasized.

Migration Strategy

• Ongoing maintenance of legacy UI framework while planning migration to newer frameworks indicates a transitional phase in development practices.

• Maven's role as a dependency manager is discussed alongside potential issues with Edge Driver during test execution.

This structure provides an organized overview of key discussions from the transcript while ensuring easy navigation through timestamps.

Selenium Configuration and Project Setup

Overview of Selenium Cache and Configuration

• Zulu points out the Selenium cache, indicating its importance for UI framework configuration.

• A detailed document outlines step-by-step instructions for setting up Selenium, including downloading version 3.19 and creating a specific folder structure on the local disk for easier access.

Folder Structure and Tools

• The setup includes various folders: dev, code (for cloning repositories), and tools (for necessary utilities).

• Access to Maven is required; users can download binaries directly without needing special permissions.

Proxy Configuration

• A proxy configuration file is essential for accessing dependencies; sensitive information like passwords should be handled carefully.

• The set XML file and Maven config are crucial components that need to be maintained in the project directory.

Framework Discussion

• The main frameworks discussed include those used for UI testing, with emphasis on building projects simply.

• Mention of other products being worked on by the team, such as Bobcat Test Automation (UI-focused), API testing frameworks, and Rev Framework.

Team Structure and Roles

Team Hierarchy

• Introduction of team members: Rob as lead, Guilherme Klein's role alongside Dolos, with updates needed on team structures.

• Overview of team members from different regions including Mexico; highlights roles within the IT product team.

Business Product Team Interaction

• Thomas Wilson's recent interactions with Harin Troy regarding upcoming demands indicate ongoing communication about future projects.

Performance Testing Queries

Current Testing Focus

• Inquiry about performance testing reveals that current demands focus primarily on aggressive tests executed by business teams rather than performance metrics.

Future Considerations

• Emphasis on automation of existing scenarios or maintenance rather than new performance tests suggests a strategic focus within the team's objectives.

Access Requirements

Necessary Access Requests

• Discussion around what access is needed to work effectively within their system indicates an organized approach to resource management.

Accessing Databases and Configuring Tools

Database Installation Options

• The speaker discusses the option to install either Microsoft SQL Server or DeBever for database access, emphasizing the need to generate data as per project requirements.

• Mention of hard-coded data in some projects, contrasting with the Bobcat project where data is generated through backend requests.

GitHub Copilot Setup

• Introduction of a specific GitHub user (ARgithubcopilotuser) necessary for utilizing GitHub Copilot, along with a step-by-step configuration guide.

• Reference to a "Do it yourself" page that will assist users in setting up Copilot on their computers.

Access Requirements

• Users must have their first access approved by the service signal before they can utilize certain tools like GitHub Copilot.

• Discussion about checking directory paths relevant to user accounts and ensuring everyone is aligned on access points.

Requesting Database Access

• The speaker mentions needing to request specific databases through a server interface, highlighting potential confusion over images shared among team members.

• Clarification that not all database requests are necessary; some may be denied based on user roles and needs.

Communication for Support

• A chat tool is introduced for requesting specific database access, indicating that communication will be essential for obtaining necessary permissions.

• Instructions provided on how to initiate conversations within the service portal, stressing the importance of speaking with human representatives rather than AI.

Accessing Resources and Knowledge Transfer

Requesting Access to Resources

• The speaker emphasizes the importance of addressing requests effectively, mentioning a specific case (X) that requires access to a database.

• Before making access requests, it is recommended to complete all necessary requests through the service signal for efficiency.

• Most access requests can be processed quickly, often within a day, including those related to ATC GitHub Organization and User access.

Essential Tools for Daily Work

• Key tools identified for daily operations include ATC GitHub and Copilot User, which are deemed essential in current workflows.

• A step-by-step guide is available for requesting access on the portal; no mandatory training is required before this process.

Training and Configuration Insights

• Although there’s no mandatory training, participants must pass a quiz with tricky questions; hints are provided in the training slides to aid in passing.

• Configuration steps for connecting to GitHub are straightforward; users can utilize various databases like MySQL or Microsoft Server without significant issues.

Addressing Questions and Knowledge Transfer

• The speaker invites questions regarding the information shared so far and acknowledges their own limited knowledge about certain products being discussed.

• There will be ongoing support during the knowledge transfer (KT), with plans for further learning sessions over the coming week.

Communication and Meeting Etiquette

• Emphasis on maintaining clear communication while working in a hybrid system; team members should inform others about any commitments that may affect availability.

• Attendance at KT meetings with BMW personnel is strongly encouraged as they provide crucial updates on project progress and information sharing.

Effective Communication in Team Meetings

Importance of Directness in Communication

• Emphasizes the need for clear and direct communication during knowledge transfer (KT) sessions, highlighting that team members should avoid unnecessary elaboration.

• Advises participants to present problems succinctly, stating that excessive detail can lead to misunderstandings or disinterest from others.

• Encourages a straightforward approach when discussing issues, suggesting that clarity will facilitate better problem-solving.

Confirmation of Participant Details

• Lists participant identifiers and confirms their accuracy, ensuring everyone is on the same page regarding who is involved in the discussion.

• Continues confirming details for additional participants, reinforcing the importance of accurate identification within team communications.

Addressing Immediate Needs and Access Issues

• Acknowledges the necessity of obtaining access rights promptly to facilitate immediate actions while waiting for further permissions.

• Discusses potential tasks that can be initiated without full access, emphasizing proactive steps to maintain progress.

Technical Setup and Installation Requirements

• Highlights specific software installations needed (e.g., Node.js), noting that some require administrative access which may delay setup.

• Mentions resources available on Confluence for documentation and installation guidance, indicating a collaborative effort to streamline processes.

Closing Remarks and Future Steps

• Expresses gratitude for participation while acknowledging personal challenges faced by the speaker, showing empathy towards team dynamics.

• Reiterates the importance of understanding development processes moving forward as part of ongoing collaboration efforts.

• Confirms next steps regarding GitHub usage and ticket submissions through service channels, ensuring clarity on action items.