Uploaded image for project: 'ui-users'
  1. ui-users
  2. UIU-504

CRUD Fee/Fine Payment Methods

    XMLWordPrintable

Details

    • UNAM

    Description

      Purpose: Implement basic CRUD functions for Fee/Fine Payment Methods. Fee/Fine Payment Methods are library-defined.

      As a library administrator I want to be able to create, read, update and delete Fee/Fine Payment Methods so I can collect fee/fine payments from patrons.

      SCENARIOS

      1. Scenario
      Given the Payment Methods page under Settings > Users > Fee/fine
      When displayed
      Then a Fee/Fine Payment Methods control should display under the header "Fee/fine: Payment methods"

      2. Scenario
      Given the new Fee/Fine Payment Methods control
      When a new Fee/Fine Payment Method is created
      Then Fee/Fine Payment Method Name and Refund Method Allowed can be specified
      (Note: Name is required--Refund Method Allowed is not required and will default at "Yes")

      3. Scenario
      Given the Fee/Fine Payment Methods control
      When a new Fee/Fine Payment Method is created
      Then:
      It should display in the list of created Fee/Fine Payment Methods on the Fee/Fine Payment Methods
      page in Settings

      4. Scenario
      Given the Fee/Fine Payment Methods control
      When a new Fee/Fine Payment Method is deleted
      Then:
      It should be removed from the list of created Fee/Fine Payment Methods on the Fee/Fine Payment Methods page in Settings

      5. Scenario
      Given the Fee/Fine Payment Methods control
      When an existing Fee/Fine Payment Method is edited
      Then:
      It should be updated per what is entered by the user
      (Note: Name is required--Refund Method Allowed is not required and will default at "Yes")

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                Akireyram Erika Miranda
                hollyolepm Holly Mistlebauer
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases