Skip to content
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

Gherkin: Generic managed service flow - topology #9768

Conversation

sanketpathak
Copy link
Contributor

@sanketpathak sanketpathak commented Aug 9, 2021

Epic: https://issues.redhat.com/browse/ODC-5722
Story: https://issues.redhat.com/browse/ODC-5962

Acceptance criteria:

  • Display bindable external services in topology as a trapezoid
  • Users can create binding connections to any bindable external service

Checks required for approving Epic gherkin scripts PR:

  • Add @epic-number to the scenarios or feature file [e.g: @odc-xxx]
  • Add @to-do for automation possible scenarios
  • Add @regression or @smoke based on the importance of the scenario
  • Update the test scenarios count in Automation status confluence Report
  • Check for the linter issues by executing yarn run gherkin-lint on frontend folder [Skip epic number tags related linter issues]

@openshift-ci openshift-ci bot added the component/topology Related to topology label Aug 9, 2021
@sanketpathak
Copy link
Contributor Author

/assign @sahil143

@sanketpathak
Copy link
Contributor Author

/cc @invincibleJai

Comment on lines 279 to 284
Scenario: Display of External Bindable resources: T-06-TC24
Given user has created external bindable resource
When user goes to Topology chart view
Then user will see the bindable resource in trapezoid shape
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This scenario will also require us to install SBO

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added the step for it

@sanketpathak sanketpathak force-pushed the gherkin-generic-managed-service-flow-topology branch from e36b803 to 5b4de3d Compare August 11, 2021 11:04
Copy link
Contributor

@sahil143 sahil143 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 16, 2021
@sanketpathak
Copy link
Contributor Author

/assign @makambalaji

When user created a deployment workload
And user drag the connector from the deployment workload
And user drops the connector on the enabled bindable resource
Then user will see service binding connection
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add the empty new line

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added

@sanketpathak sanketpathak force-pushed the gherkin-generic-managed-service-flow-topology branch from 5b4de3d to ea28856 Compare August 19, 2021 10:11
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2021
Copy link
Contributor

@gajanan-more gajanan-more left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Aug 19, 2021
@@ -273,3 +273,22 @@ Feature: Topology chart area
And user sees shortcut for Access create connector handle
And user sees shortcut for Qpen quick search modal
And user sees shortcut for Drag and drop a JAR file into Topology


@regression @manual @5722
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should be consistent with the tags. For everything that's not yet automated, do we use the tag @Manual, or @to-do? Similarly @ODC-5722 vs @5722. I've seen both looking on other PR's

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If it's a manual scenario, then we are adding @Manual
@to-do, If the scenario is able to automate, but not yet automated. then we will add this tag
@sanketpathak - Please update the epic number as @ODC-5722

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

@sanketpathak sanketpathak force-pushed the gherkin-generic-managed-service-flow-topology branch from ea28856 to 20cabce Compare August 30, 2021 14:40
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Aug 30, 2021
@regression @manual @odc-5722
Scenario: Display of External Bindable resources: T-06-TC24
Given user has installed Service Binding operator
And user has created external bindable resource
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add the steps to create external bindable resource with in this scenario, so that while executing this scenario. It is easier.
Include the test data as well

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can only use kafka connection(RHOAS) as of now for the external bindable resource, I'll rewrite it as:
user has created external bindable resource Kafka Connection "kafka-instance-123"

Scenario: Display of External Bindable resources: T-06-TC24
Given user has installed Service Binding operator
And user has created external bindable resource
When user goes to Topology chart view
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
When user goes to Topology chart view
When user navigates to Topology chart view

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

Given user has installed Service Binding operator
And user has created external bindable resource
When user goes to Topology chart view
Then user will see the bindable resource in trapezoid shape
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Include the test data in this step

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in the statement

@regression @manual @odc-5722
Scenario: Connect to External Bindable resources: T-06-TC25
Given user has installed Service Binding operator
And user has created external bindable resource
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Provide the data which is used in above scenario

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated in the statement

Comment on lines 291 to 296
When user created a deployment workload
And user drag the connector from the deployment workload
And user drops the connector on the enabled bindable resource
Then user will see service binding connection
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Provide the test data here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above

@sanketpathak sanketpathak force-pushed the gherkin-generic-managed-service-flow-topology branch from 20cabce to 6ed00d3 Compare August 31, 2021 09:52
#Please refer to test case KM-01-TC01 for creating kafka connection
And user has created external bindable resource Kafka Connection "kafka-instance-123"
When user navigates to Topology chart view
Then user will see the bindable resource in trapezoid shape
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Then user will see the bindable resource in trapezoid shape
Then user will see the bindable resource "kafka-instance-123" in trapezoid shape

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

#Please refer to test case KM-01-TC01 for creating kafka connection
And user has created external bindable resource Kafka Connection "kafka-instance-123"
And user is at the Topology chart view
When user created a deployment workload
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add deployment workload name

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

@sanketpathak sanketpathak force-pushed the gherkin-generic-managed-service-flow-topology branch from 6ed00d3 to 91c4ae2 Compare August 31, 2021 10:04
@makambalaji
Copy link
Contributor

/approve

@makambalaji
Copy link
Contributor

/label px-approved
/label docs-approved
/label qe-approved

@openshift-ci openshift-ci bot added the px-approved Signifies that Product Support has signed off on this PR label Aug 31, 2021
@openshift-ci openshift-ci bot added docs-approved Signifies that Docs has signed off on this PR qe-approved Signifies that QE has signed off on this PR labels Aug 31, 2021
@makambalaji
Copy link
Contributor

/approve

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 31, 2021
@makambalaji
Copy link
Contributor

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 1, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 1, 2021

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gajanan-more, makambalaji, sahil143, sanketpathak

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit eb8837b into openshift:master Sep 1, 2021
@spadgett spadgett added this to the v4.9 milestone Sep 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. component/topology Related to topology docs-approved Signifies that Docs has signed off on this PR lgtm Indicates that a PR is ready to be merged. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants