EPAM-EBSCO Team Leads' Forum
Permanent Forum Members:
| Name | Team |
|---|---|
| Firebird | |
| Volaris | |
| Folijet | |
| Vega | |
| Thunderjet | |
| Spitfire | |
| Citation | |
| Corsair | |
| PTF | |
| Kitfox | |
| Mriya (AQA) | |
| QA Manager |
Meeting Minutes
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.
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:
- 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.
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
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
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 Presentation (documentation)
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
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
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
Quick note: Starting from Q-release, new development environment requests for community projects have to go through the approval process by the Tech Council. This is done so that we can project the costs of AWS hosting. All such requests must be handled through Jira tickets assigned to Jira project COSTS
useful links:
TC AWS hosting costs Subgroup: https://folio-org.atlassian.net/wiki/display/TC/Controlling+AWS+Hosting+Costs+subgroup
Process of creating Jira tickets for requesting an justifying new environments: https://folio-org.atlassian.net/wiki/display/TC/AWS+Environment+Lifecycle
Meeting October 10, 2023
Attendees: Matt, PK, Kate, Slava, Gurleen, Sasha K, Serhii, Lee
Topic: Matt's presentation on FQM and ListApp
Presenter: Matt Weaver
Next topics (not in priority order).
- More on shift-left
- DCB overview and challenges (Gurleen: 7th Nov)
- COMPLETED: FQM overview and challenges, and the process of TCR
- LinkedData overview and challenges
- Onboarding external teams
- Review the RCA program
Meeting September 26, 2023
Attendees: Matt, PK, Kate, Gurleen, Sasha K, Serhii, Lee
Topic: Leads Forum Format pseudo retrospective: how do we make the forum more effective
Presenter: all
Overall Impression:
The forum has been useful!
Thoughts:
PK
- Like the idea of sharing best practices, both technical and process related
Sasha K
- Leave more space for interactions – i.e. never enough room for discussions after presentations.
Serhii
- Presentation prep time is well-spent. You have the opportunity to rethink the previous decisions when you’re putting things on paper
Matt
- Tech topics useful, learning a lot
- Consortia support information is very valuable for FQM
Kate
- Definitely keep it technical
- Challenges: RRT support; Rapid response team is not that “rapid”.
- RCA – how helpful is it?
- Tech debt feature in each team. Maybe make it more specifics?
Gurleen
- Gained useful knowledge from this forum.
- DCB has been challenging
Decisions:
Continue with presentation, but have more time for discussion after presentations: Going forward we’ll start at 7:45 AM EST
Next topics:
- More on shift-left
- DCB overview and challenges
- FQM overview and challenges, and the process of TCR
- LinkedData overview and challenges
- Onboarding external teams
- Review the RCA program
Please suggest more
Meeting September 5, 2023
Attendees: Matt, PK, Slava, Kate, Sasha, Serhii, Lee
Topic: ECS (Extended Consortium Support) continued. Applause and big thanks to Serhii_Nosko !
Presenter: Serhii_Nosko
Link to session recording (new)
Link to ECS doc on Wiki (same as previously)
Link to Serhii's presentation (same as previously)
Next time: Let's discuss the format of our forum: what's working, what's not working, how to improve the usefulness, etc
Potential next topics:
1) How's shift-left working (all)
2) FQM and List App (Matt Weaver )
3) DCB and Reshare (Gurleen Kaur1 )
4) Linked data and Bibframe (Punnoose Kutty Jacob Pullolickal )
5) please propose other topics
Meeting August 22, 2023
Attendees: Gurleen, Matt, PK, Slava, Kate, Sasha, Pavlo, Serhii, Lee
Topic: ECS (Extended Consortium Support)
Presenter: Serhii_Nosko
Next time: Continue with the Consortium functionality
Meeting August 8, 2023
Attendees: Gurleen, Matt, PK, Slava, Kate, Sasha, Serhii, Lee
Topic: Shift-left Testing diagram within a sprint
Presenter: Alexander Kurash
Next time: Discuss Consortium functionality
Meeting July 28, 2023
Attendees: Gurleen, Matt, Pavlo, Sasha, Serhii, Lee
Topic: "What Went Wrong...". This is a discussion of development efforts that should have gone better, and what conclusions can be drawn from those efforts
Presenter: Serhii_Nosko
Next time: We will continue discussing Serhii's prez, and we'll focus on TESTING, especially automated testing, especially automated testing of asynch architectures
Meeting July 11, 2023
Attendees: Gurleen, Matt, PK, Pavlo, Kate, Sasha, Serhii, Lee
Topic: "What Went Wrong...". This is a discussion of development efforts that should have gone better, and what conclusions can be drawn from those efforts
Presenter: Kate Senchenko