Koha Test Wiki Canasta - March 2024

One of a series of test instances for migrating the Koha Wiki MediaWiki database.

For the current Koha Wiki, visit https://wiki.koha-community.org .

User:Victor Grousset - tuxayo/Community work/Reports/2022-11

From Koha Test Wiki Canasta
Jump to navigation Jump to search

Release maintenance of 21.05.x branch

Released version 21.05.21

Backport list: 2

  • Bug 29603 - Fix responsive behavior of facets menu in OPAC search results
  • Bug 28553 - Patrons can be set to receive auto_renew notices as SMS, but Koha does not generate them

Minor stuff

Investigate changes when compiling SCSS: likely due to a compiler change, nothing forgotten in past backport

Patchsets analyzed but not backported: 44

This plus the backported patches gives an idea of the stream of patches to process. Analysis includes assessing the need to update the documentation.

Not backported due to one of the following:

  • severity too low considering this is the oldoldstable branch of Koha, quick analysis
  • missing dependencies/not affecting my branch
  • not enough benefits compared to the risks of regression

Backport attempts: 5

Some time needed to determine whether it impacts 21.05 or the feasibility of the backport. And also attempts to backport not possible due to code conflicts.

  • Bug 31421 - Library limitation on patron category breaks patron search
  • Bug 31364 - Saving multi-select system preference don't save when all checks are removed
  • Bug 31154 - Batch item modification fails when "Use default values" is checked
  • Bug 31497 - Quick add: mandatory fields save as empty when not filled in before first save attempt
  • Bug 31818 - Advanced editor doesn't show keyboard shortcuts

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 apply the test plan and run the QA script. Leaving the functional or code review for someone knowing that area. Or just that I'm not confident enough in my code review and need a second pair if eyes.

Began reviewing Bug 32030 - Electronic resource management (ERM)

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.

Began testing Bug 32030 - Electronic resource management (ERM)

Guide signoff session

Very low attendance. 2 people trained on patch testing. Team results: 1 ticket out of the Needs Signoff queue: 1 Signoff.

Misc tasks and work on tickets: Analysis or implementation

New tickets opened

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

Bug 32065 - Invalid YAML for some system preferences