feature(chore):962 fixed tests

eclipse-tractusx · Jun 24, 2024 · 249f3a9 · 249f3a9
1 parent 4cb7852
commit 249f3a9
Show file tree

Hide file tree

Showing 11 changed files with 169 additions and 157 deletions.
diff --git a/tx-cucumber-tests/src/test/resources/features/10_TRACEFOSS-2354.feature b/tx-cucumber-tests/src/test/resources/features/10_TRACEFOSS-2354.feature
@@ -68,14 +68,14 @@ Feature: 👍[BE][TABLE_FEATURE] Implementation of Sorting in table views
 	#Check if *owner filter* in *assets* is working correctly including:
 	#* filter without owner specification returns assets of all owner
 	#* filter for owner specification only return desired assets
-  @TRACEFOSS-1221 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TRACEFOSS-1101 @INTEGRATION_TEST
+	@TRACEFOSS-1221 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TRACEFOSS-1101 @INTEGRATION_TEST
 	Scenario Outline: [BE] Check correct filtering of owner in assets
 		When I am logged into TRACE_X_A application
 		And I request assets with <owner-filter>
 		Then I check, if only assets with <owner-filter> are responded
-
-    Examples:
+		
+		Examples:
 		  | owner-filter |
 		  | "SUPPLIER"   |
 		  | "CUSTOMER"   |
-		  | "OWN"        |
+		  | "OWN"        |
diff --git a/tx-cucumber-tests/src/test/resources/features/11_TRACEFOSS-1125.feature b/tx-cucumber-tests/src/test/resources/features/11_TRACEFOSS-1125.feature
@@ -33,37 +33,37 @@ Feature: ⭐[BE] User select severity for Quality Investigation
 	# * Add new secrets to the code
 	#
 	# 
-  @TRACEFOSS-1220 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @TRACEFOSS-1139 @TRACEFOSS-1138 @INTEGRATION_TEST @[QualityInvestigation]
-  Scenario Outline: [BE] Check correct processing of severity in quality investigation
+	@TRACEFOSS-1220 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @TRACEFOSS-1139 @TRACEFOSS-1138 @INTEGRATION_TEST @[QualityInvestigation]
+	Scenario Outline: [BE] Check correct processing of severity in quality investigation 
 		When I am logged into TRACE_X_A application
 		When I use assets with ids 'urn:uuid:7eeeac86-7b69-444d-81e6-655d0f1513bd'
-    And I create quality notification
+		And I create quality notification
 		  | "severity"    | <severity> |
 		  | "description" | "Testing severity TRACEFOSS-1220" |
-      | "type"        | "INVESTIGATION"                   |
-    Then I check, if quality notification has proper values
+		  | "type"        | "INVESTIGATION"                   |
+		Then I check, if quality notification has proper values
 		  | "severity"    | <severity> |
 		  | "description" | "Testing severity TRACEFOSS-1220" |
 		  | "status"      | "CREATED" |
-    When I approve quality notification
-    Then I check, if quality notification has proper values
+		When I approve quality notification
+		Then I check, if quality notification has proper values
 		  | "status" | "SENT" |
 		When I am logged into TRACE_X_B application
-    Then I check, if quality notification has been received
-    Then I check, if quality notification has proper values
+		Then I check, if quality notification has been received
+		Then I check, if quality notification has proper values
 		  | "severity"    | <severity> |
 		  | "description" | "Testing severity TRACEFOSS-1220" |
 		  | "status"      | "RECEIVED" |
-    When I acknowledge quality notification
-    Then I check, if quality notification has proper values
+		When I acknowledge quality notification
+		Then I check, if quality notification has proper values
 		  | "status" | "ACKNOWLEDGED" |
 		When I am logged into TRACE_X_A application
-    Then I check, if quality notification has proper values
+		Then I check, if quality notification has proper values
 		  | "status" | "ACKNOWLEDGED" |
-
-    Examples:
+		
+		Examples:
 		|severity|
 		|"MINOR"|
 		|"MAJOR"|
 		|"CRITICAL"|
-		|"LIFE-THREATENING"|
+		|"LIFE-THREATENING"|
diff --git a/tx-cucumber-tests/src/test/resources/features/1_TRACEFOSS-1393.feature b/tx-cucumber-tests/src/test/resources/features/1_TRACEFOSS-1393.feature
@@ -1,20 +1,20 @@
 @TRACEFOSS-1393
 Feature: ⭐ [BE][QUALITY_ALERTS] Create (POST) quality alerts (Rest API)
-	#h2. User Story
+	#h2. User Story 
 	#
 	#*As a* user
 	#*I want to* be able to see all quality alerts / notifications based on their status and type with the date created in a separate Quality Alerts inbox
 	#*so that* I can have an overview and perform actions like view details on the notifications.
 	#
