Difference between revisions of "Testing"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
== Testing procedures == | == Testing procedures == | ||
| − | *Include SIPs with packaged files | + | *Include SIPs with and without packaged files |
| + | *Include SIPS with and without checksum.md5 files | ||
*Test deletion of files at the Review SIP, Appraise SIP and upload DIP steps | *Test deletion of files at the Review SIP, Appraise SIP and upload DIP steps | ||
*Include SIPS with files that have no normalization paths | *Include SIPS with files that have no normalization paths | ||
Revision as of 19:09, 14 December 2010
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: Review SIP
- Tests: Quarantine, scan, identify and validate
- Tests: Appraise SIP
- 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 Review SIP, Appraise SIP and upload DIP steps
- Include SIPS with files that have no normalization paths
- Ensure that the content of the log files matches expected content
- Ensure that the METS.xml file is complete