Add test tags in functional tests (#183)

To be able to run each test scenario individually tags were added to
test scenarios

Author: e-pettersson-ericsson

src/functionaltests/java/com/ericsson/ei/subscriptions/repeatHandler/SubscriptionRepeatHandlerSteps.java

@@ -77,7 +77,7 @@ public class SubscriptionRepeatHandlerSteps extends FunctionalTestBase {
     @Autowired
     private RunSubscription runSubscription;
 
-    @Before("@SubscriptionRepeatHandler")
+    @Before("@SubscriptionRepeatTrue, @SubscriptionRepeatFalse")
     public void beforeScenario() throws IOException, JSONException {
         assertTrue(mongoDBHandler.insertDocument(dataBaseName, collectionName,
                 eventManager.getJSONFromFile(AGGREGATED_OBJECT_FILE_PATH).toString()));

src/functionaltests/resources/features/queryAggregatedObjects.feature

@@ -2,6 +2,7 @@
 @tag
 Feature: QueryAggregatedObjectsTestSteps
 
+  @QueryAggregatedObjectsTestSteps
   Scenario: Test QueryAggregatedObjectsTestSteps
     Given Aggregated object is created
     And Missed Notification object is created
@@ -14,6 +15,7 @@ Feature: QueryAggregatedObjectsTestSteps
     And Perform a query on created Aggregated object with filter
     And Perform a query and filter with part of path
 
+  @QueryConfidenceLevelModified
   Scenario: Test QueryConfidenceLevelModified
     Given Aggregated object is created
     Then perform query to retrieve and filter out confidence level information

src/functionaltests/resources/features/ruleCheck.feature

@@ -19,36 +19,36 @@
 @tag
 Feature: Test Rules Checker
 
-  @tag1
+  @ExecuteRuleSingle
   Scenario: Execute JMESPath rule on JSON object
     Given file with JMESPath rules "/ExtractionRule.txt" and file with events "/EiffelArtifactCreatedEvent.json"
     When make a POST request to the REST API "/rules/rule-check" with a single rule
     Then get response code of 200
     And get content "/ExtractedContent.json"
 
-  #@tag2
+  @ExecuteRuleMultiple
   Scenario: Execute list of JMESPath rules on list of JSON objects
     Given rules checking is enabled
     And file with JMESPath rules "/AggregateListRules.json" and file with events "/AggregateListEvents.json"
     When make a POST request to the REST API "/rules/rule-check/aggregation"
     Then get response code of 200
     And get content "/AggregateResultObject.json"
 
-  #@tag3
+  @ExecuteIncorrectRule
   Scenario: Execute incorrect list of JMESPath rules on list of JSON objects
     Given rules checking is enabled
     And file with JMESPath rules "/AggregateListRules.json" and file with events "/subscription_single.json"
     When make a POST request to the REST API "/rules/rule-check/aggregation"
     Then get response code of 400
 
-  #@tag4
+  @ExecuteRuleDisabled
   Scenario: Execute list of JMESPath rules on list of JSON objects, when rules checking is not enabled
     Given rules checking is not enabled
     And file with JMESPath rules "/AggregateListRules.json" and file with events "/AggregateListEvents.json"
     When make a POST request to the REST API "/rules/rule-check/aggregation"
     Then get response code of 503
 
-  #@tag5
+  @RuleCheckStatus
   Scenario: Check status of test rule page using REST API
     When rules checking is enabled
     Then get request from REST API "/rules/rule-check/testRulePageEnabled" return response code of 200 and status as "true"

src/functionaltests/resources/features/subscriptionBulk.feature

@@ -18,44 +18,51 @@
 #Sample Feature Definition Template
 Feature: Test Subscription Bulk Operations
 
+  @CreateSubscriptions
   Scenario: Create multiple subscriptions using REST API
     Given file with subscriptions "/subscriptions_multiple.json"
     When make a POST request with list of subscriptions to the subscription REST API "/subscriptions"
     Then get response code of 200
     And number of retrieved subscriptions using REST API "/subscriptions" is 3
     And retrieved subscriptions are same as given
 
+  @GetSubscriptions
   Scenario: Fetch multiple subscriptions using REST API, one subscription does not exist
     When make a GET request with list of subscriptions names "Subscription_Test_1,Subscription_Test_Not_Found,Subscription_Test_2" to the subscription REST API "/subscriptions"
     Then get response code of 200
     And get in response content 2 found subscriptions and not found subscription name "Subscription_Test_Not_Found"
 
+  @CreateWithDuplicate
    Scenario: Create multiple subscriptions using REST API, one subscription already exists
      Given file with subscriptions "/subscriptions_multiple_wrong.json"
      When make a POST request with list of subscriptions to the subscription REST API "/subscriptions"
      Then get response code of 400
      And get in response content subscription "Subscription_Test_2"
      And number of retrieved subscriptions using REST API "/subscriptions" is 5
 
+  @DeleteSubscriptions
   Scenario: Delete multiple subscriptions using REST API
     When make a DELETE request with list of subscriptions names "Subscription_Test_4,Subscription_Test_5" to the subscription REST API "/subscriptions"
     Then get response code of 200
     And number of retrieved subscriptions using REST API "/subscriptions" is 3
 
+  @UpdateSubscriptions
   Scenario: Update multiple subscriptions using REST API
     Given file with subscriptions "/subscriptions_multiple_updated.json"
     When make a PUT request with list of subscriptions to the subscription REST API "/subscriptions"
     Then get response code of 200
     And number of retrieved subscriptions using REST API "/subscriptions" is 3
     And retrieved subscriptions are same as given
 
+  @UpdateSubscriptionsNonExisting
   Scenario: Update multiple subscriptions using REST API, one subscription does not exist
     Given file with subscriptions "/subscriptions_multiple_wrong_updated.json"
     When make a PUT request with list of subscriptions to the subscription REST API "/subscriptions"
     Then get response code of 400
     And get in response content subscription "Subscription_Test_Not_Found"
     And number of retrieved subscriptions using REST API "/subscriptions" is 3
 
+  @DeleteSubscriptionsNonExisting
   Scenario: Delete multiple subscriptions using REST API, one subscription does not exist
     When make a DELETE request with list of subscriptions names "Subscription_Test_1,Subscription_Test_2,Subscription_Test_Not_Found,Subscription_Test_3" to the subscription REST API "/subscriptions"
     Then get response code of 400

src/functionaltests/resources/features/subscriptionCRUD.feature

@@ -19,27 +19,27 @@
 @tag
 Feature: Test Subscription CRUD  
 
-  @tag1
+  @RESTCreateSubscription
   Scenario: Create subscription with JSON object using REST API by POST method
     Given The REST API "/subscriptions" is up and running
     When  I make a POST request with valid "JSON" to the  subscription REST API "/subscriptions"
     Then  I get response code of 200
 
-  #@tag2
+  @RESTReadSubscription
   Scenario: Read subscription using REST API by GET method
     Given The REST API "/subscriptions" is up and running
     When  I make a GET request with subscription name "Subscription_Test" to the  subscription REST API "/subscriptions/"
     Then  I get response code of 200
     And   Subscription name is "Subscription_Test"
 
-  #@tag3
+  @RESTUpdateSubscription
   Scenario: Update subscription using REST API by PUT method and validate updation
     Given The REST API "/subscriptions" is up and running
     When I make a PUT request with modified notificationType as "MAIL" to REST API "/subscriptions"
     Then I get response code of 200
     And  I can validate modified notificationType "MAIL" with GET request at "/subscriptions/Subscription_Test"
 
-  #@tag4 
+  @RESTDeleteSubscription
   Scenario: Delete subscription using REST API by DELETE method and validate deletion
     Given The REST API "/subscriptions" is up and running
     When  I make a DELETE request with subscription name "Subscription_Test" to the  subscription REST API "/subscriptions/"

src/functionaltests/resources/features/subscriptionRepeatHandler.feature

@@ -19,14 +19,14 @@
 @tag
 Feature: Test Subscription Repeat Handler
 
-  @SubscriptionRepeatHandler
+  @SubscriptionRepeatFalse
   Scenario: Subscription match the Aggragated Object one time
     Given Publish events on Message Bus
     When  In MongoDb RepeatFlagHandler collection the subscription has matched the AggrObjectId
     Then  I make a DELETE request with subscription name "Subscription_Test" to the subscription REST API "/subscriptions/"
     And   Check in MongoDB RepeatFlagHandler collection that the subscription has been removed
 
-  @SubscriptionRepeatHandler
+  @SubscriptionRepeatTrue
   Scenario: Subscription match the Aggragated Object at least two time
     Given Publish events on Message Bus
     When  In MongoDb RepeatFlagHandler collection the subscription has matched the AggrObjectId at least two times