using Graph instead Of Setting Method In Tests

tests/acceptance/features/apiGraph/getUser.feature

@@ -12,7 +12,7 @@ Feature: get users
 
   @skipOnStable2.0
   Scenario: admin user gets the information of a user
-    Given the administrator has given "Alice" the role "Admin" using the settings api
+    Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
     When user "Alice" gets information of user "Brian" using Graph API
     Then the HTTP status code should be "200"
     And the JSON data of the response should match
@@ -53,8 +53,8 @@ Feature: get users
 
   @issue-5125
   Scenario Outline: non-admin user tries to get the information of a user
-    Given the administrator has given "Alice" the role "<role>" using the settings api
-    And the administrator has given "Brian" the role "<userRole>" using the settings api
+    Given the administrator has assigned the role "<role>" to user "Alice" using the Graph API
+    And the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
     When user "Brian" tries to get information of user "Alice" using Graph API
     Then the HTTP status code should be "401"
     And the JSON data of the response should match
@@ -95,7 +95,7 @@ Feature: get users
 
   @skipOnStable2.0
   Scenario: admin user gets all users
-    Given the administrator has given "Alice" the role "Admin" using the settings api
+    Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
     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
@@ -161,7 +161,7 @@ Feature: get users
 
   @skipOnStable2.0
   Scenario: admin user gets all users include disabled users
-    Given the administrator has given "Alice" the role "Admin" using the settings api
+    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
     When user "Alice" gets all users using the Graph API
     Then the HTTP status code should be "200"
@@ -228,7 +228,7 @@ Feature: get users
 
 
   Scenario Outline: non-admin user tries to get all users
-    Given the administrator has given "Alice" the role "<userRole>" using the settings api
+    Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
     When user "Brian" tries to get all users using the Graph API
     Then the HTTP status code should be "401"
     And the JSON data of the response should match
@@ -260,7 +260,7 @@ Feature: get users
 
   @skipOnStable2.0
   Scenario: admin user gets the drive information of a user
-    Given the administrator has given "Alice" the role "Admin" using the settings api
+    Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
     When the user "Alice" gets user "Brian" along with his drive information using Graph API
     Then the HTTP status code should be "200"
     And the JSON data of the response should match
@@ -383,7 +383,7 @@ Feature: get users
 
   @skipOnStable2.0
   Scenario Outline: non-admin user gets his/her own drive information
-    Given the administrator has given "Brian" the role "<userRole>" using the settings api
+    Given the administrator has assigned the role "<userRole>" to user "Brian" using the Graph API
     When the user "Brian" gets his drive information using Graph API
     Then the HTTP status code should be "200"
     And the JSON data of the response should match
@@ -511,7 +511,7 @@ Feature: get users
 
   @skipOnStable2.0
   Scenario: admin user gets the group information of a user
-    Given the administrator has given "Alice" the role "Admin" using the settings api
+    Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
     And group "tea-lover" has been created
     And group "coffee-lover" has been created
     And user "Brian" has been added to group "tea-lover"
@@ -575,8 +575,8 @@ Feature: get users
 
   @issue-5125
   Scenario Outline: non-admin user tries to get the group information of a user
-    Given the administrator has given "Alice" the role "<userRole>" using the settings api
-    And the administrator has given "Brian" the role "<role>" using the settings api
+    Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
+    And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
     And group "coffee-lover" has been created
     And user "Brian" has been added to group "coffee-lover"
     When the user "Alice" gets user "Brian" along with his group information using Graph API
@@ -619,7 +619,7 @@ Feature: get users
 
   @skipOnStable2.0
   Scenario: admin user gets all users of certain groups
-    Given the administrator has given "Alice" the role "Admin" using the settings api
+    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 group "tea-lover" has been created
@@ -753,7 +753,7 @@ Feature: get users
 
   @skipOnStable2.0
   Scenario: admin user gets all users of two groups
-    Given the administrator has given "Alice" the role "Admin" using the settings api
+    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 group "tea-lover" has been created
     And group "coffee-lover" has been created
@@ -827,8 +827,8 @@ Feature: get users
 
   @skipOnStable2.0
   Scenario Outline: non admin user tries to get users of certain groups
-    Given the administrator has given "Alice" the role "Admin" using the settings api
-    And the administrator has given "Brian" the role "<role>" using the settings api
+    Given the administrator has assigned the role "Admin" to user "Alice" using the Graph API
+    And the administrator has assigned the role "<role>" to user "Brian" using the Graph API
     And group "tea-lover" has been created
     And user "Alice" has been added to group "tea-lover"
     When the user "Brian" gets all users of the group "tea-lover" using the Graph API
@@ -862,10 +862,10 @@ Feature: get users
 
   @skipOnStable2.0
   Scenario: admin user gets all users with certain roles and members of a certain group
-    Given the administrator has given "Alice" the role "Admin" using the settings api
+    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 administrator has given "Brian" the role "Space Admin" using the settings api
-    And the administrator has given "Carol" the role "Space Admin" using the settings api
+    And the administrator has assigned the role "Space Admin" to user "Brian" using the Graph API
+    And the administrator has assigned the role "Space Admin" to user "Carol" using the Graph API
     And group "tea-lover" has been created
     And user "Brian" has been added to group "tea-lover"
     When the user "Alice" gets all users with role "Space Admin" using the Graph API
@@ -967,7 +967,7 @@ Feature: get users
 
   @skipOnStable2.0
   Scenario Outline: non-admin user tries to get users with a certain role
-    Given the administrator has given "Alice" the role "<userRole>" using the settings api
+    Given the administrator has assigned the role "<userRole>" to user "Alice" using the Graph API
     When the user "Alice" gets all users with role "<role>" using the Graph API
     Then the HTTP status code should be "401"
     And the JSON data of the response should match