-
Notifications
You must be signed in to change notification settings - Fork 61
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Move tools e2e tests to kedro-starters (#209)
* add tools e2e tests * add tools.feature * run example_pipeline with "y" * fix run * update tools e2e tests to shortnames * update check_created_project_structure_from_tools for shortnames * add shortname changes to e2e run_steps * fix example_pipeline again
- Loading branch information
1 parent
ec560f8
commit 3783891
Showing
3 changed files
with
124 additions
and
1 deletion.
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
Feature: New Kedro project with tools | ||
|
||
Scenario: Create a new Kedro project without any tools | ||
Given I have prepared a config file with tools "none" | ||
When I run a non-interactive kedro new without starter | ||
Then the expected tool directories and files should be created with "none" | ||
Given I have installed the Kedro project's dependencies | ||
When I run the Kedro pipeline | ||
Then I should get a successful exit code | ||
|
||
Scenario: Create a new Kedro project with all tools except 'viz' and 'pyspark' | ||
Given I have prepared a config file with tools "lint, test, log, docs, data" | ||
When I run a non-interactive kedro new without starter | ||
Then the expected tool directories and files should be created with "lint, test, log, docs, data" | ||
Given I have installed the Kedro project's dependencies | ||
When I run the Kedro pipeline | ||
Then I should get a successful exit code | ||
|
||
Scenario: Create a new Kedro project with all tools | ||
Given I have prepared a config file with tools "all" | ||
When I run a non-interactive kedro new without starter | ||
Then the expected tool directories and files should be created with "all" | ||
Given I have installed the Kedro project's dependencies | ||
When I run the Kedro pipeline | ||
Then I should get a successful exit code | ||
|
||
Scenario: Create a new Kedro project with only 'pyspark' tool | ||
Given I have prepared a config file with tools "pyspark" | ||
When I run a non-interactive kedro new without starter | ||
Then the expected tool directories and files should be created with "pyspark" | ||
Given I have installed the Kedro project's dependencies | ||
When I run the Kedro pipeline | ||
Then I should get a successful exit code | ||
|
||
Scenario: Create a new Kedro project with only 'viz' tool | ||
Given I have prepared a config file with tools "viz" | ||
When I run a non-interactive kedro new without starter | ||
Then the expected tool directories and files should be created with "viz" | ||
Given I have installed the Kedro project's dependencies | ||
When I run the Kedro pipeline | ||
Then I should get a successful exit code |