-
Notifications
You must be signed in to change notification settings - Fork 56
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #666 from priyabhatnagar25/Wrangler-parsing-2
wrangler e2e tests
- Loading branch information
Showing
29 changed files
with
1,161 additions
and
151 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
40 changes: 40 additions & 0 deletions
40
wrangler-transform/src/e2e-test/features/Wrangler/ParseAsExcel.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,40 @@ | ||
| # Copyright © 2023 Cask Data, Inc. | ||
| # | ||
| # Licensed under the Apache License, Version 2.0 (the "License"); you may not | ||
| # use this file except in compliance with the License. You may obtain a copy of | ||
| # the License at | ||
| # | ||
| # http://www.apache.org/licenses/LICENSE-2.0 | ||
| # | ||
| # Unless required by applicable law or agreed to in writing, software | ||
| # distributed under the License is distributed on an "AS IS" BASIS, WITHOUT | ||
| # WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the | ||
| # License for the specific language governing permissions and limitations under | ||
| # the License. | ||
|
|
||
| @Wrangler | ||
| Feature: Parse as excel | ||
|
|
||
| @GCS_SOURCE_TEST @BQ_SINK_TEST | ||
| Scenario: To verify User is able to run a pipeline using parse Excel directive | ||
| Given Open Datafusion Project to configure pipeline | ||
| Then Click on the Plus Green Button to import the pipelines | ||
| Then Select the file for importing the pipeline for the plugin "Directive_parse_excel" | ||
| Then Navigate to the properties page of plugin: "GCSFile" | ||
| Then Replace input plugin property: "project" with value: "projectId" | ||
| Then Replace input plugin property: "path" with value: "gcsSourceBucket" | ||
| Then Close the Plugin Properties page | ||
| Then Navigate to the properties page of plugin: "BigQuery" | ||
| Then Replace input plugin property: "project" with value: "projectId" | ||
| Then Replace input plugin property: "table" with value: "bqTargetTable" | ||
| Then Replace input plugin property: "dataset" with value: "dataset" | ||
| Then Validate "BigQuery" plugin properties | ||
| Then Close the Plugin Properties page | ||
| Then Rename the pipeline | ||
| Then Deploy the pipeline | ||
| Then Run the Pipeline in Runtime | ||
| Then Wait till pipeline is in running state | ||
| Then Open and capture logs | ||
| Then Verify the pipeline status is "Succeeded" | ||
| Then Close the pipeline logs | ||
| Then Validate The Data From BQ To BQ With Actual And Expected File for: "ExpectedDirective_parse_excel" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
43 changes: 43 additions & 0 deletions
43
wrangler-transform/src/e2e-test/features/Wrangler/ParseAsJson.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,43 @@ | ||
| # Copyright © 2023 Cask Data, Inc. | ||
| # | ||
| # Licensed under the Apache License, Version 2.0 (the "License"); you may not | ||
| # use this file except in compliance with the License. You may obtain a copy of | ||
| # the License at | ||
| # | ||
| # http://www.apache.org/licenses/LICENSE-2.0 | ||
| # | ||
| # Unless required by applicable law or agreed to in writing, software | ||
| # distributed under the License is distributed on an "AS IS" BASIS, WITHOUT | ||
| # WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the | ||
| # License for the specific language governing permissions and limitations under | ||
| # the License. | ||
|
|
||
| @Wrangler | ||
| Feature: parse as Json | ||
|
|
||
| @BQ_SOURCE_JSON_TEST @BQ_SOURCE_TEST @BQ_SINK_TEST | ||
| Scenario: To verify User is able to run a pipeline using parse Json directive | ||
| Given Open Datafusion Project to configure pipeline | ||
| Then Click on the Plus Green Button to import the pipelines | ||
| Then Select the file for importing the pipeline for the plugin "Directive_parse_json" | ||
| Then Navigate to the properties page of plugin: "BigQueryTable" | ||
| Then Replace input plugin property: "project" with value: "projectId" | ||
| Then Replace input plugin property: "dataset" with value: "dataset" | ||
| Then Replace input plugin property: "table" with value: "bqSourceTable" | ||
| Then Click on the Get Schema button | ||
| Then Validate "BigQueryTable" plugin properties | ||
| Then Close the Plugin Properties page | ||
| Then Navigate to the properties page of plugin: "BigQuery2" | ||
| Then Replace input plugin property: "project" with value: "projectId" | ||
| Then Replace input plugin property: "table" with value: "bqTargetTable" | ||
| Then Replace input plugin property: "dataset" with value: "dataset" | ||
| Then Validate "BigQuery2" plugin properties | ||
| Then Close the Plugin Properties page | ||
| Then Rename the pipeline | ||
| Then Deploy the pipeline | ||
| Then Run the Pipeline in Runtime | ||
| Then Wait till pipeline is in running state | ||
| Then Open and capture logs | ||
| Then Verify the pipeline status is "Succeeded" | ||
| Then Close the pipeline logs | ||
| Then Validate The Data From BQ To BQ With Actual And Expected File for: "ExpectedDirective_parse_json" |
43 changes: 43 additions & 0 deletions
43
wrangler-transform/src/e2e-test/features/Wrangler/ParseAsXmlToJson.feature
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,43 @@ | ||
| # Copyright © 2023 Cask Data, Inc. | ||
| # | ||
| # Licensed under the Apache License, Version 2.0 (the "License"); you may not | ||
| # use this file except in compliance with the License. You may obtain a copy of | ||
| # the License at | ||
| # | ||
| # http://www.apache.org/licenses/LICENSE-2.0 | ||
| # | ||
| # Unless required by applicable law or agreed to in writing, software | ||
| # distributed under the License is distributed on an "AS IS" BASIS, WITHOUT | ||
| # WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the | ||
| # License for the specific language governing permissions and limitations under | ||
| # the License. | ||
|
|
||
| @Wrangler | ||
| Feature: parse as XmlToJson | ||
|
|
||
| @BQ_SOURCE_XML_TEST @BQ_SOURCE_TEST @BQ_SINK_TEST | ||
| Scenario: To verify User is able to run a pipeline using parse XmlToJson directive | ||
| Given Open Datafusion Project to configure pipeline | ||
| Then Click on the Plus Green Button to import the pipelines | ||
| Then Select the file for importing the pipeline for the plugin "Directive_parse_xml" | ||
| Then Navigate to the properties page of plugin: "BigQueryTable" | ||
| Then Replace input plugin property: "project" with value: "projectId" | ||
| Then Replace input plugin property: "dataset" with value: "dataset" | ||
| Then Replace input plugin property: "table" with value: "bqSourceTable" | ||
| Then Click on the Get Schema button | ||
| Then Validate "BigQueryTable" plugin properties | ||
| Then Close the Plugin Properties page | ||
| Then Navigate to the properties page of plugin: "BigQuery2" | ||
| Then Replace input plugin property: "project" with value: "projectId" | ||
| Then Replace input plugin property: "table" with value: "bqTargetTable" | ||
| Then Replace input plugin property: "dataset" with value: "dataset" | ||
| Then Validate "BigQuery2" plugin properties | ||
| Then Close the Plugin Properties page | ||
| Then Rename the pipeline | ||
| Then Deploy the pipeline | ||
| Then Run the Pipeline in Runtime | ||
| Then Wait till pipeline is in running state | ||
| Then Open and capture logs | ||
| Then Verify the pipeline status is "Succeeded" | ||
| Then Close the pipeline logs | ||
| Then Validate The Data From BQ To BQ With Actual And Expected File for: "ExpectedDirective_parse_xml" |
Oops, something went wrong.