Difference between revisions of "Testing"
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: | + | *[[Tests: Transfer]] |
| − | *[[Tests: | + | *[[Tests: Ingest]] |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
*[[Scalability testing]] | *[[Scalability testing]] | ||
Revision as of 11:01, 4 January 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
- 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
- Normalize: preservation and access; preservation only; access only; no normalization
- 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