User:Victor Grousset - tuxayo/Community work/Reports/2024-06

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.

Try to get attention given to: Bug 30759 - Add hint about the data that is sent via the Google Books API to OPACSuggestionAutoFill

This follow-up bug was a blocking QA finding of mine that was missing in another ticket.

Feedback and guidance on proposed solutions + extensive additional research Bug 21507 - Decimal separators issues in patrons payments/fines, simplified

Poked at perl's IRC channel to know if there anything already existing. And emailed ICU's mailing list.

Probe left and right what would be acceptable functionally: Bug 32722 - Mandatory subfields from UNIMARC framework shouldn't block the creation of a bib record when field itself is optional

In general chat and at the french user Koha group annual gathering.

Proofread changes + Unblocked by finding out that an issue isn't related to the patch: Bug 36694 - Remove HC Sticky library in favor of CSS

Note for the people funding my work and the rest of the community for transparency purposes: Partial QA of an enhancement from ByWater Solutions. For QA of enhancements I'm asked to ideally focus on one monthly.

Provided guidance on contribution process and proofread changes: koha-misc4dev: Unimarc sample data : items' itype are not imported

https://gitlab.com/koha-community/koha-misc4dev/-/issues/76

https://gitlab.com/koha-community/koha-misc4dev/-/merge_requests/69

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.

Guide signoff session with French community as part of their annual gathering

https://koha-fr.org/symposium-2024/ 4 attendants for the morning and afternoon, 2 new people trained on patch testing and two coming mainly but not only for in depth testing of an enhancement they ordered. Results for attendants: 4.5 signoffs (one had test plan only half done due to lack of time, comment left), 2 failed QA, 3 patch does not apply. 6.25 hours of total time spent on that.

New tickets opened

i.e. Found something wrong and documented how to reproduce it. Or suggest an enhancement (usually for dev tools)