-	#h2. Outcome
+	#h2. Outcome 
 	#
 	#- (-) New table is added which shows "Quality Alerts"
 
 	#Check if *edit* of quality notification is processed correctly which contains following checks:
 	# * create notification 
 	# * edit notification in status created
 	# * validate the values have been updated
-  @TRACEFOSS-3354 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-1920 @TRACEFOSS-2910 @TRACEFOSS-1101 @TRACEFOSS-1673 @TEST-904 @TRACEFOSS-2715 @TEST-1217 @INTEGRATION_TEST
+	@TRACEFOSS-3354 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-1920 @TRACEFOSS-2910 @TRACEFOSS-1101 @TRACEFOSS-1673 @TEST-904 @TRACEFOSS-2715 @TEST-1217 @INTEGRATION_TEST
 	Scenario: [BE] Check edit notification of quality notification
 		When I am logged into TRACE_X_A application
 		When I use assets with ids 'urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa02'
@@ -23,40 +23,42 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Create (POST) quality alerts (Rest API)
 		  | "description" | "Testing ACCEPTANCE TRACEFOSS-1864" |
 		  | "type" | "ALERT" |
 		  | "title" | "Initial title" |
+		  | "receiverBpn" | "BPNL00000003CNKC"                  |
 		Then I check, if quality notification has proper values
 		  | "description" | "Testing ACCEPTANCE TRACEFOSS-1864" |
 		  | "status"      | "CREATED" |
-    When I use assets with ids 'urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa03'
+		When I use assets with ids 'urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa03'  
 		When I edit quality notification
 		  | "severity"    | "MINOR" |
 		  | "description" | "Testing ACCEPTANCE TRACEFOSS-1864 edited" |
 		  | "title" | "New Title" |
-
+		  
 		Then I check, if quality notification has proper values
 		  | "status" | "CREATED" |
 		  | "severity"    | "MINOR" |
 		  | "description" | "Testing ACCEPTANCE TRACEFOSS-1864 edited" |
 		  | "title" | "New Title" |
-      | "affectedPartId" | "urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa03" |
+		  | "affectedPartId" | "urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa03" |	
 
 	#Check if *CANCELLATION* of quality alerts is processed correctly which contains following checks:
 	#* correct CANCELLATION on receiver side
 	#* correct reception of status update on sender side
 	#* correct reason on receiver and sender side
-  @TRACEFOSS-1864 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
+	@TRACEFOSS-1864 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
 	Scenario: [BE] Check correct processing of CANCELLATION of quality alerts
 		When I am logged into TRACE_X_A application
 		When I use assets with ids 'urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa02'
 		And I create quality notification
 		  | "severity"    | "MAJOR" |
 		  | "description" | "Testing ACCEPTANCE TRACEFOSS-1864" |
 		  | "type" | "ALERT" |
+		  | "receiverBpn" | "BPNL00000003CNKC"                  |
 		Then I check, if quality notification has proper values
 		  | "description" | "Testing ACCEPTANCE TRACEFOSS-1864" |
 		  | "status"      | "CREATED" |
 		When I cancel quality notification
 		Then I check, if quality notification has proper values
 		  | "status" | "CANCELED" |
-
-    When I am logged into TRACE_X_B application
-		Then I check, if quality notification has not been received
+		  
+		When I am logged into TRACE_X_B application
+		Then I check, if quality notification has not been received
diff --git a/tx-cucumber-tests/src/test/resources/features/2_TRACEFOSS-600.feature b/tx-cucumber-tests/src/test/resources/features/2_TRACEFOSS-600.feature
@@ -33,14 +33,15 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts
 	#* correct CLOSURE on receiver side
 	#* correct reception of status update on sender side
 	#* correct reason on receiver and sender side
-  @TRACEFOSS-1863 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
+	@TRACEFOSS-1863 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
 	Scenario: [BE] Check correct processing of CLOSURE of quality alerts
 		When I am logged into TRACE_X_A application
 		When I use assets with ids 'urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa02'
 		And I create quality notification
 		  | "severity"    | "MAJOR" |
 		  | "description" | "Testing ACCEPTANCE TRACEFOSS-1863" |
 		  | "type" | "ALERT" |
+		  | "receiverBpn" | "BPNL00000003CNKC"                  |
 		Then I check, if quality notification has proper values
 		  | "description" | "Testing ACCEPTANCE TRACEFOSS-1863" |
 		  | "status"      | "CREATED" |
@@ -54,29 +55,30 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts
 		When I acknowledge quality notification
 		Then I check, if quality notification has proper values
 		  | "status" | "ACKNOWLEDGED" |
-
+		  
 		When I am logged into TRACE_X_A application
 		Then I check, if quality notification has proper values
 		  | "status" | "ACKNOWLEDGED" |
