debug

.github/workflows/e2e.yml

@@ -74,15 +74,20 @@ jobs:
       - name: Run all e2e tests
         if: github.event_name == 'workflow_dispatch' || github.event_name == 'push' || steps.filter.outputs.e2e-test == 'true'
         run: python3 e2e/src/main/scripts/run_e2e_test.py --testRunner **/${{ matrix.tests }}/**/TestRunner.java
-        # Step to check if there were failures and run retry runner if needed
-      - name: Check for Failed Tests and Run Retry Runner
+      # Step to check if there were failures and list contents of target directory for debugging
+      - name: List target directory contents for debugging
+        run: ls -al ./plugin/target
+      # Step to check if there were failures and run retry runner if needed
+      - name: Check for Failed Tests and Run Retry Test Runner
         if: always()  # Always run this step to check for failures
-        run: if [ -f ./plugin/target/failed_scenarios.txt ]; then
-                   echo "Found failed scenarios. Running retry tests."
-                   python3 e2e/src/main/scripts/run_e2e_test.py --testRunner **/${{ matrix.tests }}/**/RetryTestRunner.java
-                 else
-                   echo "No failed scenarios found."
-                 fi
+        run: |
+          echo "Checking for failed_scenarios.txt"
+          if [ -f ./plugin/target/failed_scenarios.txt ]; then
+            echo "Found failed scenarios. Running retry tests."
+            python3 e2e/src/main/scripts/run_e2e_test.py --testRunner **/${{ matrix.tests }}/**/RetryTestRunner.java
+          else
+            echo "No failed scenarios found."
+          fi
       - name: Upload debug files 
         uses: actions/upload-artifact@v3
         if: always()

src/e2e-test/features/bigquery/sink/GCSToBigQuery.feature

@@ -57,7 +57,7 @@ Feature: BigQuery sink - Verification of GCS to BigQuery successful data transfe
     Then Enter BigQuery property reference name
     Then Enter BigQuery property projectId "projectId"
     Then Enter BigQuery property datasetProjectId "projectId"
-    Then Override Service account details if set in environment variables
+    Then Override Service account details if set in environment variablesss
     Then Enter BigQuery property dataset "dataset"
     Then Enter BigQuery sink property table name
     Then Toggle BigQuery sink property truncateTable to true

src/e2e-test/features/bigquery/sink/GCSToBigQuery_WithMacro.feature

@@ -6,7 +6,7 @@ Feature: BigQuery sink - Verification of GCS to BigQuery successful data transfe
     Given Open Datafusion Project to configure pipeline
     When Source is GCS
     When Sink is BigQuery
-    Then Open GCS source properties
+    Then Open GCS source propertiess
     Then Enter GCS property reference name
     Then Enter GCS property "projectId" as macro argument "gcsProjectId"
     Then Enter GCS property "serviceAccountType" as macro argument "serviceAccountType"

src/e2e-test/features/bigquery/source/BigQuerySourceError.feature

@@ -3,7 +3,7 @@ Feature: BigQuery source - Validate BigQuery source plugin error scenarios
 
   Scenario Outline:Verify BigQuery Source properties validation errors for mandatory fields
     Given Open Datafusion Project to configure pipeline
-    When Source is BigQuery
+    When Source is BigQuerys
     Then Open BigQuery source properties
     Then Enter the BigQuery properties with blank property "<property>"
     Then Validate mandatory property error for "<property>"
@@ -29,7 +29,7 @@ Feature: BigQuery source - Validate BigQuery source plugin error scenarios
 
   Scenario Outline:Verify BigQuery Source properties validation errors for incorrect format of projectIds
     Given Open Datafusion Project to configure pipeline
-    When Source is BigQuery
+    When Source is BigQuerys
     Then Open BigQuery source properties
     Then Enter BigQuery property reference name
     Then Enter BigQuery property projectId "<ProjectID>"

src/e2e-test/features/bigqueryexecute/BQExecute.feature

@@ -1,4 +1,4 @@
-@BQExecute
+@BQExecutes
 Feature: BigQueryExecute - Verify data transfer using BigQuery Execute plugin
 
   @BQ_SOURCE_TEST @BQ_SINK_TEST @BQ_EXECUTE_SQL @BQExecute_Required

src/e2e-test/features/bigqueryexecute/BQExecuteErrorScenarios.feature

