Point black-box tests at new Sampledata folder

artefactual-labs · Dec 23, 2019 · 3dcd090 · 3dcd090
1 parent dadb7f8
commit 3dcd090
Show file tree

Hide file tree

Showing 6 changed files with 14 additions and 14 deletions.
diff --git a/features/black_box/checksum.feature b/features/black_box/checksum.feature
@@ -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
diff --git a/features/black_box/create-aip.feature b/features/black_box/create-aip.feature
@@ -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
@@ -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

diff --git a/features/black_box/extract-package.feature b/features/black_box/extract-package.feature
@@ -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
@@ -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
diff --git a/features/black_box/reingest-aip.feature b/features/black_box/reingest-aip.feature
@@ -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

diff --git a/features/black_box/transfer-microservices.feature b/features/black_box/transfer-microservices.feature
@@ -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                       |
diff --git a/features/black_box/virus.feature b/features/black_box/virus.feature
@@ -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