EPAM-EBSCO Team Leads&#39; Forum

Quick Note: This is coming hopefully this Fall. Looking forward!

Meeting August 6, 2024

Attendees: Ostap, Matt, Yogesh, PK, Sasha K, Gurleen, Kate, Sasha H, Martin, Mikita

Topic: Gitlab branching strategy

Presenter: Mikita Siadykh

Quick Note: This is coming hopefully this Fall. Looking forward!

Meeting July 23, 2024

Attendees: Ostap, Matt, Yogesh, PK, Sasha K, Serhii, Gurleen, Kate, Slava, Pavlo, Oleksii Petrenko and Tetiana Gusar

Topic: Reporting Portal and e2e test maintenance by FE engineers

Presenter: Oleksii, Tetiana

Quick Note

Reporting Portal link: https://report-portal.ci.folio.org/ui/. Please use your Github creds to log in

Leads - since now we have our Quality Gates pipeline we need to carefully monitor the e2e failure (as well as Karate failures). Please use the reporting portal to see the failures. Please make sure your FE engineers know what to do.

Some action items from the meeting (as per chatgpt )

Tatiana Gusar:
- Provide additional training for FE engineers on Cypress test maintenance
- Ensure Scrum Masters are involved in the troubleshooting process.
- Communicate with John C and Zach about monitoring Stripes e2e failures
All Team Members:
- Actively participate in the troubleshooting process.
- Utilize the report portal for tracking and resolving test failures.
Lee Braginsky/Yogesh Kumar/Oleksii:
- Monitor the engagement and progress of the team in reducing bugs.
- Ensure that all dependencies are addressed and team members are informed.

Meeting July 9, 2024

Attendees: Ostap, Matt, Yogesh, PK, Roman, Sasha K, Serhii, Gurleen, Kate, Slava,

Topic: general discussion on QualityGates, Karate failures and the priority of fixing issues

Meeting June 25, 2024

Attendees: Ostap, Matt, Yogesh, PK, Roman, Sasha K, Serhii, Gurleen, Kate, Slava,

Topic:

Discussed various topics including setting up developing envs using BusyBee vs. Vagrant.
We are ready to include Gatling reports into QualityGateCI pipeline

Presenter: Serhii Nosko

Quick Note

We are going to include Gatling report into QualityGatesCI pipeline. Yogesh is going to create ticket for Kitfox. Please continue identifying Karate tests to be included into Gatling report

BusyBee seems be a good reliable way to quickly create Eureka local development environment.

Meeting June 11, 2024

Attendees: Ostap, Matt, Yogesh, PK, Roman, Sasha K, Serhii, Gurleen, Sasha H, Slava,

Topic:

Discussed various topics including setting up developing envs using BusyBee vs. Vagrant, Gatling reports and FE engineers doing Cypress maintenance

Presenter: all

Quick Note:

Serhii Nosko has a script to quickly and reliably set up development env using BusyBee

The Quality Gate CI Pipeline is ready. https://jenkins-aws.indexdata.com/job/folioRancher/job/folioQualityGates/job/folioCiQualityGates/

Next Time: Continue the quality topic

Meeting May 28, 2024

Attendees: Ostap, Matt, Yogesh, PK, Roman, Sasha K, Serhii, Gurleen

Topic:

Gurleen presented her "quick wins" with Gatling report. Thank you Gurleen and Team Volaris
Developers' maintaining e2e tests. Tjet is doing it (I think Fjet as well, but Kate wasn't in the meeting to confirm). Leads - please work with your FE developers and have them work with Ostap to come up to speed on e2e maintenance.

Presenter: all

Quick Note: We are hearing that often POs prioritize tickets related to "quality work", such as Karate tests, Gatling performance report, or e2e maintenance lower than functional features. Dear Captains, this is where you need to negotiate with your POs and explain that this type of work makes the business features more robust. I mean, at this point, nobody questions the need to implement unit tests or integration tests, right? Gatling and e2e maintenance should become as natural as unit-testing...

