AtoM wiki - User contributions [en]

Development/Functional testing/Digital object tests

2020-09-19T01:35:48Z

PeterVG:

{{#pagetitle: Digital object tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing]] > Development/Functional testing/Digital object tests

== General behaviour ==
*Clicking Link digital object in information object show screen opens Upload digital objects screen
*User can browse for a digital object to upload
*User can link to an external URL to upload a digital object
*Clicking Create opens the show screen for the information object with digital object displayed as reference display copy
*Digital object metadata are automatically added to the information object show screen, as follows: Filename (if object was uploaded from file system), URL (if object was uploaded from external link) Media type, Mimetype, Filesize, Uploaded
**NOTE: when testing, remember these elements can be hidden to public users via Visible elements module
*Digital objects appear in browse results in appropriate categories: audio, image, other, text, video
*Digital objects appear in carousel viewer at aggregate levels of description
*Digital objects can be located via digital object browse page

== Text files ==
*In the information object show screen, clicking on the reference display object opens the master digital object (if the user's permissions are set to allow it)
*Clicking on the reference display area allows user to open or download object
*Unauthenticated users and users without view master permissions cannot open and download master digital object

== Image files ==
*In the information object show screen, clicking on the reference display object opens the master digital object or allows the user to open or save the object
*Users can right-click or command-click the image representation and receive options: Open link in new tab; Open link in new window; Bookmark link; Save link as; Send link; Copy link location; View image; Copy image; Copy image location; Save image as; Send image; and View image info.
*Unauthenticated users and users without view master permissions cannot open and download master digital object

== Video files ==
*Clicking "play" in the reference display copy plays the video
*Associated audio streams are also played
*Left-clicking "download movie" opens up the master digital object (depends on browser support)
*Right-clicking "download movie" allows the user to save the save the file (eg "Save link as")
*Users can right-click or command-click "download movie" and receive options: Open link in new tab; Open link in new window; Bookmark link; Save link as; Send link; and Copy link location.
*Unauthenticated users and users without view master permissions cannot open and download master digital object

== Audio files ==
*Clicking "play" in the reference display copy plays the audio file, or prompts user to download the file, depending on the format
*Left-clicking "download audio" opens up the master digital object (depends on browser support)
*Right-clicking "download audio" allows the user to save the save the file (eg "Save link as")
*Users can right-click or command-click "download audio" and receive options: Open link in new tab; Open link in new window; Bookmark link; Save link as; Send link; and Copy link location.

== Multi-page files ==
*User can upload multi-page files
*All pages in the multi-page file are uploaded
*Reference display copy shows first page of a multi-page file unless a different page has been chosen for display (see Digital Object Derivatives in [[Development/Functional_testing/Admin_tests]])
*User can page through pages in reference display copy
*Clicking on reference display copy opens master digital object in a new window

== Editing digital object ==
*In information object view screen, clicking on "Edit digital object" button opens the edit digital object view screen
*User can change media type
*User can delete reference representation and substitute new representation
*User can delete thumbnail representation and substitute new representation
*Clicking Save opens information object show screen with all changes saved
*Substituted reference and thumbnail representations are correctly resized
*Clicking Delete results in confirmation message: "Are you sure you want to delete the digital object linked to....?"
**Clicking Cancel returns user to digital object edit screen and digital object is not deleted
**Clicking Confirm opens the information object show screen and digital object is deleted

== Multi-file upload ==
*In information object show screen, clicking Import digital objects opens Upload multiple digital objects screen
*User can edit title it Title field
*User can select level of description
*Clicking the "select files" link opens a file browser
*User can select multiple objects from the file browser
*Digital objects are previewed, along with Title, Filename, and Filesize
*Can edit Title for previewed objects
*Can delete previewed objects
*If filesize exceeds maximum allowed upload size, a warning message appears
*If digital object is a duplicate of another digital object in the same upload, a warning message appears
*User can select more files before importing
*Clicking Import opens information object show screen
*Carousel viewer is visible in in information object show screen
*Objects are displayed as children of the current record in the hierarchy treeview
*Child level show screens open digital object displayed as reference display copy; behaviour is same as described in General behaviour, above

== Enhanced digital object display ==

*'''When an AtoM user links a digital object to an archival description:'''
*Then the "Digital object metadata" section on the archival description view page will include an "Access Copies" subsection.
*And an unauthenticated user will not see a digital object and its "Access copies" metadata if the archival description it is attached to has a "draft" instead of "published" status.
*And Clicking on the "Access copies" subsection label link will collapse or expand the subsection.
*And the "Access Copies" subsection will include metadata about the "Master file", "Reference copy", and "Thumbnail copy" representations of the digital object. Specifically: filename, media type, mime-type, filesize, and uploaded.
*And an administrator user can toggle the display of specific "Digital object metadata" section fields on or off in the *Admin > Settings > Visible Elements* section. This only affects display for unauthenticated users. Any authenticated users will see all metadata elements in each section as long as those fields contain a value.
*And when the Reference representation or Thumbnail representation is deleted via the "Edit digital object" page, then the "Reference copy" and/or "Thumbnail copy" metadata is no longer displayed on the archival description view page. Additionally, the thumbnail is not show on Browse pages and the reference copy is not displayed on view pages.
*And filename for each representation is either shown as plain text or as a hyperlink. If it is a hyperlink, it indicates that this user has access to this representation. Clicking on the hyperlink will load this representation.
*And if the filename is in hyperlink format, the icon underneath the "Master file", "Reference copy", and "Thumbnail copy" label is coloured black. It is coloured grey if the user does not have access and the hyperlink is not shown.
* And access to the "Master file", "Reference copy", and "Thumbnail copy" can be configured per user group. The "Access master", "Access reference", and/or "Access thumbnail" permission can be set to "Grant" or "Deny" for any user group, including unauthenticated ("anonymous") users.
* And access to the "Master file", "Reference copy", and "Thumbnail copy" may be overridden by actionable PREMIS rights configured for individual archival descriptions and their digital object. If a PREMIS right is added to an archival description where the "Act" is "Disseminate" and the "Restriction" is "Disallow", then the hyperlinks in the Digital object metadata section are no longer active, all the document icons are coloured grey, and the reference copy of the digital object is no longer displayed on the archival description view page. Instead the customizable text of the "Disallow statement" is displayed at the top of the page as well as in a "Permissions" field for each Access copy representation (e.g. "Access to this record is restricted because it contains personal or confidential information. Please contact the Reference Archivist for more information on accessing this record.").
* And if the "Restriction" is changed to "Conditional" and the default permission settings are enabled then the "Reference copy" and "Thumbnail copy" become available again as hyperlinks and these representations are once again displayed on the AtoM templates. The customizable text for the "Condition Statement" is displayed in a "Permissions" field for the "Master file" representation (e.g. "This record has not yet been reviewed for personal or confidential information. Please contact the Reference Archivist to request access and initiate an access review.").

== Enhanced digital object display (Preservation copies) ==

*'''When a user of a preservation system (e.g. Archivematica) has sent a DIP upload to an archival description slug in AtoM:'''
*Then an authenticated user is able to see thumbnails of the digital objects from the DIP in the digital object carousel when navigating to this AtoM slug.
*And an unauthenticated user will not see a digital object and its metadata if the archival description it is attached to has a "draft" instead of "published" status.

*'''When selecting one of the digital objects included in the DIP upload:'''
*Then the "Digital object metadata" section on the archival description view page will include a "Preservation Copies" and "Access Copies" subsection.
*And clicking on either of these subsection label links will collapse or expand the subsection.
*And the "Preservation Copies" subsection will include metadata about the "Original file" and "Preservation copy" representations that are stored in the preservation system.
*And if the preservation system did not generate a preservation copy then only "Original file" metadata is shown.
*And the "Preservation copy" metadata elements include filename, filesize, and normalized.
*And if the preservation action system statement option is enabled then the user will also see a "Permissions" field with custom text that is populated by an Administrator (e.g. "Access only provided on research room computer.")
*And the "Original file" metadata may includes filename, file format name, file format version, format registry key, format registry name, filesize, and ingested.
*And if the preservation action system statement option is enabled, the user will also see a "Permissions" field with custom text that is populated by an Administrator (e.g. "Access only provided on research room computer.")
*And an administrator user can toggle the display of specific "Digital object metadata" section fields on or off in the *Admin > Settings > Visible elements* section. This only affects display for unauthenticted users. Any authenticated users will see all metadata elements in each section as long as those fields contain a value.
*And if the user is logged in and belongs to the "authenticated" group, then they will also see the File UUID and AIP UUID for the Original file.
*And if the preservation copies came from the Archivematica preservation system and AtoM has enabled the "arStorageServicePlugin" then authenticated users with Download AIP permissions will also see a "Download file" and "Download AIP" link next to each UUID. Clicking on them will fetch the file or the full AIP from the preservation system.
*And if the user has "Download file" and "Download AIP" permissions then the box icon under the "Original file" label will be coloured black. Otherwise it is coloured grey.
*And since access to the preservation copy is only available via the preservation system, the box icon under the "Preservation copy" label is always coloured grey.

*'''When the preservation system uploads a DIP with digital objects to AtoM:'''
* Then it will generate "Master file", "Reference copy", and "Thumbnail copy" representations with metadata displayed in the "Access copies" subsection (see "Enhanced digital object display" above)

[[Category:Development documentation]]

__NOTOC__

Development/Functional testing/Digital object tests

2020-09-19T01:28:38Z

PeterVG:

Development/Functional testing/Single sign-on (CAS) tests

2020-09-09T22:17:24Z

PeterVG: /* About */

{{#pagetitle: Single sign-on (CAS) tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing]] > Development/Functional testing/Single sign-on (CAS) tests

==About==
Centralized Authentication Service (CAS) is an enterprise single sign-on protocol that can be implemented in AtoM by enabling the arCasPlugin and by registering user accounts with a CAS server. For more about CAS see https://www.apereo.org/projects/cas.

For testing purposes, a public CAS demo server can be used. See https://python-cas-flask-example.herokuapp.com/. The username ''admin'' and the password ''django-cas-ng'' can be used to authenticate on the demo server.

The arCasPlugin also provides an optional mechanism for dynamically setting AclUserGroup membership on each login, based on the presence or absence of expected values in the attributes returned from the CAS server during p3/serviceValidate (CAS version 3.0 only).

==Single sign-on login==

Test scenario: A user is authenticated through a Central Authentication Service (CAS) single sign-on form and is automatically logged in to an AtoM session.

Given: The institution hosting AtoM is running a CAS server.

And: The user has an active CAS account.

And: The user account is present in the AtoM group member list on the CAS server.

When: The user starts a new session on the institution’s domain and navigates to an AtoM page that requires authentication.

----

Then: The unauthenticated user is redirected to the CAS login form where they enter their CAS username and password.

And: The CAS server successfully authenticates the user, assigns them a session service ticket, and redirects them to the AtoM server.

And: AtoM sends the service ticket to the CAS server over HTTPS for validation.

And: The CAS server sends a success response to AtoM which includes the user attributes set on the CAS server.

And: AtoM creates a new user account if one matching the CAS account doesn’t already exist.

And: AtoM sets the user session cookie (with the service ticket stripped off) and redirects the user to a new, authenticated AtoM session.

And: AtoM checks its configuration file to see if there are expected CAS attributes for user groups. If so, AtoM checks whether the user has the appropriate attribute for a given group and elevates their user authorization to become an authenticated member of one or more of these groups if this is the case (e.g. editor, translator, administrator).
And: When the user logs out of AtoM, they will also be automatically logged out of CAS.

----

Given: A user account is created on the CAS server and the user has logged into AtoM

When: An AtoM administrator user deletes that user account in AtoM

Then: The user is still able to log-in using their CAS account and their AtoM account is re-created

Development/Functional testing/Single sign-on (CAS) tests

2020-09-09T22:14:37Z

PeterVG: /* Single sign-on login */

{{#pagetitle: Single sign-on (CAS) tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing]] > Development/Functional testing/Single sign-on (CAS) tests

==About==
Centralized Authentication Service (CAS) is an enterprise single sign-on protocol that can be implemented in AtoM by enabling the arCasPlugin and by registering user accounts with a CAS server. For more about CAS see https://www.apereo.org/projects/cas.

For testing purposes, a public CAS demo server can be used. See https://django-cas-ng-demo-server.herokuapp.com/cas/) s. The username ''admin'' and the password ''django-cas-ng'' can be used to authenticate on the demo server.

The arCasPlugin also provides an optional mechanism for dynamically setting AclUserGroup membership on each login, based on the presence or absence of expected values in the attributes returned from the CAS server during p3/serviceValidate (CAS version 3.0 only).

==Single sign-on login==

Test scenario: A user is authenticated through a Central Authentication Service (CAS) single sign-on form and is automatically logged in to an AtoM session.

Given: The institution hosting AtoM is running a CAS server.

And: The user has an active CAS account.

And: The user account is present in the AtoM group member list on the CAS server.

When: The user starts a new session on the institution’s domain and navigates to an AtoM page that requires authentication.

----

Then: The unauthenticated user is redirected to the CAS login form where they enter their CAS username and password.

And: The CAS server successfully authenticates the user, assigns them a session service ticket, and redirects them to the AtoM server.

And: AtoM sends the service ticket to the CAS server over HTTPS for validation.

And: The CAS server sends a success response to AtoM which includes the user attributes set on the CAS server.

And: AtoM creates a new user account if one matching the CAS account doesn’t already exist.

And: AtoM sets the user session cookie (with the service ticket stripped off) and redirects the user to a new, authenticated AtoM session.

And: AtoM checks its configuration file to see if there are expected CAS attributes for user groups. If so, AtoM checks whether the user has the appropriate attribute for a given group and elevates their user authorization to become an authenticated member of one or more of these groups if this is the case (e.g. editor, translator, administrator).
And: When the user logs out of AtoM, they will also be automatically logged out of CAS.

----

Given: A user account is created on the CAS server and the user has logged into AtoM

When: An AtoM administrator user deletes that user account in AtoM

Then: The user is still able to log-in using their CAS account and their AtoM account is re-created

Development/Functional testing/Single sign-on (CAS) tests

2020-09-09T22:11:15Z

PeterVG:

{{#pagetitle: Single sign-on (CAS) tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing]] > Development/Functional testing/Single sign-on (CAS) tests

==About==
Centralized Authentication Service (CAS) is an enterprise single sign-on protocol that can be implemented in AtoM by enabling the arCasPlugin and by registering user accounts with a CAS server. For more about CAS see https://www.apereo.org/projects/cas.

For testing purposes, a public CAS demo server can be used. See https://django-cas-ng-demo-server.herokuapp.com/cas/) s. The username ''admin'' and the password ''django-cas-ng'' can be used to authenticate on the demo server.

The arCasPlugin also provides an optional mechanism for dynamically setting AclUserGroup membership on each login, based on the presence or absence of expected values in the attributes returned from the CAS server during p3/serviceValidate (CAS version 3.0 only).

==Single sign-on login==

Test scenario: A user is authenticated through a Central Authentication Service (CAS) single sign-on form and is automatically logged in to an AtoM session.

Given: The institution hosting AtoM is running a CAS server.
And: The user has an active CAS account.
And: The user account is present in the AtoM group member list on the CAS server.
When: The user starts a new session on the institution’s domain and navigates to an AtoM page that requires authentication.

Then: The unauthenticated user is redirected to the CAS login form where they enter their CAS username and password.
And: The CAS server successfully authenticates the user, assigns them a session service ticket, and redirects them to the AtoM server.
And: AtoM sends the service ticket to the CAS server over HTTPS for validation.
And: The CAS server sends a success response to AtoM which includes the user attributes set on the CAS server.
And: AtoM creates a new user account if one matching the CAS account doesn’t already exist.
And: AtoM sets the user session cookie (with the service ticket stripped off) and redirects the user to a new, authenticated AtoM session.
And: AtoM checks its configuration file to see if there are expected CAS attributes for user groups. If so, AtoM checks whether the user has the appropriate attribute for a given group and elevates their user authorization to become an authenticated member of one or more of these groups if this is the case (e.g. editor, translator, administrator).
And: When the user logs out of AtoM, they will also be automatically logged out of CAS.

Given: A user account is created on the CAS server and the user has logged into AtoM
When: An AtoM administrator user deletes that user account in AtoM
Then: The user is still able to log-in using their CAS account and their AtoM account is re-created

Development/Functional testing/Single sign-on (CAS) tests

2020-09-09T22:06:21Z

PeterVG:

PeterVG: /* Create */

{{#pagetitle: Accession module tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing]] > Development/Fucntional testing/Accession module tests

<admonition type="tip">
General information on the Accessions module can be found at:

* https://www.accesstomemory.org/docs/latest/user-manual/add-edit-content/accessions/
</admonition>

(Accession module tests updated 2018-09-27 to conform with AtoM 2.4)
== Create ==
A Logged-in User should be able to create and save an accession record
*Clicking '''Add > Accession record''' opens accession record edit screen
**Accession number data field is automatically populated by the system with a date and incremental integer. This field cannot be altered by the user prior to v2.4. In 2.4 and after, the field can always be edited, and may not be populated if the Accession mask setting in Admin > Settings > Identifiers is set to 'No'.
**Acquisition date field is automatically populated by the system with the current day's date. User can change this date with the calendar GUI.
*User can enter data into required fields (free text).
*Clicking Create closes edit screen and opens view accession record screen
*Clicking Edit opens edit screen
*User clicks Donor/Transferring body area and section for data entry opens.
**Clicking Add new opens the donor dialog box. Fill in donor name and contact information then click Submit. Donor name should be visible in accession record edit template with the options to edit (pencil icon), delete (x symbol) or add another donor to the accession record (add new hyperlink text). User should be able to add and edit/delete multiple donors.
**Edit the existing donor name and contact information by clicking on the pencil icon. Donor dialog box opens.
**Select the delete symbol to delete the donor information.
*User clicks Admin area and begins to add/edit information in the Admin area.
**Can select from drop-down list.
**Can select creator name from dynamic list selection or can enter new creator name.
**Can add free text to data entry boxes.
***Option to click save and make sure creator name is presented in the view accession record screen as a hyperlink. Click on hyperlink creator name and user should be redirected to view authority record screen
*User clicks Add new rights in button block after saving description (see also [[Development/Functional testing/Rights module tests|Rights module tests]])
**Clicking Add new opens the rights edit page
**Can select Acts from drop-down pick list provides users with 7 acts to select: delete, discover, display, disseminate, modify, migrate and replicate
**Can select restriction drop-down list, 3 options: Allow, Conditional, and Disallow
**Can modify date field "start" and enter data into date field "end"
**Can select existing names from dynamic list in Rights holder field, or can input new name into field.
**Can enter free text in Rights notes field
**Can select Basis from drop-down list: copyright, license, statute, policy and donor
**Can add multiple Rights to a single Basis
**Can Click on Submit. Rights should be visible in accession record edit template with the options to edit, delete; add another right to the accession record continues to work from the
***Option to click save and make sure rights holder name is presented in the view accession record screen as a hyperlink. Click on hyperlink rights holder name and user should be redirected to view rights holder screen.
*Click save and view accession record screen.

== Read ==
*A logged-in User should be able to read all content and link to related content
**Accession number
**Acquisition date
**Source of acquisition
**Location information
**Related donor should provide a link to view donor screen
**Contact information
**Acquisition type
**Resource type
**Title
**Creators should provide a link to view authority record screen
**Archival history
**Scope and content
**Appraisal, destruction and scheduling
**Physical condition
**Received units
**Processing status
**Processing priority
**Processing notes
**Related right should include information about the act, restrictions, start & end date, rights holder, notes and basis.
**Rights holder should provide a link to view rights holder screen
*Unauthenticated users cannot enter URL to an accession and navigate directly there; option to navigate to accessions is not visible in menus for unauthenticated users

== Edit ==
A logged-in User should be able to edit the accession record
*One method of editing is to Click the Edit button at the bottom of the view accession record screen and user should be directed to the edit accession record screen
*Another method of editing is to Click on the Area title bar of the section you want to edit.
**Click on accession number. Accession number is editable. (In instances prior to 2.4 this data is NOT editable.)
**All other data entry fields in the accession record can be edited.
*Click on Save to be directed to the View accession record screen.
*Click on Create information object button. User should be directed to view archival description screen.
**Title (ISAD) Title Proper (RAD) should be populated with information from title of accession record.
**Name of creator should be populated with information from accession record.
**Archival history (ISAD) Custodial history (RAD) should be populated with information from accession record.
**Scope and content should be populated with information from accession record.
**Physical characteristics (ISAD) Physical condition (RAD) and technical requirements should be populated with information from accession record
**Name access point should be populated with the creator name from the accession record
**Rights should be populated with the rights added into the accession record
**Accession number should be a hyperlink. Click on link and user is directed to view accession record screen
*Click on Deaccession button and user is directed to edit deaccession record edit template.
*Click on Add accrual button and user is directed to an accrual record/accession edit template.
*Click on Delete button and user is directed to a question screen that asks for confirmation of deletion of specific accession record.

== Manage ==
A logged-in User can manage accession records using browse and search

*Can select accessions from the Manage menu bar drop-down list
*Can sort accessions by name Most Recent, Accession Number, Title, or Acquisition Date
*Can click on hyperlink accession identifier or title and be directed to View accession record screen
*Can search accessions by partial or exact accession identifier, and on other fields from the accessions dedicated search box (but see [https://projects.artefactual.com/issues/9290 #9290])

-----

* [[Development/Functional_testing|Back to Functional testing]]
* [[Development|Back to Development]]

[[Category: Development documentation]]

Development/Functional testing/Treeview hierarchy tests

2019-04-16T20:11:13Z

PeterVG: /* Dragging and dropping objects */

Development/Functional testing/Treeview hierarchy tests

2019-04-16T20:08:26Z

PeterVG: /* Navigating large aggregations */

Development/Functional testing/Treeview hierarchy tests

2019-04-16T19:54:47Z

PeterVG: /* Dragging and dropping objects */

Development/Functional testing/Treeview hierarchy tests

2019-04-16T19:54:21Z

PeterVG: /* Dragging and dropping objects */

{{#pagetitle: Treeview hierarchy tests }}
[[Main Page]] > [[Development]] > [[Development/Functional testing|Functional testing]] > Treeview hierarchy tests

User should be able to navigate hierarchies by expanding and collapsing objects, clicking on objects to open their show screens, and dragging and dropping objects to change their position within the hierarchy.

== Expanding and collapsing objects ==

*Opening a show screen with multiple levels should show the immediate lower levels with > signs next to them in the context menu box
*Clicking on a > sign should expand the lower level to show its lower levels
*The > sign should turn into a V sign when the object is expanded
*Clicking on the V sign should collapse the object

== Navigating large aggregations ==

* In show screens for information objects or taxonomy terms with more than 10 siblings or children, the hierarchy treeview shows only the first 6 siblings or children
* A button with ellipses [...] appears as a node at the bottom of the treeview
** Clicking on the button shows 4 more objects
** If the aggregation has more than 10 siblings, the [...] button will reappear beneath the 10th object.
*** Clicking the ellipses button again will create a slider to the right of the treeview, and will display 4 more objects at a time.
*** As the user scrolls down the slider, the treeview will automatically keep populating the hierarchy in 4-object increments until the user selects the desired object or all sibling information objects are displayed

* When selecting an information object for display in the show screen that is lower than 6th in the hierarchy, the object is shown in the hierarchy treeview along with 4 siblings in either direction (up and down). As such, a maximum total of 9 information objects are displayed in the treeview when the showscreen displays an object that is lower than the 6th in the hierarchy - the object currently selected and up to 8 other siblings.
** An ellipses button [...] will be displayed on either side of the treeview hierarchy. Clicking on the button will expand the treeview to display further siblings, in increments of 4.
** If the user has expanded the treeview down the hierarchy, the slider bar will reappear, and the treeview will automatically populate the hierarchy in 4 object increments as the user scrolls down.

== Dragging and dropping objects ==
*User should be able to drag an object with the mouse and drop it into another position under the same parent to re-order siblings.
** Note that the "Move" button should be used to move objects to a new parent in the descriptive hierarchy. See [https://projects.artefactual.com/issues/4358 issue 4358]
*If an object has child levels, dragging and dropping the object into another part under the same parent also moves all of the child levels
*Users should not be able to drag and drop if they are not logged in or do not have update permissions

[[Category:Development documentation]]

Development/Functional testing/Treeview hierarchy tests

2019-04-16T19:54:02Z

PeterVG: /* Dragging and dropping objects */