Repository object tests

From AtoM wiki
Revision as of 18:59, 12 August 2014 by Dan (talk | contribs) (Minor fix to page title and breadcrumb)

Main Page > Development > Development/Functional testing > Development/Functional testing/Repository object tests

Create

User should be able to create and save a repository object

  • Clicking on Add > Repositories (or Archival institution - depends on user label settings) opens blank repository object edit screen
  • Clicking on the Add new button in the repository show screen opens blank repository object edit screen
  • Can enter data in all fields
  • Can enter multiple values in all multi-value fields
  • Clicking Create closes edit screen and opens show screen
  • All information added to created record is visible in show screen

Read

User should be able to view all fields and follow all links

  • Website address should appear as a functioning link
    • Should also appear as a button link in the right-hand context sidebar
    • If email is added to contact information, it should also function as a mailto: link
  • In information object edit screen, can select repository in repository field
  • When an information object is linked to a repository, repository context menu box shows information object as link under holdings
  • Information objects displayed as holdings in context menu box are alphabetically sorted

Update

User should be able to edit and save changes to a repository object

  • Clicking Edit opens edit screen
  • Clicking title bar opens edit screen
  • Can edit data in all fields
  • Can delete values from multi-value fields and enter new values
  • Can select new values from drop-down lists
  • Can edit contact information area
  • Can add new contact
  • Can designate only one contact as primary
  • Clicking Save closes edit screen and opens show screen
  • All changes to saved repository object are visible on show screen
  • Clicking Cancel closes edit screen and opens show screen with no changes saved
  • Changed authorized form of name shows on related information object show screens
  • Changed identifier shows on related information object show screens (as part of reference code)
  • Changed country in contact area shows on related information object show screens (as part of reference code)

Theming

  • User should be able to click "Edit theme" button in button block and be taken to theme edit page
  • Can select a color using the color picker
    • preview of the color appears in little color swatch of color picker
  • Can upload a logo
    • If logo is bigger than recommended size, it will be cropped
    • If logo filesize is too large or wrong format, user is given warning message
  • Can upload a banner
  • If banner is bigger than recommended size, it will be cropped
  • If banner filesize is too large or banner is wrong format, user is given warning message
  • Can change existing logo or banner
    • Clicking checkbox to remove then saving results in no logo or banner
    • Can upload a different logo or banner (requires browser refresh)
  • Can add custom page content
    • Will support HTML and inline CSS content
    • Will support digital content (e.g. images, vids, etc) if path is present and accessible (e.g. on same server)
    • Will support embeds/iframes, e.g. YouTube videos, etc.
    • User can save, view custom content, then return and edit it later, and see changes when saving
  • Upon saving, theme elements (background color, logo, banner, custom content) are visible on repository show screen
  • Background color and repository logo are visible on any related information objects

Digital object upload

  • Administrator can set limit on uploads to information objects associated with the repository
    • Can set to disable uploads, set a specific limit in GBs, or set as unlimited
    • Setting should not override application-wide upload settings in Admin > Settings
  • When uploads are disabled, users can link external digital objects, but not upload new ones to related information objects
  • When specific upload limit is set, user should not be able to continue uploading content (though linking is allowed)

Translate

User should be able to translate repository object from source language to another language

  • When editing a repository object in a language different from the source language, the original language values appear above the appropriate fields
  • If they have been translated, the following appear in the current language: repository type, country, status, level of detail, language, scripts
  • The saved record shows all translations
  • If the authorized form of name has been translated, the name of the repository appears in the correct language in related information object show screens

Delete

Users should be able to delete data from repository objects and delete repository objects

  • Can delete data from all fields
  • Saving record opens show screen with deleted data removed
  • Clicking delete results in warning
  • Clicking cancel aborts the delete process and returns the user to the show screen
  • Clicking Confirm deletes the record and returns the user to the repository object list screen
  • Associated information objects are not deleted