[Koha-bugs] [Bug 31028] Add 'Report a concern' feature for patrons to report concerns about catalog records

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31028

--- Comment #215 from David Nind <david at davidnind.com> ---
Here is the draft test plan I used. See also the Specification attached to the
bug. The notes referenced are included in comment #214.

1. Apply patches
2. Update database: updatedatabase
3. Run DBIC: dbic (not sure if this is required)
4. Enable the new system preference: OpacCatalogConcerns [see note 1]

5. Report a catalog concern from the OPAC:
   5.1 Search for a record and view the details page
   5.2 There is now a "Report a concern" link in the actions box on the
right-hand sidebar (under "Suggest a purchase")
   5.3 Click on "Report a concern"
   5.4 Add some information to the form (Title, information for each of the
headings) and click Submit
   5.5 Log out from the OPAC and click on the "Report a concern" link for a
record - you should be prompted to log in. After logging in, you are then
redirected back to the record page and the form is displayed to report a
concern.

6. Manage catalog concerns from the staff interface:
   6.1 Disable these system preferences: suggestions, OPACReportProblem, and
AllowCheckoutNotes
   6.2 From the staff interface, select the link in the block after the module
options (the "Call to action" area): where there are concerns, "Catalog
concerns pending: X" is displayed [see note 2]
   OR
   6.3 Go to Cataloging > Reports > Catalog concerns
   6.4 The concern(s) you entered in the OPAC should be listed
   6.5 Click on "Details" in the actions column
       ==> Ticket details displayed in a modal window [see note 3]
   6.6 Add some text in the update field for the concern, select the Notify
checkbox, and click on either the Resolve or Comment buttons [see note 4]
   6.7 If Resolve clicked, then this will no longer be displayed in the list of
concerns (make sure the 'Hide resolve' or 'Show all' toggles work and display
concerns raised correctly based on status) 
   6.8 If Comment clicked, this will continue to be displayed in the list of
concerns
   6.9 Check that the filters for each column work as expected
   6.10 [Not sure how comments are displayed, assume when viewing the details
for a concern that any previous comments are displayed in the modal window with
the date]
   6.11 Testing notifications - see step 8.2

7. Report a catalog concern from the staff interface [see note 5]:
   7.1 Enable the CatalogConcerns system preference
   7.1 Search for a record and view the details page
   7.2 Select New > New catalog concern
   7.4 Add some information to the form (information for each of the headings)
and click Confirm

8. Other things to test:

8.1 API: not sure what to test here (if needed)
    . Enable the RESTPublicAPI system preference
    . Go to http://127.0.0.1:8080/api/v1/.html
    . Not that there are APIs for addTicket, addTicketPublic, addTicketUpdate,
deleteTicket, getTicket, listTicketUpdates, listTickets, and updateTicket

8.2 Notifications [see note 6] [need to expand and actually test this]: 
    . There are four new notice templates: TICKET_NOTIFY, TICKET_ACKNOWLEDGEME,
TICKET_RESOLVE, TICKET_UPDATE
    . Set up KTD so that email can be sent (using a Gmail address and an app
password)
    . Set up a patron with your Gmail email address
    . Setup system preference CatalogerEmails with your Gmail email address
    . Trigger the various notices and make sure they work as expected:
      . TICKET_ACKNOWLEDGEME: email to patron when they raise a concern
      . TICKET_NOTIFY: email to library staff when a concern is raised
      . TICKET_UPDATE: add an update to a concern
      . TICKET_RESOLVE: when concern marked as resolved

8.3 Test with OPACReportProblem enabled:
    . Enable the system preference
    . Submit a "Report a problem" report from the OPAC
    . Check that this works as expected in the staff interface, and that both
pending problem reports and catalog concerns are displayed
    . BONUS tests: test various combinations of enabling and disabling
suggestions, OPACReportProblem, AllowCheckoutNotes, and CatalogConcerns system
preferences [not sure whether this is really required]

8.4 Test a non-super librarian and set them up so that they can manage catalog
concerns. What permissions are required? I initially thought you needed the
manage_problem_reports permission, then I couldn't figure out the correct
permissions to give [see also note 7]. These steps need updating once figured
out:
    . Log in as a non-super librarian (needs manage_problem_reports permission,
for example Henry Acevedo with a basic set of persmissions including:
catalogue, circulate, borrowers, reserveforothers, editcatalogue,
updatecharges, reports, lists, clubs, manage_problem_reports)
    . Check that they can view and manage catalog concerns

8.4 Table configuration: have some active catalog concerns, click configure,
hide status column by default, check that you can toggle the status column on
and off.

8.5 Customise the catalog concern help text and template [see note 8]:
   . Go to Tools > HTML customizations
   . Note that there are two entries available for editing: CatalogConcernHelp
and CatalogConcernTemplate
   . Make some edits to these entries
   . From the OPAC, report a concern for a record
   . The changes you made should be reflected in the report a concern form

-- 
You are receiving this mail because:
You are watching all bug changes.