Difference between revisions of "Testing"

From Archivematica
Jump to navigation Jump to search
Line 15: Line 15:
  
 
*Include SIPs with and without packaged files
 
*Include SIPs with and without packaged files
*Include SIPS with and without checksum.md5 files
+
*Include SIPS with and without checksum.md5, sha-1 and sha-256 files
 
*Test deletion of files at the following steps: Appraise SIP for submission, Appraise SIP for preservation and upload DIP
 
*Test deletion of files at the following steps: Appraise SIP for submission, Appraise SIP for preservation and upload DIP
 
*Include SIPS with files that have no normalization paths
 
*Include SIPS with files that have no normalization paths

Revision as of 13:51, 10 June 2011

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

  • Include SIPs with and without packaged files
  • Include SIPS with and without checksum.md5, sha-1 and sha-256 files
  • Test deletion of files at the following steps: Appraise SIP for submission, Appraise SIP for preservation and upload DIP
  • Include SIPS with files that have no normalization paths
  • Include SIPs with files that have no file extensions
  • Test manual normalization
  • Test submission documentation with and without files requiring normalization
  • Test submission documentation with no files in submissionDocumentation folder
  • Ensure that the content of the log files matches expected content
  • Ensure that the METS.xml file is complete
  • Run several SIPs through at once