-    When I close quality notification
+		When I close quality notification
 		Then I check, if quality notification has proper values
-      | "status" | "CLOSED" |
-
-    When I am logged into TRACE_X_B application
+		  | "status" | "CLOSED" | 
+		  
+		When I am logged into TRACE_X_B application  
 		Then I check, if quality notification has proper values
-      | "status" | "CLOSED" |
+		  | "status" | "CLOSED" |	
 
 	#Check if *bpn names* of *sender and receiver* are processed correctly for created quality alerts which contains following checks:
 	#* correct creation on sender side
 	#* correct reception on receiver side
-  @TRACEFOSS-1547 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-904 @TEST-1217 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
+	@TRACEFOSS-1547 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-904 @TEST-1217 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
 	Scenario: [BE] Check correct processing of bpn names in quality alerts
 		When I am logged into TRACE_X_A application
 		When I use assets with ids 'urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa02'
 		And I create quality notification
 		  | "description" | "Testing BPNs TRACEFOSS-1547" |
 		  | "severity"    | "MINOR" |
 		  | "type"    | "ALERT" |
+		  | "receiverBpn" | "BPNL00000003CNKC"                  |
 		Then I check, if quality notification has proper values
 		  | "description" | "Testing BPNs TRACEFOSS-1547" |
 		  | "createdBy" | "BPNL00000003CML1" |
@@ -91,19 +93,20 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts
 		  | "description" | "Testing BPNs TRACEFOSS-1547" |
 		  | "createdBy" | "BPNL00000003CML1" |
 		  | "sendTo" | "BPNL00000003CNKC" |
-      | "status"      | "RECEIVED"                    |
+		  | "status"      | "RECEIVED" |	
 
 	#Check if *targetDate = null* is processed correctly for created quality alerts which contains following checks:
 	#* correct sending of _targetDate_ = *null*
 	#* correct reception on receiver side
-  @TRACEFOSS-1546 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-904 @TEST-1217 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
+	@TRACEFOSS-1546 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-904 @TEST-1217 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
 	Scenario: [BE] Check correct processing of targetDate = null in quality alerts
 		When I am logged into TRACE_X_A application
 		When I use assets with ids 'urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa02'
 		And I create quality notification
 		  | "severity"    | "MINOR" |
 		  | "description" | "Testing without targetDate TRACEFOSS-1546" |
 		  | "type" | "ALERT" |
+		  | "receiverBpn" | "BPNL00000003CNKC"                  |
 		Then I check, if quality notification has proper values
 		  | "description" | "Testing without targetDate TRACEFOSS-1546" |
 		  | "targetDate"  | "" |
@@ -116,20 +119,21 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts
 		Then I check, if quality notification has proper values
 		  | "description" | "Testing without targetDate TRACEFOSS-1546" |
 		  | "targetDate"  | "" |
-      | "status"      | "RECEIVED"                                  |
+		  | "status"      | "RECEIVED" |	
 
 	#Check if *DECLINATION* of quality alerts is processed correctly which contains following checks:
 	#* correct DECLINATION status on receiver side
 	#* correct reception of status update on sender side
 	#* correct reason on receiver and sender side
-  @TRACEFOSS-1545 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-904 @TEST-1217 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
+	@TRACEFOSS-1545 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-904 @TEST-1217 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
 	Scenario: [BE] Check correct processing of DECLINATION of quality alerts
 		When I am logged into TRACE_X_A application
 		When I use assets with ids 'urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa02'
 		And I create quality notification
 		  | "severity"    | "MAJOR" |
 		  | "description" | "Testing DECLINATION TRACEFOSS-1545" |
 		  | "type" | "ALERT" |
+		  | "receiverBpn" | "BPNL00000003CNKC"                  |
 		Then I check, if quality notification has proper values
 		  | "severity"    | "MAJOR" |
 		  | "description" | "Testing DECLINATION TRACEFOSS-1545" |
@@ -154,20 +158,21 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts
 		Then I check, if quality notification has proper values
 		  | "status" | "DECLINED" |
 		And I check, if quality notification has proper values
-      | "declineReason" | "declined in TRACEFOSS-1545" |
+		  | "declineReason" | "declined in TRACEFOSS-1545" |	
 
 	#Check if *ACCEPTANCE* of quality alerts is processed correctly which contains following checks:
 	#* correct ACCEPTANCE on receiver side
 	#* correct reception of status update on sender side
 	#* correct reason on receiver and sender side
-  @TRACEFOSS-1544 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-904 @TEST-1217 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
+	@TRACEFOSS-1544 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-904 @TEST-1217 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
 	Scenario: [BE] Check correct processing of ACCEPTANCE of quality alerts
 		When I am logged into TRACE_X_A application
 		When I use assets with ids 'urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa02'
 		And I create quality notification
 		  | "severity"    | "MAJOR" |
 		  | "description" | "Testing ACCEPTANCE TRACEFOSS-1544" |
 		  | "type" | "ALERT" |
