Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Check-Out: Validate Check-Out Form

Description

Purpose: To validate that the patron ID (username, currently, but default identifier will likely be configurable) is populated and valid and that the Item barcode is valid.

Scenarios:

  1. Scenario

    • Given a patron hasn't been selected on the checkout page in Scan

    • When an item is selected (entered into the barcode field and +Add Item is clicked)

    • Then the patron field should display the following validation error: "Please fill this out to continue"

  2. Scenario

    • Give scenario 1

    • When a valid patron is subsequently found

    • Then:

      • Previously entered barcode remains entered into the barcode field under scanned items

      • User can click "+ Add Item" button to create the loan record

  3. Scenario

    • Given the patron field on the checkout screen

    • When an invalid username is entered (username doesn't exist*)

    • Then the patron field should display the following validation error: "User with this ID does not exist"

  4. Scenario

    • Given the item field on the checkout screen

    • When an invalid barcode is entered (barcode doesn't exist)

    • Then the item field should display the following validation error: "Item with this barcode does not exist"

*Note: We may later display messaging for inactive or blocked users, but that will likely come as a different type of notification.

Environment

None

Potential Workaround

None

Attachments

5
  • 31 Mar 2017, 09:11 PM
  • 31 Mar 2017, 09:11 PM
  • 31 Mar 2017, 09:11 PM
  • 31 Mar 2017, 08:38 PM
  • 31 Mar 2017, 08:38 PM

Checklist

hide

TestRail: Results

Activity

Show:

Niels Erik Nielsen July 13, 2017 at 11:46 AM

Two of the four scenarios no longer pass when I test ui-scan against yesterday's folio-testing-backend black-box (2.0.0-testing.20170711) :

Scenario 1 (patron must be scanned before items)
scenario 3 (error on wrong patron id)

This was testing ui-scan tip of master. The regressions may have been introduced a while back, I cannot determine if the were in the most recent release for instance, because that release will not run with the current releases of various stripes components.

Cate Boerema May 8, 2017 at 7:53 AM

Okay, thanks . I added STRIPES-353 (bug) for missing Items under Settings. Will figure out which front-end guy should pick it up.

John Malconian May 5, 2017 at 3:50 PM

I built a new demo with the ui-organization module enabled. There are now settings for Users and Organization. I don't see items under settings. The items UI displays the same behavior you describe above. The demo is using the latest released version of ui-items (v0.1.1) so I'm not sure if what you are seeing is a regression or not? Probably something the UI team can help sort out.

Cate Boerema May 5, 2017 at 8:46 AM

Thanks, . There are still some things I don't see in the demo which are unrelated to this story: Items and Organization under Settings. Also, the collapsible detail pane for Items isn't working well anymore (the details pane should not be open by default and there should be an X in the upper left to close the pane). I am pretty sure I saw this working well in an earlier version of the other demo site.

Niels Erik Nielsen May 4, 2017 at 10:04 PM

Thank you John, demo contains what it needs for Scan.

Done

Details

Assignee

Reporter

Labels

Priority

Sprint

Parent

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created March 22, 2017 at 10:49 AM
Updated March 3, 2022 at 4:51 PM
Resolved May 4, 2017 at 10:04 PM
TestRail: Cases
TestRail: Runs

Flag notifications