@@ -1,4 +1,4 @@
-@BQExecute
+@BQExecutes
 Feature: BigQueryExecute - Verify BigQueryExecute plugin error scenarios
 
   Scenario: Verify BigQueryExecute validation error for mandatory field SQL Query

src/e2e-test/features/bigqueryexecute/BQExecute_WithMacro.feature

@@ -1,4 +1,4 @@
-@BQExecute
+@BQExecutes
 Feature: BigQueryExecute - Verify data transfer using BigQuery Execute plugin with macro arguments
 
   @BQ_SOURCE_TEST @BQ_SINK_TEST @BQ_EXECUTE_SQL

src/e2e-test/features/bigtable/BigTableToBigTable.feature

@@ -11,7 +11,7 @@
 # WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
 # License for the specific language governing permissions and limitations under
 # the License.
-@BigTable @BIGTABLE_SOURCE_TEST
+@BigTables @BIGTABLE_SOURCE_TEST
 Feature: BigTable source - Verification of BigTable to BigTable Successful Data Transfer
 
   @BIGTABLE_SINK_TEST @bigtable_Required

src/e2e-test/features/datastore/runtime.feature

@@ -12,7 +12,7 @@
 # License for the specific language governing permissions and limitations under
 # the License.
 
-@DataStore
+@DataStores
 Feature: DataStore - Verification of Datastore to Datastore Successful Data Transfer
 
   @DATASTORE_SOURCE_ENTITY @datastore_Required

src/e2e-test/features/gcs/sink/GCSSink.feature

@@ -1,4 +1,4 @@
-@GCS_Sink
+@GCS_Sinks
 Feature: GCS sink - Verification of GCS Sink plugin
 
   @CMEK @GCS_SINK_TEST @BQ_SOURCE_TEST

src/e2e-test/features/gcs/sink/GCSSinkError.feature

@@ -1,4 +1,4 @@
-@GCS_Sink
+@GCS_Sinks
 Feature: GCS sink - Verify GCS Sink plugin error scenarios
 
   Scenario Outline:Verify GCS Sink properties validation errors for mandatory fields

src/e2e-test/features/gcs/source/GCSSourceError.feature

@@ -1,4 +1,4 @@
-@GCS_Source
+@GCS_Sources
 Feature: GCS source - Verify GCS Source plugin error scenarios
 
   Scenario Outline:Verify GCS Source properties validation errors for mandatory fields

src/e2e-test/features/gcs/source/GCSSourceToBigQuery.feature

@@ -1,4 +1,4 @@
-@GCS_Source
+@GCS_Sources
 Feature: GCS source - Verification of GCS to BQ successful data transfer
 
   @GCS_CSV_TEST @BQ_SINK_TEST

src/e2e-test/features/gcs/source/GCSSourceToBigQueryAdditionalTests.feature

@@ -1,4 +1,4 @@
-@GCS_Source
+@GCS_Sources
 Feature: GCS source - Verification of GCS to BQ successful data transfer
 
   @BQ_SINK_TEST @GCS_READ_RECURSIVE_TEST

src/e2e-test/features/gcs/source/GCSToGCSAdditonalTests.feature

@@ -1,4 +1,4 @@
-@GCS_Source
+@GCS_Sources
 Feature: GCS source - Verification of GCS to GCS Additional Tests successful
 
   @GCS_AVRO_FILE @GCS_SINK_TEST @GCS_Source_Required @ITN_TEST

src/e2e-test/features/gcs/source/GCSToGCS_withConnections.feature

@@ -1,4 +1,4 @@
-@GCS_Source
+@GCS_Sources
 Feature: GCS source - Verification of GCS to GCS successful data transfer using connections
 
   @GCS_CSV_TEST @GCS_SINK_TEST @GCS_CONNECTION

src/e2e-test/features/gcs/source/GCSourceSchema.feature

@@ -1,4 +1,4 @@
-@GCS_Source
+@GCS_Sources
 Feature: GCS source - Validate GCS plugin output schema for different formats
 
   Scenario Outline:GCS Source output schema validation for csv and tsv format
@@ -7,7 +7,7 @@ Feature: GCS source - Validate GCS plugin output schema for different formats
     Then Open GCS source properties
     Then Enter GCS property projectId and reference name
     Then Override Service account details if set in environment variables
