Revert "chore: TRACEFOSS-XXX remove feature files."

This reverts commit 9a31a7d.
catenax-ng · Sep 19, 2023 · 4aa5296 · 4aa5296
1 parent 09a13fa
commit 4aa5296
Show file tree

Hide file tree

Showing 10 changed files with 1,194 additions and 0 deletions.
diff --git a/tx-cucumber-tests/src/test/resources/features/10_TRACEFOSS-1125.feature b/tx-cucumber-tests/src/test/resources/features/10_TRACEFOSS-1125.feature
@@ -0,0 +1,67 @@
+@TRACEFOSS-1125
+Feature: ⭐[BE] User select severity for Quality Investigation
+	#*As a* User,
+	#*I want* to be able to assign a severity status for the part(s) of a notification
+	#*so that* I am able to inform the supplier (within the notification) about the criticality of my request for investigation.
+	#h3. Outcome
+	# * User can select the severity based on the list in the documentation
+	# ** MINOR
+	# ** MAJOR
+	# ** CRITICAL
+	# ** LIFE-THREATENING
+	# * Severity is sent to the receiver of the notification in the corresponding field
+	# * The severity of the parts is changed on sender and receiver side based on the information in the notification.
+	#
+	#h2. Hints
+	# * Today severity is hard coded "minor" in Notification
+	# * [Concept|https://confluence.catena-x.net/pages/viewpage.action?pageId=69429778]
+
+	#Check if *severity* is processed correctly for created quality investigations which contains following checks:
+	# * correct creation
+	# * correct reception on receiver side
+	#
+	#h2. Sprint Planning 2
+	# * Make sure to not have duplicate lines of gherkin language which link to the same technical methods
+	# * Write test
+	# * Validate github action against e2e environment
+	# * Give Feedback to Alex and make suggestions of gherkin and technical steps
+	# * Request two new technical users (see reference ticket here: https://jira.catena-x.net/browse/CPLP-2808)  with client id / secret for
+	# ** ADMIN role
+	# ** USER role
+	# * Request system team ticket (see reference ticket here: [https://github.com/eclipse-tractusx/sig-infra/issues/66) |https://github.com/eclipse-tractusx/sig-infra/issues/66]
+	# ** For the mapping of the secrets in github
+	# * Add new secrets to the code
+	#
+	# 
+  @TRACEFOSS-1220 @TRACEFOSS-1920 @TEST-1217 @TRACEFOSS-1138 @TRACEFOSS-1139 @TRACEFOSS-1101 @TRACEFOSS-1673 @TEST-904 @INTEGRATION_TEST
+  Scenario Outline: [BE] Check correct processing of severity in quality investigation
+    When I am logged into TRACE_X_A application
+    And I create quality investigation
+      | "severity"    | <severity>                        |
+      | "description" | "Testing severity TRACEFOSS-1220" |
+    Then I check, if quality investigation has proper values
+      | "severity"    | <severity>                        |
+      | "description" | "Testing severity TRACEFOSS-1220" |
+      | "status"      | "CREATED"                         |
+    When I approve quality investigation
+    Then I check, if quality investigation has proper values
+      | "status" | "SENT" |
+    When I am logged into TRACE_X_B application
+    Then I check, if quality investigation has been received
+    Then I check, if quality investigation has proper values
+      | "severity"    | <severity>                        |
+      | "description" | "Testing severity TRACEFOSS-1220" |
+      | "status"      | "RECEIVED"                        |
+    When I acknowledge quality investigation
+    Then I check, if quality investigation has proper values
+      | "status" | "ACKNOWLEDGED" |
+    When I am logged into TRACE_X_A application
+    Then I check, if quality investigation has proper values
+      | "status" | "ACKNOWLEDGED" |
+
+    Examples:
+      | severity           |
+      | "MINOR"            |
+      | "MAJOR"            |
+      | "CRITICAL"         |
+      | "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
@@ -0,0 +1,277 @@
+@TRACEFOSS-1393
+Feature: ⭐ [BE][QUALITY_ALERTS] Create (POST) quality alerts (Rest API)
+	#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
+	#
+	#- (-) New table is added which shows "Quality Alerts"
+
+	#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-1920 @TEST-1217 @TEST-904 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST
+  Scenario: [BE] Check correct processing of CANCELLATION of quality alerts
+    When I am logged into TRACE_X_A application
+    And I create quality alert
+      | "severity"    | "MAJOR"                             |
+      | "description" | "Testing ACCEPTANCE TRACEFOSS-1864" |
+    Then I check, if quality alert has proper values
+      | "description" | "Testing ACCEPTANCE TRACEFOSS-1864" |
+      | "status"      | "CREATED"                           |
+    When I cancel quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "CANCELED" |
+
+    When I am logged into TRACE_X_B application
+    Then I check, if quality alert has not been received
+
+	#Check if *CLOSURE* of quality alerts is processed correctly which contains following checks:
+	#* correct CLOSURE on receiver side
+	#* correct reception of status update on sender side
+	#* correct reason on receiver and sender side
+  @TRACEFOSS-1863 @TRACEFOSS-1920 @TEST-1217 @TEST-904 @TRACEFOSS-1101 @TRACEFOSS-1673 @INTEGRATION_TEST
+  Scenario: [BE] Check correct processing of CLOSURE of quality alerts
+    When I am logged into TRACE_X_A application
+    And I create quality alert
+      | "severity"    | "MAJOR"                             |
+      | "description" | "Testing ACCEPTANCE TRACEFOSS-1863" |
+    Then I check, if quality alert has proper values
+      | "description" | "Testing ACCEPTANCE TRACEFOSS-1863" |
+      | "status"      | "CREATED"                           |
+    When I approve quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "SENT" |
+    When I am logged into TRACE_X_B application
+    Then I check, if quality alert has been received
+    And I check, if quality alert has proper values
+      | "status" | "RECEIVED" |
+    When I acknowledge quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "ACKNOWLEDGED" |
+
+    When I am logged into TRACE_X_A application
+    Then I check, if quality alert has proper values
+      | "status" | "ACKNOWLEDGED" |
+    When I close quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "CLOSED" |
+
+    When I am logged into TRACE_X_B application
+    Then I check, if quality alert has proper values
+      | "status" | "CLOSED" |
+
+	#Check if *several parts* are processed correctly in *one* created quality alert which contains following checks:
+	#* correct sending of several parts in *one* alert
+	#* correct reception of several parts in *one* alert on receiver side
+	#* correct update of *one* alert with several parts
+  @TRACEFOSS-1670 @TRACEFOSS-1920 @TRACEFOSS-1101 @TRACEFOSS-1673 @TEST-904 @TEST-1217 @INTEGRATION_TEST
+  Scenario: [BE] Check correct processing of several parts in quality alerts
+    When I am logged into TRACE_X_A application
+    And I create quality alert with two parts
+      | "severity"    | "MINOR"                           |
+      | "description" | "Testing severity TRACEFOSS-1670" |
+    Then I check, if quality alert has proper values
+      | "description"  | "Testing severity TRACEFOSS-1670" |
+      | "status"       | "CREATED"                         |
+      | "assetIdCount" | "2"                               |
+    When I approve quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "SENT" |
+    When I am logged into TRACE_X_B application
+    Then I check, if quality alert has been received
+    Then I check, if quality alert has proper values
+      | "description"  | "Testing severity TRACEFOSS-1670" |
+      | "status"       | "RECEIVED"                        |
+      | "assetIdCount" | "2"                               |
+    When I acknowledge quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "ACKNOWLEDGED" |
+    When I am logged into TRACE_X_A application
+    Then I check, if quality alert has proper values
+      | "status"       | "ACKNOWLEDGED" |
+      | "assetIdCount" | "2"            |
+
+	#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-1101 @TRACEFOSS-1920 @TRACEFOSS-1673 @TEST-904 @TEST-1217 @INTEGRATION_TEST
+  Scenario: [BE] Check correct processing of bpn names in quality alerts
+    When I am logged into TRACE_X_A application
+    And I create quality alert
+      | "description" | "Testing BPNs TRACEFOSS-1547" |
+      | "severity"    | "MINOR"                       |
+    Then I check, if quality alert has proper values
+      | "description" | "Testing BPNs TRACEFOSS-1547" |
+      | "createdBy"   | "BPNL00000003CML1"            |
+      | "sendTo"      | "BPNL00000003CNKC"            |
+      | "status"      | "CREATED"                     |
+    When I approve quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "SENT" |
+    When I am logged into TRACE_X_B application
+    Then I check, if quality alert has been received
+    Then I check, if quality alert has proper values
+      | "description" | "Testing BPNs TRACEFOSS-1547" |
+      | "createdBy"   | "BPNL00000003CML1"            |
+      | "sendTo"      | "BPNL00000003CNKC"            |
+      | "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-1101 @TRACEFOSS-1920 @TRACEFOSS-1673 @TEST-904 @TEST-1217 @INTEGRATION_TEST
+  Scenario: [BE] Check correct processing of targetDate = null in quality alerts
+    When I am logged into TRACE_X_A application
+    And I create quality alert
+      | "severity"    | "MINOR"                                     |
+      | "description" | "Testing without targetDate TRACEFOSS-1546" |
+    Then I check, if quality alert has proper values
+      | "description" | "Testing without targetDate TRACEFOSS-1546" |
+      | "targetDate"  | ""                                          |
+      | "status"      | "CREATED"                                   |
+    When I approve quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "SENT" |
+    When I am logged into TRACE_X_B application
+    Then I check, if quality alert has been received
+    Then I check, if quality alert has proper values
+      | "description" | "Testing without targetDate TRACEFOSS-1546" |
+      | "targetDate"  | ""                                          |
+      | "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-1101 @TRACEFOSS-1920 @TRACEFOSS-1673 @TEST-904 @TEST-1217 @INTEGRATION_TEST
+  Scenario: [BE] Check correct processing of DECLINATION of quality alerts
+    When I am logged into TRACE_X_A application
+    And I create quality alert
+      | "severity"    | "MAJOR"                              |
+      | "description" | "Testing DECLINATION TRACEFOSS-1545" |
+    Then I check, if quality alert has proper values
+      | "severity"    | "MAJOR"                              |
+      | "description" | "Testing DECLINATION TRACEFOSS-1545" |
+      | "status"      | "CREATED"                            |
+    When I approve quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "SENT" |
+    When I am logged into TRACE_X_B application
+    Then I check, if quality alert has been received
+    Then I check, if quality alert has proper values
+      | "severity"    | "MAJOR"                              |
+      | "description" | "Testing DECLINATION TRACEFOSS-1545" |
+      | "status"      | "RECEIVED"                           |
+    When I acknowledge quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "ACKNOWLEDGED" |
+    When I decline quality alert
+      | "reason" | "declined in TRACEFOSS-1545" |
+    Then I check, if quality alert has proper values
+      | "status" | "DECLINED" |
+    When I am logged into TRACE_X_A application
+    Then I check, if quality alert has proper values
+      | "status" | "DECLINED" |
+    And I check, if quality alert has proper values
+      | "description" | "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-1101 @TRACEFOSS-1920 @TEST-904 @TRACEFOSS-1673 @TEST-1217 @INTEGRATION_TEST
+  Scenario: [BE] Check correct processing of ACCEPTANCE of quality alerts
+    When I am logged into TRACE_X_A application
+    And I create quality alert
+      | "severity"    | "MAJOR"                             |
+      | "description" | "Testing ACCEPTANCE TRACEFOSS-1544" |
+    Then I check, if quality alert has proper values
+      | "severity"    | "MAJOR"                             |
+      | "description" | "Testing ACCEPTANCE TRACEFOSS-1544" |
+      | "status"      | "CREATED"                           |
+    When I approve quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "SENT" |
+    When I am logged into TRACE_X_B application
+    Then I check, if quality alert has been received
+    Then I check, if quality alert has proper values
+      | "severity"    | "MAJOR"                             |
+      | "description" | "Testing ACCEPTANCE TRACEFOSS-1544" |
+      | "status"      | "RECEIVED"                          |
+    When I acknowledge quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "ACKNOWLEDGED" |
+    When I accept quality alert
+      | "reason" | "accepted in TRACEFOSS-1544" |
+    Then I check, if quality alert has proper values
+      | "status" | "ACCEPTED" |
+    When I am logged into TRACE_X_A application
+    Then I check, if quality alert has proper values
+      | "status" | "ACCEPTED" |
+    And I check, if quality alert has proper values
+      | "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-1920 @TEST-904 @TRACEFOSS-1673 @TRACEFOSS-1101 @TEST-1217 @INTEGRATION_TEST
+  Scenario: [BE] Check correct processing of targetDate in quality alerts
+    When I am logged into TRACE_X_A application
+    And I create quality alert
+      | "severity"    | "MINOR"                             |
+      | "description" | "Testing targetDate TRACEFOSS-1543" |
+      | "targetDate"  | "2055-05-30T20:43:06.333827Z"       |
+    Then I check, if quality alert has proper values
+      | "description" | "Testing targetDate TRACEFOSS-1543" |
+      | "targetDate"  | "2055-05-30T20:43:06.333827Z"       |
+      | "status"      | "CREATED"                           |
+    When I approve quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "SENT" |
+    When I am logged into TRACE_X_B application
+    Then I check, if quality alert has been received
+    Then I check, if quality alert has proper values
+      | "description" | "Testing targetDate TRACEFOSS-1543" |
+      | "targetDate"  | "2055-05-30T20:43:06.333827Z"       |
+      | "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-1920 @TRACEFOSS-1101 @TRACEFOSS-1673 @TEST-904 @TEST-1217 @INTEGRATION_TEST
+  Scenario Outline: [BE] Check correct processing of severity in quality alerts
+    When I am logged into TRACE_X_A application
+    And I create quality alert
+      | "severity"    | <severity>                        |
+      | "description" | "Testing severity TRACEFOSS-1539" |
+    Then I check, if quality alert has proper values
+      | "severity"    | <severity>                        |
+      | "description" | "Testing severity TRACEFOSS-1539" |
+      | "status"      | "CREATED"                         |
+    When I approve quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "SENT" |
+    When I am logged into TRACE_X_B application
+    Then I check, if quality alert has been received
+    Then I check, if quality alert has proper values
+      | "severity"    | <severity>                        |
+      | "description" | "Testing severity TRACEFOSS-1539" |
+      | "status"      | "RECEIVED"                        |
+    When I acknowledge quality alert
+    Then I check, if quality alert has proper values
+      | "status" | "ACKNOWLEDGED" |
+    When I am logged into TRACE_X_A application
+    Then I check, if quality alert has proper values
+      | "status" | "ACKNOWLEDGED" |
+
+    Examples:
+      | severity           |
+      | "MINOR"            |
+      | "MAJOR"            |
+      | "CRITICAL"         |
+      | "LIFE-THREATENING" |