BTW, the Quality Gate CI Pipeline is ready. https://jenkins-aws.indexdata.com/job/folioRancher/job/folioQualityGates/job/folioCiQualityGates/

Next Time: Continue the quality topic

Meeting May 14, 2024

Attendees: Ostap, Kate, Yogesh, PK, Martin, Sasha K, Serhii, Sasha H

Topic:

Discuss progress with Karate/Gatling tests and reports
Developers' maintaining e2e tests

Presenter: all

Quick Note: Sasha K and Serhii stated that teams Vega and Thunderjet finally have stably green Gatling reports. Thank you! Who's next please?

Still not many teams have their FE developers maintain e2e tests. Folijet seems to be the only exception where FE developers are up to speed on Cypress. Success stories on the subject are expected next time.

Next Time: TBD

Meeting April 30, 2024

Attendees: Ostap, Kate, Yogesh Matt, PK, Martin, Sasha K, Gurleen, Sasha H

Topic:

Discuss progress with Karate/Gatling tests and reports
Discuss how teams are reacting to newly found bugs

Presenter: all

Quick Note: Sasha/Gurleen mentioned that Gatling is not running consistently, we need to look into it deeper. More - next time

WRT bugs, I'm hearing that in a development cycle, while newly found P1s are usually addressed immediately, the P2s are often placed on the backlog and addressed later (sometimes MUCH later - per PO's prioritization). Which means that we often complete stories with P2s. I personally don't like it, as I think this leads to more bugs before BF and during BF. Let's discuss further

A word of wisdom from Martin:

For every bug we have to ask 5 "why's". Why did the bug happen? Let's say it's coding (i.e, not due to requirements), why coding? If we didn't know the impact that the new implementation causing on other parts of the code, why didn't we know? Because we didn't have an automated test. Why didn't we have an automated test for other parts of the code? Because we didn't have time to write tests. Why didn't we have time to write tests? Because we don't have skills or because the code is not easily testable, or because we don't have time to skip features... Keep asking why will eventually get to the root cause, not just a superficial cause. Every developer should be asking this question and help the team improve. In this case if we don't have enough skills, work with management to get the skills. If the code is not testable, have a story and work with the architect to redesign the code. If no time, work with PO next time on priorities.

Next time: 1) Summarize our progress with Gatling. 2) Continue discussion of how to reduce the number of P1/P2 defects in newly developed features

Meeting April 16, 2024

Attendees: Ostap, Kate, Matt, PK, Martin, Olamide, Sasha K, Slava, Gurleen, Sasha H

Topic: Continue with Karate tests. How do we address Karate failures immediately (as opposed to schedule bug fixes)

Presenter: all

Quick Note: According to the Leads, teams almost always look into Karate failures pretty much immediately and address them right away if the fix is expected to be a quick one. However, if the fix is not expected to be quick (maybe a day or two) then it's up to POs to prioritize and schedule the fix. We want to be more assertive in addressing Karate failures. Lee is going to say a few words on this subject at Mark V's FOLIO status meeting on Thursday

Meeting April 2, 2024

Attendees: Ostap Voitsekhovskyistap, Kate, Matt, PK, Yogesh, Martin, Olamide, Sasha K, Gurleen, Serhii,

Topic: Continue with Karate tests. Using Karate tests for performance measuring.

Presenter: Olamide Kolawole

Quick Note from Olamide: let's get started!

We need each team lead to implement a scenario or more in one maven module within each team lead's ownership. You can reuse existing scenarios or create new one. Let's target next week tuesday(April 9th) to have this done so that we can have further conversations regarding its execution environment, test strategy, report collation, inclusion in continuous integration as quality gate. This first step's purpose is to gain a shared understanding. If you need any help or support please don't hesitate to reach out to me.

Link to PR

Link to official Karate docs

Meeting March 19, 2024

Attendees: Ostap Voitsekhovskyi, Kate, Matt, PK, Yogesh, Martin, Olamide, Sasha K, Gurleen, Serhii,

Topic: Continue with Karate tests. Using Karate tests for performance measuring

Presenter: Olamide Kolawole

