Uploaded image for project: 'ui-oai-pmh'
  1. ui-oai-pmh
  2. UIOAIPMH-12

Validate set creation or change

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Closed (View Workflow)
    • Priority: P2
    • Resolution: Done
    • Affects Version/s: None
    • Fix Version/s: 1.3.0
    • Labels:
      None
    • Template:
    • Sprint:
      Gulfstream Sprint 97
    • Story Points:
      8
    • Development Team:
      Gulfstream

      Description

      Purpose:

      As long as set rules are restricted by the OAI-PMH protocol and additional records filtration is going to be performed on the set basis, the system should validate set before saving, so that set hierarchy was correct and filtration wasn't broken.

      User story statement:

      As a system administrator,
      I want system to forbid saving invalid sets
      so that sets hierarchy complies to OAI-PMH protocol and allows proper records filtering

      Scenarios:

      1. Scenario - Minimal set information validation success

      • Given user creates/edits the set
      • When user fills in set name
      • And at least one filtering condition with specified Value and Set spec is activated
      • And all other set validation rules are in compliance
      • Then set can be saved

      2. Scenario - Minimal set information validation error (required fields)

      • Given user creates/edits the set
      • When user tries to save a set
      • And at least one of the required fields isn't specified (set name, filtering condition value, filtering condition set spec)
      • Then focus this field
      • And display a message "This field cannot be empty"
      • And page with all set changes isn't cleared so that user can correct information and try to save again

      3. Scenario - Minimal set information validation error (empty filtering conditions list)

      • Given user creates/edits the set
      • When user tries to save a set
      • And none of the filtering conditions is activated
      • Then display a message "Set filtering conditions list cannot be empty. Please, add at least one filtering condition to save set."
      • And page with all set changes isn't cleared so that user can correct information and try to save again

      4. Scenario - Field length validation success

      • Given user creates/edits the set
      • When user fills in text field or text area
      • And text fields for Set Spec of filtering conditions contain less than 51 characters
      • And all other text fields contain less than 256 characters
      • And all text areas contain less than 1500 characters
      • And all other set validation rules are in compliance
      • Then set can be saved

      5. Scenario - Field length validation error

      • Given user creates/edits the set
      • When user fills in text field or text area
      • And text field for Set Spec of filtering conditions contains more than 50 characters or other text field contains 256 or more characters or text area contains1500 or more characters
      • Then focus this field
      • And display a message "Field cannot be more than 255 characters long" or "Field cannot be more than 1499 characters long"
      • And page with all set changes isn't cleared so that user can correct information and try to save again

      6. Scenario - Set spec allowed characters

      • Given user creates/edits the set
      • When user fills in set spec for filtering condition
      • And all characters are within URI unreserved characters: [A-Z][a-z][0-9]("-" | "_" | "." | "!" | "~" | "*" | "'" | "(" | ")")
      • Then set can be saved

      7. Scenario - Set spec unallowed characters

      • Given user creates/edits the set
      • When user fills in set spec for filtering condition
      • And not all characters are within URI unreserved characters: [A-Z][a-z][0-9]("-" | "_" | "." | "!" | "~" | "*" | "'" | "(" | ")")
      • Then focus this field
      • And display a message "Set spec can only use A-Z a-z 0-9 - _ . ! ~ * ` ( )"
      • And page with all set changes isn't cleared so that user can correct information and try to save again

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                Dmitriy Litvinenko Dmitriy Litvinenko
                Reporter:
                Anastasiia Zakharova Anastasiia Zakharova (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases