Difference between revisions of "Testing"
Jump to navigation
Jump to search
| Line 21: | Line 21: | ||
*Ensure that the content of the log files matches expected content | *Ensure that the content of the log files matches expected content | ||
*Ensure that the METS.xml file is complete | *Ensure that the METS.xml file is complete | ||
| + | *Run several SIPs through at once | ||
Revision as of 19:36, 8 February 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.
- Tests: Receive SIP
- Tests: Appraise SIP for submission
- Tests: Quarantine, scan, identify and validate
- Tests: Appraise SIP for preservation
- Tests: Normalize
- Tests: Generate access copies
- Tests: Approve and store AIP
- Tests: Upload DIP
Testing procedures
- Include SIPs with and without packaged files
- Include SIPS with and without checksum.md5 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
- 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