FINERACT-2070: Remove TestRailId annotations

fineract-e2e-tests-runner/src/test/resources/features/BatchApi.feature

@@ -1,12 +1,12 @@
 @BatchApiFeature
 Feature: Batch API
 
-  @TestRailId:C63
+
   Scenario: As a user I would like to run a sample Batch API scenario
     When Batch API sample call ran
     Then Admin checks that all steps result 200OK
 
-  @TestRailId:C2484 @idempotency
+   @idempotency
   Scenario: As admin I would like to verify that idempotency applies correctly in case of BatchAPI call with the same idempotency key on two repayments
     When Batch API call runs with idempotency key
     Then Admin checks that all steps result 200OK for Batch API idempotency request
@@ -16,24 +16,24 @@ Feature: Batch API
     Then Batch API response has the same idempotency key in segment with requestId 6 as in segment with requestId 5
     Then Loan has 1 "REPAYMENT" transactions on Transactions tab after Batch API run
 
-  @TestRailId:C2640
+
   Scenario: Verify Batch API call in case of enclosing transaction is TRUE and all steps result 200OK
     When Batch API call with steps: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "true"
     Then Admin checks that all steps result 200OK
 
-  @TestRailId:C2641
+
   Scenario: Verify Batch API call in case of enclosing transaction is TRUE and one of the steps fails
     When Batch API call with steps: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "true", with failed approve step
     Then Verify that step 3 throws an error with error code 404
     Then Nr. 1 Client creation was rolled back
     Then Nr. 1 Loan creation was rolled back
 
-  @TestRailId:C2642
+
   Scenario: Verify Batch API call in case of enclosing transaction is FALSE and all steps result 200OK
     When Batch API call with steps: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "false"
     Then Admin checks that all steps result 200OK
 
-  @TestRailId:C2643
+
   Scenario: Verify Batch API call in case of enclosing transaction is FALSE, there is only one reference-tree and one of the steps fails
     When Batch API call with steps: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "false", with failed approve step
     Then Verify that step Nr. 1 results 200
@@ -43,12 +43,12 @@ Feature: Batch API
     Then Nr. 1 Client was created
     Then Nr. 1 Loan was created
 
-  @TestRailId:C2644
+
   Scenario: Verify Batch API call in case of enclosing transaction is FALSE, there are two reference-trees and all steps result 200
     When Batch API call with steps done twice: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "false"
     Then Admin checks that all steps result 200OK
 
-  @TestRailId:C2645
+
   Scenario: Verify Batch API call in case of enclosing transaction is FALSE, there are two reference-trees and one of the steps in second tree fails
     When Batch API call with steps done twice: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "false", with failed approve step in second tree
     Then Verify that step Nr. 1 results 200
@@ -65,14 +65,14 @@ Feature: Batch API
     Then Nr. 2 Client was created
     Then Nr. 2 Loan was created
 
-  @TestRailId:C2646
+
   Scenario: Verify Batch API call in case of enclosing transaction is FALSE and one of the steps is doubled
     When Batch API call with steps: createClient, createLoan, approveLoan, getLoanDetails runs with enclosingTransaction: "false", and approveLoan is doubled
     Then Admin checks that all steps result 200OK
     Then Batch API response has no "x-served-from-cache" field in segment with requestId 3
     Then Batch API response has boolean value in header "x-served-from-cache": "true" in segment with requestId 4
 
-  @TestRailId:C2840
+
   Scenario: Verify datatable Batch API calls, when the second request relies on the first response, but the first response is empty
     When A datatable for "Loan" is created
     And Batch API call with steps: queryDatatable, updateDatatable runs, with empty queryDatatable response

fineract-e2e-tests-runner/src/test/resources/features/BusinessDate.feature

@@ -1,27 +1,27 @@
 @BusinessDateFeature
 Feature: BusinessDate
 
-  @TestRailId:C38
+
   Scenario: As a user I would like to enable the Business date configuration
     Given Global configuration "enable_business_date" is enabled
 
-  @TestRailId:C39
+
   Scenario: As a user I would like to disable the Business date configuration
     Given Global configuration "enable_business_date" is disabled
 
-  @TestRailId:C40
+
   Scenario: As a user I would like to set the business date
     When Admin sets the business date to "10 July 2022"
     Then Admin checks that the business date is correctly set to "10 July 2022"
 
-  @TestRailId:C41
+
   Scenario: As a user I would like to change the business date manually
     When Admin sets the business date to "10 July 2022"
     Then Admin checks that the business date is correctly set to "10 July 2022"
     When Admin sets the business date to "11 July 2022"
     Then Admin checks that the business date is correctly set to "11 July 2022"
 
