Skip to content

WIP: Point black-box and old-school AMAUAT tests at new sample data folder #153

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 2 commits into
base: qa/1.x
Choose a base branch
from
Draft

WIP: Point black-box and old-school AMAUAT tests at new sample data folder #153

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3dcd090
Point black-box tests at new Sampledata folder
ross-spencer Dec 23, 2019
4840c02
wip: old-style amauat changes
ross-spencer Dec 23, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions features/black_box/checksum.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,12 @@
Feature: Alma wants to verify checksums transmitted with a transfer to ensure that the transfer contents haven't been corrupted.

Scenario: External metadata checksums are verified
Given a "standard" transfer type located in "SampleTransfers/DemoTransferCSV"
Given a "standard" transfer type located in "amauat-automated-acceptance-tests/standard-transfer/DemoTransferCSV"
When the transfer compliance is verified
Then the "Verify metadata directory checksums" job completes successfully

Scenario: External metadata checksums are not verified
Given a "standard" transfer type located in "TestTransfers/fixityCheckShouldFail"
Given a "standard" transfer type located in "amauat-automated-acceptance-tests/standard-transfer/fixityCheckShouldFail"
When the transfer compliance is verified
Then the "Verify metadata directory checksums" job fails
And the "Failed transfer" microservice is executed
6 changes: 3 additions & 3 deletions features/black_box/create-aip.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Alma wants to be able to create AIPs from all of Archivematica's different trans
Background: The storage service is configured with a transfer source that can see the archivematica-sampledata repository.

Scenario: Generate an AIP using a standard transfer workflow
Given a "standard" transfer type located in "SampleTransfers/DemoTransferCSV"
Given a "standard" transfer type located in "amauat-automated-acceptance-tests/standard-transfer/DemoTransferCSV"
When the AIP is downloaded
Then the AIP METS can be accessed and parsed by mets-reader-writer
And the AIP conforms to expected content and structure
Expand All @@ -20,13 +20,13 @@ Background: The storage service is configured with a transfer source that can se
And every PREMIS event recorded in the AIP METS records the logged-in user, the organization and the software as PREMIS agents

Scenario: Generate an AIP using an unzipped bag transfer workflow
Given a "unzipped bag" transfer type located in "SampleTransfers/BagTransfer"
Given a "unzipped bag" transfer type located in "amauat-automated-acceptance-tests/bagit/BagTransfer"
When the transfer is approved
Then the "Verify bag, and restructure for compliance" job completes successfully
And there is a sourceMD containing a BagIt mdWrap in the AIP METS

Scenario: Generate an AIP using a Dataverse workflow
Given a "dataverse" transfer type located in "SampleTransfers/Dataverse/NDSAStaffingReport"
Given a "dataverse" transfer type located in "amauat-automated-acceptance-tests/Dataverse/NDSAStaffingReport"
When the AIP is downloaded
Then the "Set convert Dataverse structure flag" job completes successfully
And the "Set parse Dataverse METS flag" job completes successfully
Expand Down
4 changes: 2 additions & 2 deletions features/black_box/extract-package.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
Feature: Alma wants package files included in the transfer to be extracted.

Scenario: packages are extracted successfully
Given a "standard" transfer type located in "SampleTransfers/OfficeDocs"
Given a "standard" transfer type located in "amauat-automated-acceptance-tests/standard-transfer/OfficeDocs"
When the transfer compliance is verified
Then the "Extract contents from compressed archives" job completes successfully
And the "Sanitize extracted objects' file and directory names" job completes successfully
Expand All @@ -12,7 +12,7 @@ Feature: Alma wants package files included in the transfer to be extracted.
And the "Determine if transfer still contains packages" job completes successfully

Scenario: packages are not extracted successfully
Given a "standard" transfer type located in "TestTransfers/broken_package_format_types"
Given a "standard" transfer type located in "amauat-automated-acceptance-tests/standard-transfer/broken_package_format_types"
When the transfer compliance is verified
Then the "Extract contents from compressed archives" job fails
And the "Failed transfer" microservice is executed
4 changes: 2 additions & 2 deletions features/black_box/reingest-aip.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,15 +2,15 @@
Feature: Alma wants to be able to re-ingest an AIP and have the reingest recorded accurately in the AIP METS file.

Scenario: Reingest without error
Given a "standard" transfer type located in "SampleTransfers/DemoTransferCSV" has been reingested
Given a "standard" transfer type located in "amauat-automated-acceptance-tests/standard-transfer/DemoTransferCSV" has been reingested
When the reingest has been processed
Then the AIP can be successfully stored
And there is a reingestion event for each original object in the AIP METS
And there is a fileSec for deleted files for objects that were re-normalized
And there is a current and a superseded techMD for each original object

Scenario: Reingest unzipped bag transfer
Given a "unzipped bag" transfer type located in "SampleTransfers/UnzippedBag" has been reingested
Given a "unzipped bag" transfer type located in "amauat-automated-acceptance-tests/bagit/UnzippedBag" has been reingested
When the reingest has been processed
Then the AIP can be successfully stored
And there is a reingestion event for each original object in the AIP METS
Expand Down
6 changes: 3 additions & 3 deletions features/black_box/transfer-microservices.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,6 @@ Feature: Alma wants to ensure that PREMIS events are recorded for all preservati
And there are <validated_objects_count> original objects in the AIP METS with a validation event

