Added test for sending share invitation to disabled user (#8174)

tests/acceptance/features/apiGraph/addUserToGroup.feature

@@ -272,7 +272,7 @@ Feature: add users to group
     Given these groups have been created:
       | groupname | comment      |
       | sales     | normal group |
-    And the user "Admin" has disabled user "Alice" using the Graph API
+    And the user "Admin" has disabled user "Alice"
     When the administrator adds the following users to the following groups using the Graph API
       | username | groupname |
       | Alice    | sales     |

tests/acceptance/features/apiGraph/createUser.feature

@@ -68,7 +68,7 @@ Feature: create user
   Scenario: user cannot be created with the name of the disabled user
     Given user "Brian" has been created with default attributes and without skeleton files
     And the administrator has assigned the role "Admin" to user "Alice" using the Graph API
-    And the user "Alice" has disabled user "Brian" using the Graph API
+    And the user "Alice" has disabled user "Brian"
     When the user "Alice" creates a new user with the following attributes using the Graph API:
       | userName       | Brian                 |
       | displayName    | This is another Brian |

tests/acceptance/features/apiGraph/deleteUser.feature

@@ -112,7 +112,7 @@ Feature: delete user
   Scenario: admin user deletes a disabled user
     Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
     And user "Brian" has been created with default attributes and without skeleton files
-    And the user "Alice" has disabled user "Brian" using the Graph API
+    And the user "Alice" has disabled user "Brian"
     When the user "Alice" deletes a user "Brian" using the Graph API
     Then the HTTP status code should be "204"
     And user "Brian" should not exist
@@ -124,7 +124,7 @@ Feature: delete user
     And user "Carol" has been created with default attributes and without skeleton files
     And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
     And the administrator has assigned the role "<userRole>" to user "Carol" using the Graph API
-    And the user "Alice" has disabled user "Brian" using the Graph API
+    And the user "Alice" has disabled user "Brian"
     When the user "Carol" deletes a user "Brian" using the Graph API
     Then the HTTP status code should be "401"
     And user "Brian" should exist

tests/acceptance/features/apiGraph/editUser.feature

@@ -76,7 +76,7 @@ Feature: edit user
       | displayName | sam             |
       | email       | sam@example.com |
       | password    | 1234            |
-    And the user "Alice" has disabled user "Brian" using the Graph API
+    And the user "Alice" has disabled user "Brian"
     When the user "Alice" changes the user name of user "sam" to "Brian" using the Graph API
     Then the HTTP status code should be "409"
     And the user information of "sam" should match this JSON schema
@@ -410,7 +410,7 @@ Feature: edit user
 
 
   Scenario: admin user enables disabled user
-    Given the user "Alice" has disabled user "Brian" using the Graph API
+    Given the user "Alice" has disabled user "Brian"
     When the user "Alice" enables user "Brian" using the Graph API
     Then the HTTP status code should be "200"
     When user "Alice" gets information of user "Brian" using Graph API
@@ -454,7 +454,7 @@ Feature: edit user
 
   Scenario Outline: normal user should not be able to enable another user
     Given user "Carol" has been created with default attributes and without skeleton files
-    And the user "Alice" has disabled user "Carol" using the Graph API
+    And the user "Alice" has disabled user "Carol"
     And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
     When the user "Brian" tries to enable user "Carol" using the Graph API
     Then the HTTP status code should be "401"

tests/acceptance/features/apiGraph/getUser.feature

@@ -176,7 +176,7 @@ Feature: get users
 
   Scenario: admin user gets all users include disabled users
     Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
-    And the user "Alice" has disabled user "Brian" using the Graph API
+    And the user "Alice" has disabled user "Brian"
     When user "Alice" gets all users using the Graph API
     Then the HTTP status code should be "200"
     And the JSON data of the response should contain the user "Alice Hansen" in the item 'value', the user-details should match
@@ -656,7 +656,7 @@ Feature: get users
   Scenario: admin user gets all users of certain groups
     Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
     And user "Carol" has been created with default attributes and without skeleton files
-    And the user "Alice" has disabled user "Carol" using the Graph API
+    And the user "Alice" has disabled user "Carol"
     And group "tea-lover" has been created
     And group "coffee-lover" has been created
     And user "Alice" has been added to group "tea-lover"

tests/acceptance/features/apiGraph/removeUserFromGroup.feature

@@ -200,7 +200,7 @@ Feature: remove a user from a group
     And the following users have been added to the following groups
       | username | groupname       |
       | Alice    | brand-new-group |
-    And the user "Admin" has disabled user "Alice" using the Graph API
+    And the user "Admin" has disabled user "Alice"
     When the administrator removes the following users from the following groups using the Graph API
       | username | groupname       |
       | Alice    | brand-new-group |