-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Functional test] [WIP] Cluster feature #1063
Changes from 1 commit
a6ea712
d0b2790
052409b
8eb8bfc
c0f5e18
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,91 @@ | ||
Feature: CLUSTER | ||
Feature: CLUSTER | ||
|
||
Scenario: Import a cluster | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Scenario: Import Cluster page should be available |
||
Given User is on "clusters" page | ||
When User should see the "import" button | ||
And User clicks on "import" button | ||
Then User sees the "import-clusters" page | ||
|
||
Scenario: Unmanage a cluster | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This scenario should come once the import is done so move it after There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. will move this also in import and unmanage feature file |
||
Given User is on "clusters" page | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
|
||
When User clicks on cluster dropdown | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. it's a kebab menu. |
||
And User clicks on unmanage button | ||
And User sees "Unmanage Cluster" dialogue box | ||
And User clicks on "unmanage" button | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Need consistency with being generic or not generic |
||
Then User should see "unmanage cluster" "task page" | ||
And User closes "task page" | ||
And User sees cluster is unmanaged | ||
|
||
Scenario: Naming an imported cluster | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This has multiple scenarios. Normal import I suggest we create a new file for import There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I agree |
||
Given User is on "clusters" page | ||
And User should see the "import" button | ||
And User clicks on "import" button | ||
And User sees the "import-clusters" page | ||
When User enters cluster name | ||
And User clicks on "import" button | ||
Then User sees "task submitted" page | ||
And User clicks on "close" button | ||
Then User sees the "cluster" page | ||
And User sees name in cluster list view | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Maybe make cluster name generic so you can assert that what was entered is equal to what appears at the end |
||
|
||
Scenario: Filter by valid cluster name | ||
Given User is on "clusters" page | ||
When User filters by a "valid" cluster name | ||
Then User should see the cluster name | ||
|
||
Scenario: Filter by invalid cluster name | ||
Given User is on "clusters" page | ||
When User filters by an "invalid" cluster name | ||
Then User should see no clusters | ||
|
||
Scenario: Cluster status Icon in list view | ||
Given User is on "clusters" page | ||
When I see "cluster" list view available | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Use "User" instead of "I" |
||
Then I should see the Cluster status Icon in list view | ||
|
||
Scenario: Cluster name in list view | ||
Given User is on "clusters" page | ||
When I see "cluster" list view available | ||
And I should see the hyperlink on Cluster Name | ||
And I click on Cluster name | ||
Then I should see the object detail view | ||
|
||
Scenario: Cluster version in list view | ||
Given User is on "clusters" page | ||
When I see "cluster" list view available | ||
And I should see the hyperlink on Cluster Name | ||
And I click on Cluster name | ||
Then I should see the object detail view | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is exactly the same as the scenario above apart from the title |
||
|
||
Scenario: Hosts in list view | ||
Given User is on "clusters" page | ||
When I see "cluster" list view available | ||
And I should see the hyperlink on Hosts number | ||
And I click on the Number | ||
Then I should see the "cluster-hosts" page | ||
|
||
Scenario: Cluster options dropdown is clicked | ||
Given User is on "clusters" page | ||
And User opens the clusters page | ||
When User clicks cluster dropdown | ||
Then The cluster names are listed | ||
|
||
Scenario: Sort the Clusters by Name | ||
Given User is on "clusters" page | ||
When User should select "name" from the dropdownzz | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "dropdownzz" |
||
Then User should see the List view sorted on basis of "name" | ||
|
||
Scenario: Sort the Clusters by Status | ||
Given User is on "clusters" page | ||
When User should select "status" from the dropdown | ||
Then User should see the List view sorted on basis of "status" | ||
|
||
Scenario: Sort the Clusters by Cluster Version | ||
Given User is on "clusters" page | ||
When User should select "status" from the dropdown | ||
Then User should see the List view sorted on basis of "cluster version" | ||
|
||
Scenario: Sort the Clusters by Managed | ||
Given User is on "clusters" page | ||
When User should select "utilization" from the dropdown | ||
Then User should see the List view sorted on basis of "managed" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the first scenario should be the user is on cluster list page and user is able to see one cluster at least.