Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Gherkin:Getting Started - Spring Boot-ODC-4389
- Loading branch information
Sanket
committed
Mar 12, 2021
1 parent
a26cab4
commit 725804d
Showing
5 changed files
with
324 additions
and
22 deletions.
There are no files selected for viewing
157 changes: 157 additions & 0 deletions
157
frontend/packages/dev-console/integration-tests/features/addFlow/upload-JAR-file.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,157 @@ | ||
Feature: Upload JAR file | ||
As a user, I want to upload a JAR file from using Upload JAR file card from Add page | ||
|
||
Background: | ||
Given user is at developer perspective | ||
And user is at Add page | ||
And user has created or selected namespace "aut-upload-jar-file" | ||
|
||
|
||
@regression @manual | ||
Scenario Outline: Upload JAR file from Add options | ||
Given user is at the Add page | ||
When user clicks on the Upload JAR file card | ||
And user clicks on Browse in JAR file section | ||
And user selects file to upload | ||
And user selects appropriate Build image version | ||
And user gives Application name as "sample-upload-app" and workload Name as "<name>" | ||
And user selects resource type as "<resource_type>" | ||
And user clicks create button | ||
Then user will be redirected to Topology page | ||
And user can see a toast notification of JAR file uploading with link to build logs | ||
And user can see "<resource_type>" "<name>" in application "sample-upload-app" is created in topology | ||
|
||
Examples: | ||
| name | resource_type | | ||
| sample-yaml-upload-1 | Deployment | | ||
| sample-yaml-upload-2 | Deployment Config | | ||
|
||
@regression @manual | ||
Scenario Outline: Upload JAR file through drag and drop from Add options | ||
Given user is at the Add page | ||
When user clicks on the Upload JAR file card | ||
And user drag and drop the file in JAR file section | ||
And user selects appropriate Build image version | ||
And user gives Application name as "sample-upload-app" and workload Name as "<name>" | ||
And user selects resource type as "<resource_type>" | ||
And user clicks create button | ||
Then user will be redirected to Topology page | ||
And user can see a toast notification of JAR file uploading with link to build logs | ||
And user can see "<resource_type>" "<name>" in application "sample-upload-app" is created in topology | ||
|
||
Examples: | ||
| name | resource_type | | ||
| sample-yaml-upload-a | Deployment | | ||
| sample-yaml-upload-b | Deployment Config | | ||
|
||
|
||
@regression | ||
Scenario: Upload JAR file with advanced option "Health Checks" : A-04-TC12 | ||
When user is on the Upload JAR file form | ||
And user clicks on Browse in JAR file section | ||
And user selects file to upload | ||
And user gives Application name as "sample-upload-app" and workload Name as "sample-yaml-upload" | ||
And user clicks "Health Checks" link in Advanced Options section | ||
And user fills the Readiness Probe details | ||
And user fills the Liveness Probe details | ||
And user fills the Startup Probe details | ||
And user clicks Create button on Add page | ||
Then user will be redirected to Topology page | ||
|
||
|
||
@regression | ||
Scenario: Upload JAR file without application route : A-04-TC05 | ||
When user is on the Upload JAR file form | ||
And user clicks on Browse in JAR file section | ||
And user selects file to upload | ||
And user gives Application name as "sample-upload-app" and workload Name as "sample-yaml-upload" | ||
And user unselects the advanced option Create a route to the application | ||
And user clicks Create button on Add page | ||
Then user will be redirected to Topology page | ||
And public url is not created for node "sample-yaml-upload" in the workload sidebar | ||
|
||
|
||
@regression | ||
Scenario: Upload JAR file with advanced option "Routing" : A-04-TC06 | ||
When user is on the Upload JAR file form | ||
And user clicks on Browse in JAR file section | ||
And user selects file to upload | ||
And user gives Application name as "sample-upload-app" and workload Name as "sample-yaml-upload" | ||
And user clicks "Routing" link in Advanced Options section | ||
And user enters Hostname as "home" | ||
And user enters Path as "/home" | ||
And user selects default Target Port | ||
And user clicks Create button on Add page | ||
Then user will be redirected to Topology page | ||
And the route of application "sample-yaml-upload" contains "home" in the Routes section of the workload sidebar | ||
|
||
|
||
@regression | ||
Scenario: Upload JAR file by unselecting options in "Build Configuration" section: A-04-TC07 | ||
When user is on the Upload JAR file form | ||
And user clicks on Browse in JAR file section | ||
And user selects file to upload | ||
And user gives Application name as "sample-upload-app" and workload Name as "sample-yaml-upload" | ||
And user clicks "Build Configuration" link in Advanced Options section | ||
And user unselects Configure a webhook build trigger checkbox in build configuration section | ||
And user unselects Automatically build a new image when the builder image changes checkbox in build configuration section | ||
And user unselects Launch the first build when the build configuration is created checkbox in build configuration section | ||
And user enters Name as "home" in Environment Variables section | ||
And user enters Value as "value" in Environment Variables section | ||
And user clicks Create button on Add page | ||
Then user will be redirected to Topology page | ||
And build does not get started for "sample-yaml-upload" | ||
|
||
|
||
@regression | ||
Scenario: Upload JAR file with advanced option "Deployment" : A-04-TC08 | ||
When user is on the Upload JAR file form | ||
And user clicks on Browse in JAR file section | ||
And user selects file to upload | ||
And user gives Application name as "sample-upload-app" and workload Name as "sample-yaml-upload" | ||
And user clicks "Deployment" link in Advanced Options section | ||
And user verify the Auto deploy when new image is available checkbox is selected | ||
And user enters Name as "home" in Environment Variables Runtime only section | ||
And user enters Value as "value" in Environment Variables Runtime only section | ||
And user clicks Create button on Add page | ||
Then user will be redirected to Topology page | ||
|
||
|
||
@regression | ||
Scenario: Upload JAR file with advanced option "Resource Limits" : A-04-TC09 | ||
When user is on the Upload JAR file form | ||
And user clicks on Browse in JAR file section | ||
And user selects file to upload | ||
And user gives Application name as "sample-upload-app" and workload Name as "sample-yaml-upload" | ||
And user clicks "Resource Limits" link in Advanced Options section | ||
And user enters CPU Request as "10" in CPU section | ||
And user enters CPU Limits as "12" in CPU section | ||
And user enters Memory Request as "200" in Memory section | ||
And user enters Memory Limit as "300" in Memory section | ||
And user clicks Create button on Add page | ||
Then user will be redirected to Topology page | ||
|
||
|
||
@regression | ||
Scenario: Upload JAR file with advanced option "Scaling" : A-04-TC10 | ||
When user is on the Upload JAR file form | ||
And user clicks on Browse in JAR file section | ||
And user selects file to upload | ||
And user gives Application name as "sample-upload-app" and workload Name as "sample-yaml-upload" | ||
And user clicks "Scaling" link in Advanced Options section | ||
And user enters number of replicas as "5" in Replicas section | ||
And user clicks Create button on Add page | ||
Then user will be redirected to Topology page | ||
|
||
|
||
@regression | ||
Scenario: Upload JAR file with advanced option "Labels" : A-04-TC11 | ||
When user is on the Upload JAR file form | ||
And user clicks on Browse in JAR file section | ||
And user selects file to upload | ||
And user gives Application name as "sample-upload-app" and workload Name as "sample-yaml-upload" | ||
And user clicks "Labels" link in Advanced Options section | ||
And user enters label as "app=frontend" | ||
And user clicks Create button on Add page | ||
Then user will be redirected to Topology page | ||
And verify the label "app=frontend" in side bar of application node "sample-yaml-upload" |
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
80 changes: 58 additions & 22 deletions
80
frontend/packages/dev-console/integration-tests/features/topology/topology-list-view.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 |
---|---|---|
@@ -1,25 +1,61 @@ | ||
Feature: List view in topology | ||
As a user, I want to see list view in topology | ||
|
||
Background: | ||
Given user is at developer perspective | ||
And user has selected namespace "aut-topology-list-view" | ||
|
||
|
||
@regression, @smoke | ||
Scenario: Topology List view : T-07-TC05 | ||
Given user created workload "nodejs-ex-git" with resource type "Deployment" | ||
When user clicks on List view button | ||
And user verifies the filter by resource on top | ||
Then user will see workloads are segregated by applications groupings | ||
|
||
@regression | ||
Scenario: Topology filter by resource: T-07-TC06, T-07-TC07 | ||
Given user created two workloads with resource type "Deployment" and "Deployment-Config" | ||
When user clicks on List view button | ||
And user clicks the filter by resource on top | ||
And user will see "Deployment" and "Deployment-Config" options with '1' associated with it | ||
And user clicks on Deployment | ||
And user can see only the deployment workload | ||
And user clicks on Deployment-Config | ||
Then user can see only the deployment-config workload | ||
Background: | ||
Given user is at developer perspective | ||
And user has selected namespace "aut-topology-list-view" | ||
|
||
|
||
@regression, @smoke | ||
Scenario: Topology List view : T-07-TC05 | ||
Given user created workload "nodejs-ex-git" with resource type "Deployment" | ||
When user clicks on List view button | ||
And user verifies the filter by resource on top | ||
Then user will see workloads are segregated by applications groupings | ||
|
||
|
||
@regression | ||
Scenario: Topology filter by resource: T-07-TC06, T-07-TC07 | ||
Given user created two workloads with resource type "Deployment" and "Deployment-Config" | ||
When user clicks on List view button | ||
And user clicks the filter by resource on top | ||
And user will see "Deployment" and "Deployment-Config" options with '1' associated with it | ||
And user clicks on Deployment | ||
And user can see only the deployment workload | ||
And user clicks on Deployment-Config | ||
Then user can see only the deployment-config workload | ||
|
||
|
||
@regression, @manual | ||
Scenario: Drag and drop jar file in topology list view | ||
Given user has a jar file named "sample_yaml_upload.yaml" | ||
And user is at the Topology list view page | ||
When user drags and drop jar file on topology | ||
And user gives Application name as "sample-upload-app" and workload Name as "sample-yaml-upload" in Upload JAR file form | ||
And user clicks on Create | ||
Then user is redirected to topology | ||
And user can see a toast notification of JAR file uploading with link to build logs | ||
And user can see deployment "sample-yaml-upload" in application "sample-upload-app" is created in topology | ||
|
||
|
||
@regression, @manual | ||
Scenario: Drag and drop Incompatible file in topology chart view | ||
Given user has a incompatible file | ||
And user is at the Topology chart view | ||
When user drags and drop the file on topology | ||
Then the curser will show the action is not available | ||
|
||
|
||
@regression, @manual | ||
Scenario: View shortcuts menu | ||
Given user has uploaded a jar file | ||
When user clicks on View shortcuts | ||
Then user sees shortcut for Drag and drop a JAR file into Topology | ||
|
||
|
||
@regression, @manual | ||
Scenario: Drag and drop Incompatible file in topology chart view | ||
Given user has a incompatible file | ||
And user is at the Topology chart view | ||
When user drags and drop the file on topology | ||
Then the curser will show the action is not available |
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