Difference between revisions of "Testing"

From Archivematica
Jump to navigation Jump to search
(Accession numbers)
Line 89: Line 89:
*Create new Locations
*Create new Locations
**AIP recovery; AIP storage; Currently processing; DIP storage; Storage Service internal processing; Transfer backlog; Transfer source
**AIP recovery; AIP storage; Currently processing; DIP storage; Transfer backlog; Transfer source
**Test different access protocols
**Test different access protocols

Revision as of 11:08, 29 June 2015

Main Page > Development > Development documentation > Testing

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.4.

Archivematica testing procedures


  • 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


  • 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
    • Store DIP
    • Upload DIP to CONTENTdm
    • 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

Preservation Planning

  • Update FPR


  • Check links to AtoM


  • Test processing pre-configurations
  • Hide AtoM DIP upload link
  • Hide DSpace transfer type
  • Check transfer source locations
  • Check AIP storage locations
  • Clear Processing storage locations
  • Change PREMIS agent
  • Add new users

Storage Service testing procedures


  • Create new pipeline


  • Create new Space
    • Test different access protocols


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


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


  • Create new user
  • Create new callback