Examples: sample transfers
| sample_transfer_path | validated_objects_count |
| SampleTransfers/DemoTransferCSV | 2 |
| TestTransfers/badNames | 0 |
| sample_transfer_path | validated_objects_count |
| amauat-automated-acceptance-tests/standard-transfer/DemoTransferCSV | 2 |
| amauat-automated-acceptance-tests/standard-transfer/badNames | 0 |
4 changes: 2 additions & 2 deletions features/black_box/virus.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,12 +2,12 @@
Feature: Alma wants to ensure that virus scanning in Archivematica works correctly to ensure transfers pass when they have no viruses, and transfers fail when they contain viruses.

Scenario: Virus checks for a transfer pass
Given a "standard" transfer type located in "SampleTransfers/DemoTransferCSV"
Given a "standard" transfer type located in "amauat-automated-acceptance-tests/standard-transfer/DemoTransferCSV"
When the transfer compliance is verified
Then the "Scan for viruses" job completes successfully

Scenario: Virus checks for a transfer fail
Given a "standard" transfer type located in "TestTransfers/virusTests"
Given a "standard" transfer type located in "amauat-automated-acceptance-tests/standard-transfer/virusTests"
When the transfer compliance is verified
Then the "Scan for viruses" job fails
And the "Failed transfer" microservice is executed
2 changes: 1 addition & 1 deletion features/core/aip-encryption-mirror.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ Feature: AIP Encryption via Mirror Locations
And there is a standard GPG-encrypted Replicator location in the storage service
And the default AIP Storage location has the GPG-encrypted Replicator location as its replicator
And automated processing with all decision points resolved
When a transfer is initiated on directory SampleTransfers/BagTransfer
When a transfer is initiated on directory amauat-automated-acceptance-tests/bagit/BagTransfer
And the user waits for the AIP to appear in archival storage
And the user searches for the AIP UUID in the Storage Service
Then the master AIP and its replica are returned by the search
Expand Down
8 changes: 4 additions & 4 deletions features/core/aip-encryption.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,7 +31,7 @@ Feature: AIP Encryption
And there is a standard GPG-encrypted AIP Storage location in the storage service
And automated processing with all decision points resolved
And automated processing configured to Store AIP Encrypted in standard Archivematica Directory
When a transfer is initiated on directory SampleTransfers/BagTransfer
When a transfer is initiated on directory amauat-automated-acceptance-tests/bagit/BagTransfer
And the user waits for the AIP to appear in archival storage
And the user downloads the AIP pointer file
Then the pointer file contains a PREMIS:EVENT element for the encryption event
Expand All @@ -47,7 +47,7 @@ Feature: AIP Encryption
And automated processing with all decision points resolved
And the processing config decision "Select compression algorithm" is set to "Uncompressed"
And automated processing configured to Store AIP Encrypted in standard Archivematica Directory
When a transfer is initiated on directory SampleTransfers/BagTransfer
When a transfer is initiated on directory amauat-automated-acceptance-tests/bagit/BagTransfer
And the user waits for the AIP to appear in archival storage
And the user queries the API until the AIP has been stored
Then the uncompressed AIP on disk at /var/archivematica/sharedDirectory/www/AIPsStoreEncrypted/ is encrypted
Expand All @@ -61,7 +61,7 @@ Feature: AIP Encryption
And there is a standard GPG-encrypted Transfer Backlog location in the storage service
And automated processing with all decision points resolved
And the processing config decision "Create SIP(s)" is set to "Send to backlog"
When a transfer is initiated on directory SampleTransfers/BagTransfer
When a transfer is initiated on directory amauat-automated-acceptance-tests/bagit/BagTransfer
And the user waits for the SIP to appear in transfer backlog
Then the transfer on disk is encrypted
# TODO: implement the following steps. Spending time implementing these did
Expand All @@ -87,7 +87,7 @@ Feature: AIP Encryption
And automated processing with all decision points resolved
And automated processing configured to Store AIP Encrypted in standard Archivematica Directory
When the user creates a new GPG key and assigns it to the standard GPG-encrypted space
And an encrypted AIP is created from the directory at SampleTransfers/BagTransfer
And an encrypted AIP is created from the directory at amauat-automated-acceptance-tests/bagit/BagTransfer
And the user attempts to delete the new GPG key
Then the user is prevented from deleting the key because it is attached to a space
When the user assigns a different GPG key to the standard GPG-encrypted space
Expand Down
8 changes: 4 additions & 4 deletions features/core/ingest-mkv-conformance.feature
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,9 @@ Feature: Ingest (i.e., post-normalization) conformance check
Then all PREMIS implementation-check-type validation events have eventOutcome = <event_outcome>

Examples: Normalized for Preservation File Validity Possibilities
| file_validity | microservice_output | validation_result | event_outcome | transfer_path |
| valid | Completed successfully | Passed | pass | TestTransfers/acceptance-tests/preforma/when-normalized-all-valid |
#| not valid | Failed | Failed | fail | TestTransfers/acceptance-tests/preforma/when-normalized-none-valid |
| file_validity | microservice_output | validation_result | event_outcome | transfer_path |
| valid | Completed successfully | Passed | pass | amauat-automated-acceptance-tests/standard-transfer/preforma/when-normalized-all-valid |
| not valid | Failed | Failed | fail | amauat-automated-acceptance-tests/standard-transfer/preforma/when-normalized-none-valid |

@access
Scenario Outline: Isla wants to confirm that normalization to .mkv for access is successful
Expand All @@ -40,4 +40,4 @@ Feature: Ingest (i.e., post-normalization) conformance check

Examples: Normalized for Access File Validity Possibilities
| file_validity | microservice_output | validation_result | event_outcome | transfer_path |
| valid | Completed successfully | Passed | pass | TestTransfers/acceptance-tests/preforma/when-normalized-access-all-valid |
| valid | Completed successfully | Passed | pass | amauat-automated-acceptance-tests/standard-transfer/preforma/when-normalized-access-all-valid |
Loading