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

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 follow-up that was requested by another QAer: Bug 38503 - Add a Cypress task to generate objects based on its swagger def spec

First try at release notes capitalizing on having tested that bug.

Fixes to solve conflicts in node package changes in the recent QA tooling tickets (Bug 38524 tree)

Bug 38524 - Add support for Vue.js and TypeScript to ESLint config to be able to actually enforce coding guideline JS8

One is also used in the Node.js upgrade (Bug 38426): Bug 38770 - Remove @vue/cli-service and babel

QA feedback about point still needed to be addressed and how to try: Bug 7376 - Transfer limits should be checked at check-in

Call for help at patch testing session of french community didn't work.

Find issues: Bug 35451 - Add tablename field to additional_field_values

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

Find issues: Bug 36271 - Bookings should have circulation rules

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

Find issue + minor follow-up after quick QA look: Bug 11530 - Recalculating an item's total issue count with update_totalissues.pl ignores deleted items

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

Find issue: Bug 17506 - Offline circ needs to be logged

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

Partial QA: Bug 38838 - optgroup construct needs cleaning in the reports module

Enhancement but it's from Jonathan and part of the large work related to "Bug 38664 - Tidy the whole codebase". So it should fit the scope of funded work.

Spent time testing to disprove an issue found previously. And time reviewing the code without finding issues until someone else finished the QA.

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.

Test that it solves another issue: Bug 38588 - Checkin that triggers a transfer => print slip => Internal server error

It solve the most important issue found in Bug 38806 - Dismissing a "Wrong transfer detected" modal leads to transfer not cancelable anymore

Test plan successful but confirmed divergence of behavior between browsers: Bug 38793 - Transfer silently not canceled when TransfersBlockCirc = "don't block" and AutomaticConfirmTransfer = "do automatically confirm"

And later added release notes + tried to improve title.

Two days of patch testing session with French community as part of their yearly hackathon

• 6 attendants in total. 2 main attendants full time. (1 new to patch testing, 1 needing more in depth guidance to get back to using koha-testing-docker for testing more stuff) And 4 others from another workgroup that as part of their specific work on serials spend a big chunk on their time on testing patches. They were more autonomous but I still regularly provided guidance. (3 people new to patch testing)
• I also completed a few signoffs with functional feedback. Either from me or using the opportunity to be with librarians to make them detail potential functional issues. Or have them functionally endorse with detailed explanations some tickets that might be hard to implement. So implementers and reviewers have more confidence about going to the right direction.
• Results: 11 signoffs, 4 failed QA, 1 attempt that might have found an issue, 3 patch does not apply
• 17.32 hours of total time spent related to that testing session (before, during, after).

Start planning patch testing session with French community as part of their yearly conference in march

Registrations are looking good about the attendance :)