-    Then Enter GCS source property path "<GcsPath>"
+    Then Enter GCS source property path "<GcsPath>"s
     Then Select GCS property format "<FileFormat>"
     Then Toggle GCS source property skip header to true
     Then Validate output schema with expectedSchema "<ExpectedSchema>"
@@ -28,7 +28,7 @@ Feature: GCS source - Validate GCS plugin output schema for different formats
     Then Enter GCS property projectId and reference name
     Then Override Service account details if set in environment variables
     Then Enter GCS source property path "<GcsPath>"
-    Then Select GCS property format "<FileFormat>"
+    Then Select GCS property format "<FileFormat>"s
     Then Validate output schema with expectedSchema "<ExpectedSchema>"
     @GCS_BLOB_TEST
     Examples:
@@ -52,7 +52,7 @@ Feature: GCS source - Validate GCS plugin output schema for different formats
     Given Open Datafusion Project to configure pipeline
     When Source is GCS
     Then Open GCS source properties
-    Then Enter GCS property projectId and reference name
+    Then Enter GCS property projectId and reference names
     Then Override Service account details if set in environment variables
     Then Enter GCS source property path "<GcsPath>"
     Then Select GCS property format "<FileFormat>"
@@ -70,7 +70,7 @@ Feature: GCS source - Validate GCS plugin output schema for different formats
     Given Open Datafusion Project to configure pipeline
     When Source is GCS
     Then Open GCS source properties
-    Then Enter GCS property projectId and reference name
+    Then Enter GCS property projectId and reference names
     Then Override Service account details if set in environment variables
     Then Enter GCS source property path "gcsDelimitedFile"
     Then Select GCS property format "delimited"
@@ -82,7 +82,7 @@ Feature: GCS source - Validate GCS plugin output schema for different formats
     Given Open Datafusion Project to configure pipeline
     When Source is GCS
     Then Open GCS source properties
-    Then Enter GCS property projectId and reference name
+    Then Enter GCS property projectId and reference names
     Then Enter GCS source property path "<GcsPath>"
     Then Select GCS property format "<FileFormat>"
     Then Toggle GCS source property skip header to true

src/e2e-test/features/gcscopy/GCSCopy.feature

@@ -12,7 +12,7 @@
 # License for the specific language governing permissions and limitations under
 # the License.
 
-@GCSCopy
+@GCSCopys
 Feature:GCSCopy - Verification of successful objects copy from one bucket to another
 
   @CMEK @GCS_CSV_TEST @GCS_SINK_TEST @GCSCopy_Required @ITN_TEST
@@ -22,7 +22,7 @@ Feature:GCSCopy - Verification of successful objects copy from one bucket to ano
     When Select plugin: "GCS Copy" from the plugins list as: "Conditions and Actions"
     When Navigate to the properties page of plugin: "GCS Copy"
     And Replace input plugin property: "project" with value: "projectId"
-    And Enter GCSCopy property source path "gcsCsvFile"
+    And Enter GCSCopy property source path "gcsCsvFile"s
     And Enter GCSCopy property destination path
     Then Override Service account details if set in environment variables
     Then Enter GCSCopy property encryption key name "cmekGCS" if cmek is enabled

src/e2e-test/features/gcscopy/GCSCopyErrorScenarios.feature

@@ -21,7 +21,7 @@ Feature: GCSCopy - Validate GCSCopy plugin error scenarios
     When Expand Plugin group in the LHS plugins list: "Conditions and Actions"
     When Select plugin: "GCS Copy" from the plugins list as: "Conditions and Actions"
     When Navigate to the properties page of plugin: "GCS Copy"
-    Then Click on the Validate button
+    Then Click on the Validate buttons
     Then Verify mandatory property error for below listed properties:
       | sourcePath |
       | destPath   |

src/e2e-test/features/gcscopy/GCSCopy_WithMacro.feature

@@ -17,7 +17,7 @@ Feature:GCSCopy - Verification of successful objects copy from one bucket to ano
 
   @CMEK @GCS_CSV_TEST @GCS_SINK_TEST @GCSCopy_Required @ITN_TEST
   Scenario:Validate successful copy object from one bucket to another new bucket with macro arguments
-    Given Open Datafusion Project to configure pipeline
+    Given Open Datafusion Project to configure pipelines
     When Expand Plugin group in the LHS plugins list: "Conditions and Actions"
     When Select plugin: "GCS Copy" from the plugins list as: "Conditions and Actions"
     When Navigate to the properties page of plugin: "GCS Copy"

