# [APPSVC-357](https://issues.redhat.com/browse/APPSVC-357) UI-level in-cluster E2E scenarios - interoperability with OpenShift Console

@ui @user.admin
Feature: Install Service Binding Operator

    Background: Logged into OpenShift Console
        Given user is logged into OpenShift Console with admin permissions
        * Administrator view is opened

    Scenario: Install Community version of Service Binding Operator via OperaHub in OpenShift DevConsole
        Given OperatorHub page is opened
        * "Service Binding Operator" card is clicked and Community operators confirmed
        * "Install" button is clicked
        * "Installation Mode" is selected to be "All namespaces on the cluster (default)"
        * "Update Channel" is selected to be "alpha"
        * "Approval Strategy" is selected to be "Automatic"
        When "Subscribe" button is clicked
        Then "Installed Operators" page should be shown
        * Service Binding Operator with a "Succeeded" status should be present within 2 minutes

@ui @user.non-admin
Feature: Bind applications to services in topology view

    Background:
        Given user is logged into OpenShift Console with non-admin permissions
        * Service Binding Operator is installed
        * PostgreSQL DB operator is installed
        * Namespace "<nsName>" is used
        * "Topology" page in "Developer" view is opened

    Scenario: Bind Node.js application to PostgreSQL DB in topology view
        Given PostgreSQL DB instance "db-demo" is running and shown
        * imported Nodejs application "nodejs-rest-http-crud" is running and shown
        * application icon is hovered by mouse
        When arrow is dragged and dropped over to the DB icon
        Then application should be re-deployed
        * application should be connected to the DB "db-demo"