Scenario:  Bind multiple applications to a service
        Given Generic test application "app1" is running with label "release=3.0"
        And Generic test application "app2" is running with label "release=3.0"
        And Service Binding is applied
            """
            apiVersion: binding.operators.coreos.com/v1alpha1
            kind: ServiceBinding
            metadata:
                name: service-binding-multiple-app
            spec:
                services:
                  - group: stable.example.com
                    version: v1
                    kind: Backend
                    name: service-1
                application:
                    matchLabels: 
                               release: 3.0
                    group: apps
                    version: v1
                    resource: deployments
            """
        * CustomResourceDefinition backends.stable.example.com is available
        When The Custom Resource is present
            """
            apiVersion: stable.example.com/v1
            kind: Backend
            metadata:
                name: service-a-b-s
                annotations:
                    service.binding: path={.status.data.dbCredentials},objectType=Secret,elementType=map
            spec:
                    host: example.comm
            """
        Then Service Binding "service-binding-multiple-app" is ready
        And Content of file "/bindings/service-binding-multiple-app/host" in application "app-1" pod is
            """
            example.com
            """
        And Content of file "/bindings/service-binding-multiple-app/host" in application "app-2" pod is
            """
            example.com
            """

 @negative
    Scenario: Service Binding with both name and matchLabels field is not allowed
        When Service Binding is applied
            """
            apiVersion: binding.operators.coreos.com/v1alpha1
            kind: ServiceBinding
            metadata:
                name: service-binding-name-label
            spec:
                services:
                  - group: stable.example.com
                    version: v1
                    kind: Backend
                    name: service-1
                application:
                    name: generic-application
                    matchLabels: 
                               release: 3.0
                    group: apps
                    version: v1
                    resource: deployments
            """
        Then Error message is thrown
        And Service Binding "binding-request-name-label" is not persistent in the cluster