src/e2e-test/features/gcscreate/GCSCreate.feature

@@ -15,7 +15,7 @@ Feature: GCSCreate - Verification of GCS Create plugin
     Then Enter GCSCreate property encryption key name "cmekGCS" if cmek is enabled
     Then Validate "GCS Create" plugin properties
     Then Close the GCS Create properties
-    Then Save and Deploy Pipeline
+    Then Save and Deploy Pipelines
     Then Run the Pipeline in Runtime
     Then Wait till pipeline is in running state
     Then Open and capture logs
@@ -34,7 +34,7 @@ Feature: GCSCreate - Verification of GCS Create plugin
     Then Select GCS Create property fail if objects exists as "true"
     Then Override Service account details if set in environment variables
     Then Validate "GCS Create" plugin properties
-    Then Close the GCS Create properties
+    Then Close the GCS Create propertiess
     Then Save and Deploy Pipeline
     Then Run the Pipeline in Runtime
     Then Wait till pipeline is in running state
@@ -55,7 +55,7 @@ Feature: GCSCreate - Verification of GCS Create plugin
     Then Override Service account details if set in environment variables
     Then Validate "GCS Create" plugin properties
     Then Close the GCS Create properties
-    Then Save and Deploy Pipeline
+    Then Save and Deploy Pipelines
     Then Run the Pipeline in Runtime
     Then Wait till pipeline is in running state
     Then Verify the pipeline status is "Succeeded"

src/e2e-test/features/gcscreate/GCSCreate_WithMacro.feature

@@ -17,7 +17,7 @@ Feature: GCSCreate - Verification of GCS Create plugin with macro arguments
     Then Validate "GCS Create" plugin properties
     Then Close the GCS Create properties
     Then Save and Deploy Pipeline
-    Then Run the Pipeline in Runtime
+    Then Run the Pipeline in Runtimes
     Then Enter runtime argument value "projectId" for key "gcsCreateProjectId"
     Then Enter runtime argument value "gcsCreateObject1" for GCSCreate property key "gcsCreateObjectsToCreate"
     Then Enter runtime argument value "true" for GCSCreate property key "gcsCreateFailIfObjectExists"

src/e2e-test/features/gcsdelete/GCSDelete.feature

@@ -13,7 +13,7 @@ Feature: GCS Delete - Verification of GCS Delete plugin
     Then Validate "GCS Delete" plugin properties
     Then Close the GCS Delete properties
     Then Save and Deploy Pipeline
-    Then Run the Pipeline in Runtime
+    Then Run the Pipeline in Runtimes
     Then Wait till pipeline is in running state
     Then Open and capture logs
     Then Verify the pipeline status is "Succeeded"
@@ -26,7 +26,7 @@ Feature: GCS Delete - Verification of GCS Delete plugin
     When Select plugin: "GCS Delete" from the plugins list as: "Conditions and Actions"
     When Navigate to the properties page of plugin: "GCS Delete"
     Then Enter the GCS Delete property projectId "projectId"
-    Then Enter the GCS Delete property objects to delete as path "gcsCsvFile"
+    Then Enter the GCS Delete property objects to delete ass path "gcsCsvFile"
     Then Override Service account details if set in environment variables
     Then Validate "GCS Delete" plugin properties
     Then Close the GCS Delete properties
@@ -45,7 +45,7 @@ Feature: GCS Delete - Verification of GCS Delete plugin
     When Navigate to the properties page of plugin: "GCS Delete"
     Then Enter the GCS Delete property projectId "projectId"
     Then Enter the GCS Delete property objects to delete as list of objects "gcsDeleteObjectsList"
-    Then Override Service account details if set in environment variables
+    Then Override Service account details isf set in environment variables
     Then Validate "GCS Delete" plugin properties
     Then Close the GCS Delete properties
     Then Save and Deploy Pipeline
@@ -61,7 +61,7 @@ Feature: GCS Delete - Verification of GCS Delete plugin
     When Expand Plugin group in the LHS plugins list: "Conditions and Actions"
     When Select plugin: "GCS Delete" from the plugins list as: "Conditions and Actions"
     When Navigate to the properties page of plugin: "GCS Delete"
