debug

Author: AnkitCLI

.github/workflows/e2e.yml

@@ -40,7 +40,7 @@ jobs:
           )
     strategy:
       matrix:
-        tests: [bigquery, common, gcs, pubsub, spanner, gcscreate, gcsdelete, gcsmove, bigqueryexecute, gcscopy, datastore, bigtable]
+        tests: [bigquery, common, gcs, pubsub, spanner, gcscreate, gcsdelete, gcsmove, bigqueryexecute, gcscopy, bigtable, datastore]
       fail-fast: false
     steps:
       # Pinned 1.0.0 version

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

@@ -3,7 +3,7 @@ Feature: BigQueryExecute - Verify data transfer using BigQuery Execute plugin
 
   @BQ_SOURCE_TEST @BQ_SINK_TEST @BQ_EXECUTE_SQL @BQExecute_Required
   Scenario: Verify Store results in a BigQuery Table functionality of BQExecute plugin
-    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: "BigQuery Execute" from the plugins list as: "Conditions and Actions"
     When Navigate to the properties page of plugin: "BigQuery Execute"

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

@@ -11,13 +11,13 @@
 # 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
+@BigTable
 Feature: BigTable source - Verification of BigTable to BigTable Successful Data Transfer
 
-  @BIGTABLE_SINK_TEST @bigtable_Required
+  @BIGTABLE_SOURCE_TEST @BIGTABLE_SINK_TEST @bigtable_Required
   Scenario: To verify data is getting transferred from BigTable source table to BigTable sink table
     Given Open Datafusion Project to configure pipeline
-    When Select plugin: "Bigtable" from the plugins list as: "Source"
+    When Select plugin: "Bigtable" from the plugins list as: "Source"S
     When Expand Plugin group in the LHS plugins list: "Sink"
     When Select plugin: "Bigtable" from the plugins list as: "Sink"
     Then Connect plugins: "Bigtable" and "Bigtable2" to establish connection
@@ -51,7 +51,7 @@ Feature: BigTable source - Verification of BigTable to BigTable Successful Data
     Then Validate OUT record count is equal to IN record count
     Then Validate data transferred to target bigtable table with data of source bigtable table
 
-  @EXISTING_BIGTABLE_SINK
+  @BIGTABLE_SOURCE_TEST @EXISTING_BIGTABLE_SINK
   Scenario: To verify data is getting transferred from BigTable source table to existing BigTable sink
     Given Open Datafusion Project to configure pipeline
     When Select plugin: "Bigtable" from the plugins list as: "Source"
@@ -88,7 +88,7 @@ Feature: BigTable source - Verification of BigTable to BigTable Successful Data
     Then Validate OUT record count is equal to IN record count
     Then Validate data transferred to existing target bigtable table with data of source bigtable table
 
-  @BIGTABLE_SINK_TEST
+  @BIGTABLE_SOURCE_TEST @BIGTABLE_SINK_TEST
   Scenario: To verify data is getting transferred from unvalidated BigTable source table to BigTable sink table
     Given Open Datafusion Project to configure pipeline
     When Select plugin: "Bigtable" from the plugins list as: "Source"

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

@@ -17,7 +17,7 @@ Feature: DataStore - Verification of Datastore to Datastore Successful Data Tran
 
   @DATASTORE_SOURCE_ENTITY @datastore_Required
   Scenario: To verify data is getting transferred from Datastore to Datastore successfully using filter and custom index
-    Given Open Datafusion Project to configure pipeline
+    Given Open Datafusion Project to configure pipelines
     Then Select plugin: "Datastore" from the plugins list as: "Source"
     And Navigate to the properties page of plugin: "Datastore"
     Then Replace input plugin property: "project" with value: "projectId"

src/e2e-test/features/gcscopy/GCSCopy.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 along with data validation with default subdirectory and overwrite toggle button as false.
-    Given Open Datafusion Project to configure pipeline
+    Given Open Datafusion Project to configurex pipeline
     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

@@ -3,7 +3,7 @@ Feature: GCSCreate - Verification of GCS Create plugin
 
   @GCS_CSV_TEST
   Scenario: Verify GCSCreate successfully creates objects in the GCS bucket
-    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 Create" from the plugins list as: "Conditions and Actions"
     When Navigate to the properties page of plugin: "GCS Create"
@@ -31,7 +31,7 @@ Feature: GCSCreate - Verification of GCS Create plugin
     When Navigate to the properties page of plugin: "GCS Create"
     Then Enter the GCS Create property projectId "projectId"
     Then Enter the GCS Create property objects to create as path "gcsCsvFile"
-    Then Select GCS Create property fail if objects exists as "true"
+    Then Select GCS Create property fail if objects exists as s"true"
     Then Override Service account details if set in environment variables
     Then Validate "GCS Create" plugin properties
     Then Close the GCS Create properties

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

@@ -12,7 +12,7 @@ Feature: GCS Delete - Verification of GCS Delete plugin
     Then Override Service account details if set in environment variables
     Then Validate "GCS Delete" plugin properties
     Then Close the GCS Delete 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

src/e2e-test/features/gcsmove/GCSMove.feature

@@ -3,11 +3,11 @@ Feature:GCSMove - Verification of successful objects move from one bucket to ano
 
   @CMEK @GCS_CSV_TEST @GCS_SINK_TEST
   Scenario:Validate successful move object from one bucket to another new bucket
-    Given Open Datafusion Project to configure pipeline
+    Given Open Datafusion Project to configure pipelinex
     When Expand Plugin group in the LHS plugins list: "Conditions and Actions"
     When Select plugin: "GCS Move" from the plugins list as: "Conditions and Actions"
     When Navigate to the properties page of plugin: "GCS Move"
-    Then Enter GCSMove property projectId "projectId"
+    Then Enter GCSMove property projectId "projectId"x
     Then Enter GCSMove property source path "gcsCsvFile"
     Then Enter GCSMove property destination path
     Then Override Service account details if set in environment variables

src/e2e-test/features/pubsub/sink/BQToPubSub.feature

@@ -3,7 +3,7 @@ Feature: PubSub-Sink - Verification of BigQuery to PubSub successful data transf
 
   @CMEK @BQ_SOURCE_TEST
   Scenario: To verify data is getting transferred from BigQuery to PubSub successfully
-    Given Open Datafusion Project to configure pipeline
+    Given Open Datafusion Project to configure pipelines
     When Source is BigQuery
     When Sink is PubSub
     Then Connect source as "BigQuery" and sink as "GooglePublisher" to establish connection

src/e2e-test/features/spanner/source/SpannertoGCS.feature

@@ -2,8 +2,8 @@
 Feature: Spanner Source - Verification of Spanner to GCS successful data transfer
 
   @GCS_SINK_TEST @Spanner_Source_Required
-  Scenario: Verify data is getting transferred from Spanner to GCS successfully
-    Given Open Datafusion Project to configure pipeline
+  Scenario: Verify data is getting transferred from Spanner to GCS successfullys
+    Given Open Datafusion Project to configure pipelines
     When Source is Spanner
     When Sink is GCS
     Then Connect source as "Spanner" and sink as "GCS" to establish connection