KT 1º 2026 01 27 17 03 32

Understanding the Current Project Situation

Team Introduction and Setup

• The speaker introduces themselves as the QA lead for automation, indicating they are new to the team and still learning about their responsibilities.

• They mention that the team has set up their machines with necessary tools like S-code, Maven, Node.js, and Selenium.

Workflow Challenges

• The speaker expresses uncertainty regarding the workflow processes and how tasks are managed within the project.

• They request any information or insights from a colleague to better understand daily operations and previous experiences in similar roles.

Knowledge Transfer (KT) Sessions

Planned Knowledge Sharing

• The speaker discusses plans for conducting KT sessions led by Vinny, who is knowledgeable about the products being tested.

• It is noted that Vinny aims to present automation projects and product details during these sessions.

Products Under Testing

• The current focus includes four main products: CRM, Coussin Medisto, Bobcat, and Gamera.

• Vinny's prior experience as a technical leader on Coussin Medisto positions him well to guide others through these products.

Technical Setup Assistance

Installation Links Shared

• A link is shared for installation instructions related to setting up Bobcash; however, there are issues with accessing it.

• The speaker attempts to troubleshoot communication issues while sharing links via chat.

Future Collaboration Plans

• There’s an intention to collaborate on configuring environments together in future sessions.

• The speaker mentions having access to several repositories including Bobcat and expresses willingness to share them for further understanding of past projects.

Project Development Insights

Initial Thoughts on Project Complexity

• The speaker reflects on the complexity of a project, noting that it has become more manageable recently. They mention that while it was previously bureaucratic, improvements are now evident with the introduction of a new framework called Rev, developed in TypeScript.

Framework Discussion

• There is a discussion about the Rev framework, which is still under development. It aims to simplify work processes and enhance efficiency compared to previous methods. The speaker expresses interest in accessing this new tool for better productivity.

Technical Challenges Encountered

• The conversation reveals some technical difficulties faced by the team, including issues with version installations and broken links (404 errors). This highlights common challenges in software development environments where dependencies can complicate setups.

Collaboration and Screen Sharing

• One participant mentions sharing their screen to demonstrate their setup process using VS Code and other tools like Intel G. This emphasizes collaborative efforts within the team to troubleshoot and configure necessary software for project tasks.

Understanding Workflow Processes

• A detailed explanation of workflow processes is provided, focusing on how tasks are managed through cards in a project management system (Gira). Participants discuss moving cards through various stages: from "to do" to "in progress," then to "review," and finally validating by business stakeholders. This structured approach ensures accountability and clarity in task management.

Business Process and Review Workflow

Overview of Business Validation Process

• The business validation process involves delivering evidence such as screenshots and videos of tests executed, which are then documented in a card for approval.

• Once the business validates the work, it moves to a closed status, indicating that a decision has been made regarding the task's completion.

Roles in Approval and Review

• Troy is mentioned as one potential approver from the Product Owner (P.O.) team; however, others like Vini or Thomas can also fulfill this role.

• Any team member can review Pull Requests (PR), with specific individuals like Vini or Alejandro often involved in this process.

Understanding Review Assignments

• Clarification is sought on how reviewers are assigned; typically, the person who reports the card does not have their name listed as a reviewer unless they comment on it.

• It’s noted that there should be clarity on who reviewed each card to improve accountability within the workflow.

Challenges in Documentation and Best Practices

• There is an acknowledgment of a lack of centralized resources or documentation outlining best practices for coding within the team.

• The absence of a collection of standard assertions used by everyone complicates consistency across projects.

Navigating Blockages and Project Familiarity

• Team members must proactively seek solutions when blocked by issues, often requiring them to reach out to others for assistance.

• Gaining familiarity with projects occurs through repeated involvement; working on multiple sprints allows deeper understanding over time.

Insights into Project Management Dynamics

• Team members may not receive comprehensive introductions to new projects; instead, they learn through hands-on experience with tasks assigned by leads.

• Specific scenarios are provided by project leads detailing what needs automation without extensive background information about broader project contexts.

Automation Processes and Tools Transition

• The technical team receives predefined scenarios for automation rather than developing them independently, limiting their intimate knowledge of products being tested.

• Current projects utilize Selenium with Ruby but are transitioning to TypeScript with Playwright for future developments.

Transitioning from Ruby to TypeScript and Java

Current Project Status

• Discussion on the transition from Ruby projects, indicating a shift towards TypeScript and Java. The speaker mentions that they are abandoning Ruby frameworks as new automation is not being added.

• The Bobcat project is currently being expanded in Java, with plans to eventually transition it to TypeScript.

Collaboration and Setup

• Plans to set up a Java environment on the speaker's machine for collaboration on automation tests. They express willingness to assist in configuring the setup.

• Emphasis on learning through collaboration, with an intention to share knowledge about automation processes.

Daily Learning and Reporting

• The speaker's manager requests daily updates on what has been learned or accomplished, highlighting a structured approach to tracking progress.

• Acknowledgment of the challenge in providing daily insights due to limited ongoing projects, suggesting a disconnect between management expectations and current project realities.

Future Automation Developments

• Anticipation of future access to new projects once certain conditions are met (e.g., completion of REV). There’s mention of potential new automations for various applications.

• Discussion about needing to recall previous automation methods as they prepare for migration from old systems once stability is achieved.

Team Dynamics and Knowledge Sharing

• Insights into team structure where different members will focus on various aspects of upcoming projects. This indicates a collaborative effort toward familiarization with new automations.

• Recognition of the need for refresher training on older automation tools after a period without use, emphasizing continuous learning within the team.

Supportive Environment

• Commitment expressed by one member to support others in their tasks while also seeking assistance when needed, fostering a collaborative work culture.