User:Victor Grousset - tuxayo/Community work/Reports/2025-03

QA

Notes:

• An attempt results in feedback provided on the bug. To ask if I correctly followed the test plan due to results that I couldn't interpret. Or if there is indeed an issue. Or questions to clarify something in the code.
• Partial QA is a way to contribute to a ticket that I can't QA alone but for which I can confidently review only part of the code or aren't sure enough about understanding the functional need and change.

Quick triage: Not ready for testing due dependency issue: Bug 38093 - Bundles: Add MARC link options should also add a link in 462

Dependency likely to change a lot, removed from NSO queue.

Investigate and open ticket for upcoming bad issue: Bug 39314 - RabbitMQ can't upgrade from 3.x to 4.x without running a data migration on 3.13

• Look a build failure for our docker images
• Open a Debian ticket for the packaging issue impacting us now + the upcoming upgrade issue : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100165

That looked bad enough to be worth keeping looking into that on QA time. Priorities are open to discussion of course.

Found issues: Bug 37344 - Patrons with cancelled discharge are seen as discharged when suspended due to overdue

At the patch testing session, someone got an issue when testing this. So found a possible cause.

Signoffs (testing submitted patches so they can move on to be integrated)

Note: an attempt usually results in feedback provided on the bug. To ask if I correctly followed the test plan due to results that I couldn't interpret. Or if there is indeed an issue.

Prepare patch testing session with French community as part of their yearly conference

Test sandboxes, reach to their admins about issues. Make a shared document and send to french community so they add patches they want to be tested.

Guide patch testing session with French community as part of their yearly conference

• 3 attendants in total. (1 new to patch testing).
• Results: 1 signoff, 3 failed QA (one huge to test), 1 attempt that might have found an issue, 1 removed from needs signoff because not ready for testing, 2 patch does not apply.
• 9.25 hours of total time directly for that testing session (before, during, after).
• Even if one of the patches was a tough one. Not a great ROI. That gives some factors for when it will be worth it in the future. For the registration threshold. For being one or two days of testing. Being after 2 days of conferences.

After patch testing session: explain patch workflow and signoff rules to dispel belief that signoff must be from another organization

To a attendant and their colleague which though it was not possible to signoff each other patches.

Open ticket: Sandboxes: Changing name or email in sign-off action doesn't work. Old ones are kept

https://gitlab.com/koha-community/koha-sandboxes-docker/-/issues/100