+		  | "receiverBpn" | "BPNL00000003CNKC"                  |
 		Then I check, if quality notification has proper values
 		  | "severity"    | "MAJOR" |
 		  | "description" | "Testing ACCEPTANCE TRACEFOSS-1544" |
@@ -192,68 +197,69 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts
 		Then I check, if quality notification has proper values
 		  | "status" | "ACCEPTED" |
 		And I check, if quality notification has proper values
-      | "acceptReason" | "accepted in TRACEFOSS-1544" |
+		  | "acceptReason" | "accepted in TRACEFOSS-1544" |	
 
 	#Check if *targetDate* is processed correctly for created quality alerts which contains following checks:
 	#* correct sending of _targetDate_
 	#* correct reception on receiver side
-  @TRACEFOSS-1543 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-904 @TEST-1217 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
-  Scenario: [BE] Check correct processing of targetDate in quality alerts
+	@TRACEFOSS-1543 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-904 @TEST-1217 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
+	Scenario: [BE] Check correct processing of targetDate in quality alerts 
 		When I am logged into TRACE_X_A application
 		When I use assets with ids 'urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa02'
-    And I create quality notification
+		And I create quality notification
 		  | "severity"    | "MINOR" |
 		  | "description" | "Testing targetDate TRACEFOSS-1543" |
 		  | "targetDate"  | "2055-05-30T20:43:06.333827Z" |
-      | "type"        | "ALERT"                             |
-    Then I check, if quality notification has proper values
+		  | "type" | "ALERT" | 
+		Then I check, if quality notification has proper values
 		  | "description" | "Testing targetDate TRACEFOSS-1543" |
 		  | "targetDate"  | "2055-05-30T20:43:06.333827Z" |
 		  | "status"      | "CREATED" |
-    When I approve quality notification
-    Then I check, if quality notification has proper values
+		When I approve quality notification
+		Then I check, if quality notification has proper values
 		  | "status" | "SENT" |
 		When I am logged into TRACE_X_B application
-    Then I check, if quality notification has been received
-    Then I check, if quality notification has proper values
+		Then I check, if quality notification has been received
+		Then I check, if quality notification has proper values
 		  | "description" | "Testing targetDate TRACEFOSS-1543" |
 		  | "targetDate"  | "2055-05-30T20:43:06.333827Z" |
-      | "status"      | "RECEIVED"                          |
+		  | "status"      | "RECEIVED" |	
 
 	#Check if *severity* is processed correctly for created quality alerts which contains following checks:
 	#* correct creation
 	#* correct reception on receiver side
-  @TRACEFOSS-1539 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
-  Scenario Outline: [BE] Check correct processing of severity in quality alerts
+	@TRACEFOSS-1539 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS]
+	Scenario Outline: [BE] Check correct processing of severity in quality alerts 
 		When I am logged into TRACE_X_A application
 		When I use assets with ids 'urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa02'
-    And I create quality notification
+		And I create quality notification
 		  | "severity"    | <severity> |
 		  | "description" | "Testing severity TRACEFOSS-1539" |
-      | "type"        | "ALERT"                           |
-    Then I check, if quality notification has proper values
+		  | "type" | "ALERT" | 
+		  | "receiverBpn" | "BPNL00000003CNKC"                  |
+		Then I check, if quality notification has proper values
 		  | "severity"    | <severity> |
 		  | "description" | "Testing severity TRACEFOSS-1539" |
 		  | "status"      | "CREATED" |
-    When I approve quality notification
-    Then I check, if quality notification has proper values
+		When I approve quality notification
+		Then I check, if quality notification has proper values
 		  | "status" | "SENT" |
 		When I am logged into TRACE_X_B application
-    Then I check, if quality notification has been received
-    Then I check, if quality notification has proper values
+		Then I check, if quality notification has been received
+		Then I check, if quality notification has proper values
 		  | "severity"    | <severity> |
 		  | "description" | "Testing severity TRACEFOSS-1539" |
 		  | "status"      | "RECEIVED" |
-    When I acknowledge quality notification
-    Then I check, if quality notification has proper values
+		When I acknowledge quality notification
+		Then I check, if quality notification has proper values
 		  | "status" | "ACKNOWLEDGED" |
 		When I am logged into TRACE_X_A application
-    Then I check, if quality notification has proper values
+		Then I check, if quality notification has proper values
 		  | "status" | "ACKNOWLEDGED" |
-
-    Examples:
+		
+		Examples:
 		|severity|
 		|"MINOR"|
 		|"MAJOR"|
 		|"CRITICAL"|
-		|"LIFE-THREATENING"|
+		|"LIFE-THREATENING"|