Testing

Main Page > Development > Development documentation > Testing

This page is no longer being maintained and may contain inaccurate information. Please see the Archivematica documentation for up-to-date information.

Functional testing starts with a list of steps which must be completed to verify that specific modules and/or features are working in Archivematica. These lists can be used for manual testing, for creating automated functional tests, or for updating automating functional tests when/if the application/interface changes.

The testing procedures described here are updated as of version 1.6.

• See also Scalability testing

Archivematica testing procedures

Transfer

• Process all transfers in the SampleTransfers directory
• Process all transfers in the TestTransfers directory
• Process a transfer using each identification tool
• Process transfers containing submission documentation
• Process a transfer composed of multiple source directories
• Process multiple transfers at once
• Process a transfer with an accession number
• Process transfers with csv metadata import
  • Simple metadata.csv
  • Compound metadata.csv (mix of directories and objects)
• Edit MCP processing configuration xml file
• Add and delete rights metadata
• Add and delete descriptive metadata
• Test all workflows:
  • Quarantine/do not quarantine
  • Remove from quarantine/leave in quarantine
  • SIP creation: Single SIP and continue processing; send to backlog; reject transfer
• Remove transfers from dashboard

Backlog

• Search transfer backlog
• Download Transfer

Appraisal

• Search transfer backlog
• Backlog
  • Add tags to selected files
  • Deselect, collapse, expand
• Test analysis
  • Select objects for report and visualization
  • Tags, examine contents, preview file
• Test file list
  • Date range searching
  • Adding tags
• ArchivesSpace
• Arrangement
  • Add Directory
  • Edit Metadata
  • Delete selected
  • Create
  • Reload

Ingest

• Search transfer backlog
  • Search by: File name, File extension, Accession number, Ingest date, SIP UUID
  • Create SIP by dragging directory from backlog
  • Create SIP by creating new hierarchy
• Test all workflows:
  • Normalize: preservation and access; preservation only; access only; service files for access; no normalization; manual normalization
  • Upload DIP to AtoM
    • Upload DIP with Dublin Core metadata
    • Upload a DIP with a hierarchy
  • Store DIP
    • Store DIP after uploading to a different access system
  • Upload DIP to CONTENTdm
  • Upload DIP to ArchivesSpace
  • Review DIP
• Review normalization
  • Report
  • Directory
• Add and delete rights metadata
• Add and delete descriptive metadata
• Review AIP
  • Validate METS

• Store AIP
• Reject AIP
• Reject DIP
• Remove SIPs from the dashboard

Archival Storage

• Request to delete an AIP
• Search for AIP
  • File UUID; file path; file extension; AIP UUID; AIP name; Part of AIC; AIC identifier; Transfer metadata; Transfer metadata (other)
  • Show files
  • Show AICs
• Create AIC
• Reingest an AIP
  • Reingest and update metadata
  • Reingest and normalize for access
  • Reingest metadata, partial, full
  • Change processing config

Preservation Planning

• Update FPR

Access

• Check links to AtoM

Administration

• Test processing pre-configurations
• Hide AtoM DIP upload link
• Hide DSpace transfer type
• Check transfer source locations
• Fetch levels of description from AtoM
• Check AIP storage locations
• Clear Processing storage locations
• Change PREMIS agent
• Add new users
• Switch users during processing

Storage Service testing procedures

Pipelines

• Create new pipeline

Spaces

• Create new Space
  • Test different access protocols

Locations

• Create new Locations
  • AIP recovery; AIP storage; Currently processing; DIP storage; Transfer backlog; Transfer source
  • Test different access protocols

Packages

• Approve recovery request
• Reject recovery request
• Approve delete request
• Reject delete request
• Download AIP
• Download DIP

Administration

• Create new user
• Create new callback