Difference between revisions of "Testing"

From Archivematica
Jump to navigation Jump to search
Line 3: Line 3:
 
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.
 
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.
  
*[[Tests: Transfer]]
+
*See also [[Scalability testing]]
*[[Tests: Ingest]]
 
*[[Scalability testing]]
 
  
 
== Testing procedures ==
 
== Testing procedures ==

Revision as of 17:49, 1 November 2012

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.

Testing procedures

  • Process all transfers in the SampleTransfers directory
  • Process all transfers in the TestTransfers directory
  • Process transfers containing submission documentation
  • Process a transfer composed of multiple source directories
  • Process multiple transfers at once
  • Process transfers with csv metadata import
  • Edit MCP processing configuration xml file
  • Test all workflows:
    • Create/do not create transfer backup
    • Quarantine/do not quarantine
    • Remove from quarantine/leave in quarantine
    • SIP creation: manual, single SIP, single SIP and continue processing (1.0 and beyond)
    • Normalize: preservation and access; preservation only; access only; service files for access; no normalization
    • Upload DIP with and without intermediate parent level
    • Upload DIP to CONTENTdm
  • Delete files from transfer
  • Delete files from SIP
  • Add and delete rights metadata
  • Add and delete descriptive metadata
  • Remove transfers and SIPs from the dashboard
  • Add and delete source directories in administration tab
  • Test every link and breadcrumb with populated and unpopulated database

Virtual machine testing

  • All sample transfers and test transfers can be processed
  • Thunar has processing folders in left panel
  • Archivematica and AtoM can be launched from desktop
  • AtoM contains sample data
  • Check that all metadata added in AM is indexed and present in AtoM