Quick Note:

Thank you for your attention in todays meeting! Regarding Karate tests, we came to the following conclusions. This will be sort of be a list of action items that we will work towards to make karate tests better

Attain 100% pass rate. Teams will work to resolve flaky tests. Continuously erring tests can be excluded. We must be prepared to compromise.
After reaching a stable "100%" pass rate, teams have committed to hop on test failures for immediate resolution. This can have an impact on sprint commitments.
After reaching a stable "100%" pass rate for a flower release, a branch will be cut in the karate tests repo to represent the test suite that verifies the flower release.

I will continue to update this list as we work the items in our meetings. The immediate requests from teams regarding Karate tests is stabilization. I will also be preparing guidelines for Karate performance tests for your review. Thanks!

Link to presentation - none

Meeting March 5, 2024

Attendees: Ostap, Yogesh, Sasha K, Gurleen, Serhii, PK, Pavlo, Kate, Matt, Lee, Sasha H, Olamide, Slava

Topic: Excellent presentation by Olamide on Karate testing strategies. This topic will continue next time as many participants had questions

Presenter: Olamide Kolawole

Link to recording:

Link to presentation:

Next time: we will continue with the Karate testing discussion

Meeting February 20, 2024

Attendees: Ostap, Yogesh, Sasha K, Gurleen, Serhii, PK, Pavlo, Kate, Matt, Lee

Topic: Yogesh Kumar is presenting the Shift-left program and its results so far

Quick notes: Yogesh reminded us why shift-left is important for early feedback on Quality.

Presenter: Yogesh emphasized the importance of shift-left for early quality feedback. He also provided an update on our shift-left journey.

Meeting January 19, 2024

Attendees: Ostap, Yogesh, Sasha H, Sasha K, Gurleen, Serhii, PK, Matt, Lee

Topic: Ostap Voitsekhovskyi is presenting automated testing and Team Mriya

Quick notes: Ostap went through the "theory" of quality automation and why it's so important to us, as well as the technique of creating Cypress tests. I think we should continue this discussion next time and proceed to leads' questions.

Presenter: Ostap Voitsekhovskyi

Link to Presentation (documentation)

Meeting December 19, 2023

Attendees Sasha K, Serhii, Kate, Pavlo, Matt, Gurleen, Lee, Sasha H (now part of the forum), Yogesh, Oleksii P

Topic: Sasha H presentation on how to use the Unified Pipeline.

Quick notes: The Unified Pipeline is a set of jenkins jobs to create rancher environments for teams. Can the leads/team members use it so the teams take care of their immediate devops needs and free up team Kitfox to focus on strategic automation initiatives?

Team leads are also encouraged to come up with additional requests for Kitfox.

Presenter: oleksandr_haimanov

Link to recoding

Meeting December 5, 2023

Attendees Sasha, Serhii, Kate, PK, Matt, Slava, Lee

Topic: Linked Data and Bibframe

Quick notes: Team Citation is working on adoption of the concept of Linked Data Bibframe for FOLIO.

Presenter: Punnoose Kutty Jacob Pullolickal

Link to recoding

Next time: We will continue our conversation about LinkedData and FOLIO. Please prepare questions for Punnoose Kutty Jacob Pullolickal

Meeting November 7, 2023

Attendees Sasha K, Serhii, PK, Matt, Gurleen, Slava, Lee

Topic: DCB (Direct Consortia Borrower)

Quick notes: The DCB is K int's product, and the main challenge is to integrate this product with FOLIO. Team Volaris is releasing the initial version of DCB-FOLIO integration today! (11/7/23)

Presenter: Gurleen Kaur1

Link to recoding

Next time: LinkedData and FOLIO presented by Punnoose Kutty Jacob Pullolickal

Meeting October 24, 2023

Attendees + Guests: Mark V, Maccabee Levin, Peter Murray, Sasha K, Kate, Serhii, PK, Matt, Gurleen, Pavlo, Slava, Lee

Topic: Controlling AWS hosting costs (subgroup of Tech Council)

Presenter: Maccabee Levine