-    Then Enter the GCS Delete property projectId "projectId"
+    Then Enter the GCS Delete property projectId s"projectId"
     Then Enter the GCS Delete property objects to delete as path "gcsWildcardPath1"
     Then Override Service account details if set in environment variables
     Then Validate "GCS Delete" plugin properties
@@ -81,7 +81,7 @@ Feature: GCS Delete - Verification of GCS Delete plugin
     When Select plugin: "GCS Delete" from the plugins list as: "Conditions and Actions"
     When Navigate to the properties page of plugin: "GCS Delete"
     Then Enter the GCS Delete property projectId "projectId"
-    Then Enter the GCS Delete property objects to delete as path "gcsWildcardPath2"
+    Then Enter the GCS Delete property objectss to delete as path "gcsWildcardPath2"
     Then Override Service account details if set in environment variables
     Then Validate "GCS Delete" plugin properties
     Then Close the GCS Delete properties
@@ -98,7 +98,7 @@ Feature: GCS Delete - Verification of GCS Delete plugin
     Given Open Datafusion Project to configure pipeline
     When Expand Plugin group in the LHS plugins list: "Conditions and Actions"
     When Select plugin: "GCS Delete" from the plugins list as: "Conditions and Actions"
-    When Navigate to the properties page of plugin: "GCS Delete"
+    When Navigate to the properties pagse of plugin: "GCS Delete"
     Then Enter the GCS Delete property projectId "projectId"
     Then Enter the GCS Delete property objects to delete as path "gcsWildcardPath3"
     Then Override Service account details if set in environment variables
@@ -116,7 +116,7 @@ Feature: GCS Delete - Verification of GCS Delete plugin
   Scenario: Verify the GCS Delete successfully deletes file from multiple buckets
     Given Open Datafusion Project to configure pipeline
     When Expand Plugin group in the LHS plugins list: "Conditions and Actions"
-    When Select plugin: "GCS Delete" from the plugins list as: "Conditions and Actions"
+    When Select plugin: "GCS Delete" from sthe plugins list as: "Conditions and Actions"
     When Navigate to the properties page of plugin: "GCS Delete"
     Then Enter the GCS Delete property projectId "projectId"
     Then Enter the GCS Delete property objects from multiple Buckets to delete as list of objects "gcsMultiBucketsPath1"
@@ -133,10 +133,10 @@ Feature: GCS Delete - Verification of GCS Delete plugin
 
   @GCS_DELETE_MULTIPLE_BUCKETS_TEST
   Scenario: Verify the GCS Delete successfully deletes file from multiple buckets use wildcard
-    Given Open Datafusion Project to configure pipeline
+    Given Open Datafusion Project to consfigure pipeline
     When Expand Plugin group in the LHS plugins list: "Conditions and Actions"
     When Select plugin: "GCS Delete" from the plugins list as: "Conditions and Actions"
-    When Navigate to the properties page of plugin: "GCS Delete"
+    When Navigate to the propertises page of plugin: "GCS Delete"
     Then Enter the GCS Delete property projectId "projectId"
     Then Enter the GCS Delete property objects from multiple Buckets to delete as list of objects "gcsWildcardMultiBucketsPath1"
     Then Override Service account details if set in environment variables
@@ -154,14 +154,14 @@ Feature: GCS Delete - Verification of GCS Delete plugin
     Given Open Datafusion Project to configure pipeline
     When Expand Plugin group in the LHS plugins list: "Conditions and Actions"
     When Select plugin: "GCS Delete" from the plugins list as: "Conditions and Actions"
-    When Navigate to the properties page of plugin: "GCS Delete"
+    When Navigate to the properties pagse of plugin: "GCS Delete"
     Then Validate mandatory property error for "paths"
 
   Scenario:Verify GCS Delete properties validation error for incorrect bucket path
     Given Open Datafusion Project to configure pipeline
     When Expand Plugin group in the LHS plugins list: "Conditions and Actions"
     When Select plugin: "GCS Delete" from the plugins list as: "Conditions and Actions"
     When Navigate to the properties page of plugin: "GCS Delete"
-    Then Enter the GCS Delete property objects to delete as path "gcsInvalidBucketName"
+    Then Enter the GCS Delete property objectss to delete as path "gcsInvalidBucketName"
     Then Override Service account details if set in environment variables
     Then Verify invalid bucket name error message is displayed for GCS Delete objects to delete path "gcsInvalidBucketName"