-  @TestRailId:C27
+
   Scenario: As a user I would like to change the business date with scheduled job
     When Admin sets the business date to "10 July 2022"
     When Admin runs the Increase Business Date by 1 day job

fineract-e2e-tests-runner/src/test/resources/features/COB.feature

@@ -1,7 +1,7 @@
 @COBFeature
 Feature: COBFeature
 
-  @TestRailId:C2501 @Skip
+   @Skip
   Scenario: As an admin I would like to see that last closed business date got updated after COB catch up job finished
     When Admin sets the business date to "01 January 2022"
     When Admin creates a client with random data
@@ -22,7 +22,7 @@ Feature: COBFeature
     Then Loan status will be "CLOSED_OBLIGATIONS_MET"
 
 
-  @TestRailId:C2681 @Skip
+   @Skip
   Scenario: As an admin I would like to check that the Delinquency bucket set on the loan correctly when the arrears setting is 3 on the product
     When Admin sets the business date to "1 January 2022"
     When Admin creates a client with random data
@@ -33,7 +33,7 @@ Feature: COBFeature
     When Admin runs COB job
     Then Admin checks that delinquency range is: "RANGE_1" and has delinquentDate "2022-02-03"
 
-  @TestRailId:C2791 @Skip
+   @Skip
   Scenario: Verify that COB processes loans which are not closed/overpaid and has a last_closed_business_date exactly 1 day behind COB date
     When Admin sets the business date to "01 July 2023"
     When Admin creates a client with random data
@@ -49,7 +49,7 @@ Feature: COBFeature
     When Admin runs COB job
     Then Admin checks that last closed business date of loan is "02 July 2023"
 
-  @TestRailId:C2792
+
   Scenario: Verify that COB doesn’t touch loans with last closed business date behind COB date
     When Admin sets the business date to "01 July 2023"
     When Admin creates a client with random data
@@ -74,7 +74,7 @@ Feature: COBFeature
       | RANGE_3                | 09 August 2023 |                |
       | RANGE_1                | 04 August 2023 | 09 August 2023 |
 
-  @TestRailId:C2793
+
   Scenario: Verify that COB doesn’t touch CLOSED loans
     When Admin sets the business date to "01 July 2023"
     When Admin creates a client with random data
@@ -106,7 +106,7 @@ Feature: COBFeature
       | RANGE_3                | 09 August 2023 | 10 August 2023 |
       | RANGE_1                | 04 August 2023 | 09 August 2023 |
 
-  @TestRailId:C2794
+
   Scenario: Verify that COB doesn’t touch OVERPAID loans
     When Admin sets the business date to "01 July 2023"
     When Admin creates a client with random data
@@ -138,7 +138,7 @@ Feature: COBFeature
       | RANGE_3                | 09 August 2023 | 10 August 2023 |
       | RANGE_1                | 04 August 2023 | 09 August 2023 |
 
-  @TestRailId:C2795 @Skip
+   @Skip
   Scenario: Verify that COB catch up runs properly on loan which is behind date because of locked with error
     When Admin sets the business date to "01 January 2022"
     When Admin creates a client with random data
@@ -161,7 +161,7 @@ Feature: COBFeature
     And Customer makes "AUTOPAY" repayment on "05 January 2022" with 1000 EUR transaction amount
     Then Loan status will be "CLOSED_OBLIGATIONS_MET"
 
-  @TestRailId:C2796
+
   Scenario: Verify that after COB runs there are no unreleased loan locks
     When Admin sets the business date to "01 July 2023"
     When Admin creates a client with random data
@@ -174,7 +174,7 @@ Feature: COBFeature
     When Admin runs COB job
     Then The loan account is not locked
 
-  @TestRailId:C2797 @Skip
+   @Skip
   Scenario: Verify that Inline COB is executed for stuck loans - when payment happened on a loan with last closed business date in the past, COB got executed before the repayment
     When Admin sets the business date to "01 July 2023"
     When Admin creates a client with random data
@@ -194,7 +194,7 @@ Feature: COBFeature
 
 #  On a hard locked loan, in case of the lock has an error message, payment by a non-bypass user should trigger inlineCob and it should be executed
 #  this functionality is not implemented yet
-  @Skip @TestRailId:C2798
+  @Skip
   Scenario: Verify that Inline COB is executed for stuck loans - when payment happened on a locked loan COB got executed before the repayment
     When Admin sets the business date to "01 July 2023"
     When Admin creates a client with random data
