test: reenabled tests removed in error

Author: stevenhsd

tests/features/planets.feature

@@ -8,33 +8,33 @@ Feature: Pipeline tests using the planets dataset
     Some validation of entity attributes is performed: SQL expressions and Python filter
     functions are used, and templatable business rules feature in the transformations.
 
-    # Scenario: Validate and filter planets (spark)
-    #     Given I submit the planets file planets_demo.csv for processing
-    #     And A spark pipeline is configured
-    #     And I add initial audit entries for the submission
-    #     Then the latest audit record for the submission is marked with processing status file_transformation
-    #     When I run the file transformation phase
-    #     Then the planets entity is stored as a parquet after the file_transformation phase
-    #     And the latest audit record for the submission is marked with processing status data_contract
-    #     When I run the data contract phase
-    #     Then there is 1 record rejection from the data_contract phase
-    #     And the planets entity is stored as a parquet after the data_contract phase
-    #     And the latest audit record for the submission is marked with processing status business_rules
-    #     When I run the business rules phase
-    #     Then The rules restrict "planets" to 1 qualifying record
-    #     And At least one row from "planets" has generated error code "HIGH_DENSITY"
-    #     And At least one row from "planets" has generated error code "WEAK_ESCAPE"
-    #     And the planets entity is stored as a parquet after the business_rules phase
-    #     And the latest audit record for the submission is marked with processing status error_report
-    #     When I run the error report phase
-    #     Then An error report is produced
-    #     And The entity "planets" does not contain an entry for "Jupiter" in column "planet"
-    #     And The entity "planets" contains an entry for "Neptune" in column "planet"
-    #     And The statistics entry for the submission shows the following information
-    #         | parameter                | value |
-    #         | record_count             | 9     |
-    #         | number_record_rejections | 18    |
-    #         | number_warnings          | 0     |
+    Scenario: Validate and filter planets (spark)
+        Given I submit the planets file planets_demo.csv for processing
+        And A spark pipeline is configured
+        And I add initial audit entries for the submission
+        Then the latest audit record for the submission is marked with processing status file_transformation
+        When I run the file transformation phase
+        Then the planets entity is stored as a parquet after the file_transformation phase
+        And the latest audit record for the submission is marked with processing status data_contract
+        When I run the data contract phase
+        Then there is 1 record rejection from the data_contract phase
+        And the planets entity is stored as a parquet after the data_contract phase
+        And the latest audit record for the submission is marked with processing status business_rules
+        When I run the business rules phase
+        Then The rules restrict "planets" to 1 qualifying record
+        And At least one row from "planets" has generated error code "HIGH_DENSITY"
+        And At least one row from "planets" has generated error code "WEAK_ESCAPE"
+        And the planets entity is stored as a parquet after the business_rules phase
+        And the latest audit record for the submission is marked with processing status error_report
+        When I run the error report phase
+        Then An error report is produced
+        And The entity "planets" does not contain an entry for "Jupiter" in column "planet"
+        And The entity "planets" contains an entry for "Neptune" in column "planet"
+        And The statistics entry for the submission shows the following information
+            | parameter                | value |
+            | record_count             | 9     |
+            | number_record_rejections | 18    |
+            | number_warnings          | 0     |
 
     Scenario: Handle a file with no extension provided (spark)
         Given I submit the planets file planets_no_extension for processing