@@ -213,7 +213,7 @@ Feature: COBFeature
     When Created user makes externalID controlled "AUTOPAY" repayment on "04 July 2023" with 500 EUR transaction amount
     Then Admin checks that last closed business date of loan is "03 July 2023"
 
-  @TestRailId:C3044 @AdvancedPaymentAllocation
+   @AdvancedPaymentAllocation
   Scenario: Verify that LoanAccountCustomSnapshotBusinessEvent is created with proper business date when installment is due date and COB runs
     Given Admin puts CHECK_DUE_INSTALLMENTS job into LOAN_CLOSE_OF_BUSINESS workflow
     When Admin sets the business date to "01 January 2024"

fineract-e2e-tests-runner/src/test/resources/features/Client.feature

@@ -20,19 +20,19 @@
 @ClientFeature
 Feature: Client
 
-  @TestRailId:C14 @Smoke
+   @Smoke
   Scenario Outline: Client creation functionality for Fineract
     When Admin creates a client with Firstname <firstName> and Lastname <lastName>
     Then Client is created successfully
     Examples:
       | firstName    | lastName |
       | "FirstName1" | "Test1"  |
 
-  @TestRailId:C15
+
   Scenario Outline: Client creation with address functionality for Fineract
     When Global configuration "Enable-Address" is enabled
     When Admin creates a client with Firstname <firstName> and Lastname <lastName> with address
     Then Client is created successfully
     Examples:
       | firstName    | lastName |
-      | "FirstName2" | "Test2"  |
+      | "FirstName2" | "Test2"  |

fineract-e2e-tests-runner/src/test/resources/features/InlineCOB.feature

@@ -1,7 +1,7 @@
 @InlineCOBFeature
 Feature: InlineCOBFeature
 
-  @TestRailId:C2457
+
   Scenario: As an admin I would like to see that inline COB Happy Path scenario is working properly
     When Admin sets the business date to "1 January 2022"
     When Admin creates a client with random data
@@ -12,7 +12,7 @@ Feature: InlineCOBFeature
     When Admin runs inline COB job for Loan
     Then Admin checks that delinquency range is: "RANGE_3" and has delinquentDate "2022-02-03"
 
-  @TestRailId:C2473
+
   Scenario: As an admin I would like to see that loan was catching up with inline COB
     When Admin sets the business date to "1 January 2022"
     When Admin creates a client with random data
@@ -27,7 +27,7 @@ Feature: InlineCOBFeature
     When Admin runs inline COB job for Loan
     Then Admin checks that last closed business date of loan is "04 January 2022"
 
-  @TestRailId:C2554
+
   Scenario: As an admin I would like to see that loan was catching up with inline COB on a repayment
     When Admin sets the business date to "1 January 2022"
     When Admin creates a client with random data
@@ -44,7 +44,7 @@ Feature: InlineCOBFeature
     And Created user makes "AUTOPAY" repayment on "5 January 2022" with 100 EUR transaction amount
     Then Admin checks that last closed business date of loan is "04 January 2022"
 
-  @TestRailId:C2602
+
   Scenario: Verify that LoanCOBApiFilter works fine in the background and loanId controlled transaction does not trigger inlineCOB if COB had not been applied on loan before
     When Admin sets the business date to "01 January 2023"
     When Admin creates a client with random data
@@ -67,7 +67,7 @@ Feature: InlineCOBFeature
       | RANGE_1                | 06 January 2023 | 07 January 2023 |
     Then Admin checks that last closed business date of loan is "null"
 
-  @TestRailId:C2603
+
   Scenario: Verify that LoanCOBApiFilter works fine in the background and externalId controlled transaction does not trigger inlineCOB if COB had not been applied on loan before
     When Admin sets the business date to "01 January 2023"
     When Admin creates a client with random data
@@ -90,7 +90,7 @@ Feature: InlineCOBFeature
       | RANGE_1                | 06 January 2023 | 07 January 2023 |
     Then Admin checks that last closed business date of loan is "null"
 
-  @TestRailId:C2604
+
   Scenario: Verify that LoanCOBApiFilter works fine in the background and loanId controlled transaction triggers inlineCOB if COB had been applied on loan before
     When Admin sets the business date to "01 January 2023"
     When Admin creates a client with random data
@@ -116,7 +116,7 @@ Feature: InlineCOBFeature
       | RANGE_1                | 06 January 2023 | 07 January 2023 |
     Then Admin checks that last closed business date of loan is "06 January 2023"
 
-  @TestRailId:C2605
+
   Scenario: Verify that LoanCOBApiFilter works fine in the background and externalId controlled transaction triggers inlineCOB if COB had been applied on loan before
     When Admin sets the business date to "01 January 2023"
     When Admin creates a client with random data