From 4cb78524429db7f2d891f97be571c803d4e55254 Mon Sep 17 00:00:00 2001 From: Maximilian Wesener Date: Mon, 24 Jun 2024 08:16:43 +0200 Subject: [PATCH 1/4] feature(chore):962 fixed nullpointer --- .../infrastructure/notification/model/NotificationEntity.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tx-backend/src/main/java/org/eclipse/tractusx/traceability/notification/infrastructure/notification/model/NotificationEntity.java b/tx-backend/src/main/java/org/eclipse/tractusx/traceability/notification/infrastructure/notification/model/NotificationEntity.java index 4163e2f035..2bfe6756f3 100644 --- a/tx-backend/src/main/java/org/eclipse/tractusx/traceability/notification/infrastructure/notification/model/NotificationEntity.java +++ b/tx-backend/src/main/java/org/eclipse/tractusx/traceability/notification/infrastructure/notification/model/NotificationEntity.java @@ -98,7 +98,7 @@ public static Notification toDomain(NotificationEntity notificationEntity) { .targetDate(convertInstantToString(notificationEntity.getTargetDate())) .severity(NotificationSeverity.fromString(notificationEntity.getSeverity() != null ? notificationEntity.getSeverity().getRealName() : null)) .notifications(messages) - .initialReceiverBpns(List.of()) + .initialReceiverBpns(List.of(initialReceiverBpn)) .build(); } From 249f3a92bbe8c508c9979717a89811dcef4353d6 Mon Sep 17 00:00:00 2001 From: Maximilian Wesener Date: Mon, 24 Jun 2024 08:23:12 +0200 Subject: [PATCH 2/4] feature(chore):962 fixed tests --- .../features/10_TRACEFOSS-2354.feature | 8 +- .../features/11_TRACEFOSS-1125.feature | 30 +++---- .../features/1_TRACEFOSS-1393.feature | 22 ++--- .../features/2_TRACEFOSS-600.feature | 86 ++++++++++--------- .../features/3_TRACEFOSS-938.feature | 8 +- .../features/4_TRACEFOSS-936.feature | 40 +++++---- .../features/5_TRACEFOSS-1625.feature | 7 +- .../features/6_TRACEFOSS-382.feature | 22 ++--- .../features/7_TRACEFOSS-1090.feature | 30 +++---- .../features/8_TRACEFOSS-608.feature | 42 ++++----- .../features/9_TRACEFOSS-607.feature | 31 +++---- 11 files changed, 169 insertions(+), 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 index fcf234244d..b4cb1dc9a9 100644 --- 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 Then I check, if only assets with are responded - - Examples: + + Examples: | owner-filter | | "SUPPLIER" | | "CUSTOMER" | - | "OWN" | + | "OWN" | \ No newline at end of file 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 index 2a181f8266..99c359e636 100644 --- 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" | | | "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" | | | "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" | | | "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"| \ No newline at end of file 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 index 2afe7b857d..cc0f44d4b0 100644 --- 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,12 +1,12 @@ @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" @@ -14,7 +14,7 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Create (POST) quality alerts (Rest API) # * 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,27 +23,28 @@ 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' @@ -51,12 +52,13 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Create (POST) quality alerts (Rest API) | "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 \ No newline at end of file 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 index 3009823690..82ac27ff46 100644 --- 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,7 +33,7 @@ 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' @@ -41,6 +41,7 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts | "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,22 +55,22 @@ 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' @@ -77,6 +78,7 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts | "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,12 +93,12 @@ 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' @@ -104,6 +106,7 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts | "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,13 +119,13 @@ 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' @@ -130,6 +133,7 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts | "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,13 +158,13 @@ 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' @@ -168,6 +172,7 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts | "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" | | | "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" | | | "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" | | | "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"| \ No newline at end of file diff --git a/tx-cucumber-tests/src/test/resources/features/3_TRACEFOSS-938.feature b/tx-cucumber-tests/src/test/resources/features/3_TRACEFOSS-938.feature index bf2d377e28..a13e02e74b 100644 --- a/tx-cucumber-tests/src/test/resources/features/3_TRACEFOSS-938.feature +++ b/tx-cucumber-tests/src/test/resources/features/3_TRACEFOSS-938.feature @@ -35,14 +35,14 @@ Feature: ⭐[TEST] Update Quality Investigation (over EDC) #* correct CANCELLATION on receiver side #* correct reception of status update on sender side #* correct reason on receiver and sender side - @TRACEFOSS-1862 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QualityInvestigation] - Scenario: [BE] Check correct processing of CANCELLATION of quality notification + @TRACEFOSS-1862 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QualityInvestigation] + Scenario: [BE] Check correct processing of CANCELLATION of quality notification 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 | "severity" | "MAJOR" | | "description" | "Testing ACCEPTANCE TRACEFOSS-1862" | - | "type" | "INVESTIGATION" | + | "type" | "INVESTIGATION" | Then I check, if quality notification has proper values | "description" | "Testing ACCEPTANCE TRACEFOSS-1862" | | "status" | "CREATED" | @@ -50,4 +50,4 @@ Feature: ⭐[TEST] Update Quality Investigation (over EDC) 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 + Then I check, if quality notification has not been received \ No newline at end of file diff --git a/tx-cucumber-tests/src/test/resources/features/4_TRACEFOSS-936.feature b/tx-cucumber-tests/src/test/resources/features/4_TRACEFOSS-936.feature index 242d83cf37..3db4edc08f 100644 --- a/tx-cucumber-tests/src/test/resources/features/4_TRACEFOSS-936.feature +++ b/tx-cucumber-tests/src/test/resources/features/4_TRACEFOSS-936.feature @@ -24,15 +24,16 @@ Feature: ⭐[BE] Include reason for receiver and sender investigations #* correct CLOSE on receiver side #* correct reception of status update on sender side #* correct reason on receiver and sender side - @TRACEFOSS-1861 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QualityInvestigation] - Scenario: [BE] Check correct processing of CLOSURE of quality investigation + @TRACEFOSS-1861 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QualityInvestigation] + Scenario: [BE] Check correct processing of CLOSURE of 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 | "severity" | "MAJOR" | | "description" | "Testing CLOSURE TRACEFOSS-1861" | | "type" | "INVESTIGATION" | - Then I check, if quality notification has proper values + | "receiverBpn" | "BPNL00000003CNKC" | + Then I check, if quality notification has proper values | "description" | "Testing CLOSURE TRACEFOSS-1861" | | "status" | "CREATED" | When I approve quality notification @@ -50,46 +51,47 @@ Feature: ⭐[BE] Include reason for receiver and sender investigations Then I check, if quality notification has proper values | "status" | "ACKNOWLEDGED" | When I close quality notification - Then I check, if quality notification has proper values + Then I check, if quality notification has proper values | "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 *ACCEPTANCE* of quality investigations 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-1222 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1139 @TRACEFOSS-1138 @TRACEFOSS-1101 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-1217 @TEST-904 @TRACEFOSS-3128 @TRACEFOSS-3373 @INTEGRATION_TEST @[QualityInvestigation] - Scenario: [BE] Check correct processing of ACCEPTANCE of quality investigation + @TRACEFOSS-1222 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1139 @TRACEFOSS-1138 @TRACEFOSS-1101 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-1217 @TEST-904 @TRACEFOSS-3128 @TRACEFOSS-3373 @INTEGRATION_TEST @[QualityInvestigation] + Scenario: [BE] Check correct processing of ACCEPTANCE of 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" | "MAJOR" | | "description" | "Testing ACCEPTANCE TRACEFOSS-1222" | - | "type" | "INVESTIGATION" | - Then I check, if quality notification has proper values + | "type" | "INVESTIGATION" | + | "receiverBpn" | "BPNL00000003CNKC" | + Then I check, if quality notification has proper values | "severity" | "MAJOR" | | "description" | "Testing ACCEPTANCE TRACEFOSS-1222" | | "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" | "MAJOR" | | "description" | "Testing ACCEPTANCE TRACEFOSS-1222" | | "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 accept quality notification + When I accept quality notification | "reason" | "accepted in TRACEFOSS-1222" | - Then I check, if quality notification has proper values + Then I check, if quality notification has proper values | "status" | "ACCEPTED" | 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" | "ACCEPTED" | | "acceptReason" | "accepted in TRACEFOSS-1222" | diff --git a/tx-cucumber-tests/src/test/resources/features/5_TRACEFOSS-1625.feature b/tx-cucumber-tests/src/test/resources/features/5_TRACEFOSS-1625.feature index ac2d2a9404..1f90a5a94e 100644 --- a/tx-cucumber-tests/src/test/resources/features/5_TRACEFOSS-1625.feature +++ b/tx-cucumber-tests/src/test/resources/features/5_TRACEFOSS-1625.feature @@ -18,14 +18,15 @@ Feature: [BE][FE]Handling of several parts in one quality alert #* 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-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-904 @TEST-1217 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QUALITY_ALERTS] + @TRACEFOSS-1670 @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 several parts in quality alerts When I am logged into TRACE_X_A application When I use assets with ids 'urn:uuid:6b2296cc-26c0-4f38-8a22-092338c36e22,urn:uuid:1be6ec59-40fb-4993-9836-acb0e284fa02' And I create quality notification | "severity" | "MINOR" | - | "description" | "Testing severity TRACEFOSS-1670" | + | "description" | "Testing severity TRACEFOSS-1670" | | "type" | "ALERT" | + | "receiverBpn" | "BPNL00000003CNKC" | Then I check, if quality notification has proper values | "description" | "Testing severity TRACEFOSS-1670" | | "status" | "CREATED" | @@ -45,4 +46,4 @@ Feature: [BE][FE]Handling of several parts in one quality alert When I am logged into TRACE_X_A application Then I check, if quality notification has proper values | "status" | "ACKNOWLEDGED" | - | "assetIdCount" | "2" | + | "assetIdCount" | "2" | \ No newline at end of file diff --git a/tx-cucumber-tests/src/test/resources/features/6_TRACEFOSS-382.feature b/tx-cucumber-tests/src/test/resources/features/6_TRACEFOSS-382.feature index abe13d8071..26b0e65acc 100644 --- a/tx-cucumber-tests/src/test/resources/features/6_TRACEFOSS-382.feature +++ b/tx-cucumber-tests/src/test/resources/features/6_TRACEFOSS-382.feature @@ -1,13 +1,13 @@ @TRACEFOSS-382 Feature: Create Request for quality investigation / store in queue - #h2. Remarks - #* (-) Test the solution - #* (-) Provide test data - #* (-) TRACEFOSS-392 - #* (-) TRACEFOSS-384 - #* (-) - # - #h2. User story + #h2. Remarks + #* (-) Test the solution + #* (-) Provide test data + #* (-) TRACEFOSS-392 + #* (-) TRACEFOSS-384 + #* (-) + # + #h2. User story #As a user # #I want to be able to create a quality investigation for selected parts with a description of the defect @@ -31,8 +31,8 @@ Feature: Create Request for quality investigation / store in queue #* correct sending of several parts in *one* investigation #* correct reception of several parts in *one* investigation on receiver side #* correct update of *one* investigation with several parts - @TRACEFOSS-1652 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TRACEFOSS-1101 @INTEGRATION_TEST @[QualityInvestigation] - Scenario: [BE] Check correct processing of several parts in quality investigation + @TRACEFOSS-1652 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TRACEFOSS-2715 @TRACEFOSS-1101 @INTEGRATION_TEST @[QualityInvestigation] + Scenario: [BE] Check correct processing of several parts 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,urn:uuid:5205f736-8fc2-4585-b869-6bf36842369a' And I create quality notification @@ -58,4 +58,4 @@ Feature: Create Request for quality investigation / store in queue When I am logged into TRACE_X_A application Then I check, if quality notification has proper values | "status" | "ACKNOWLEDGED" | - | "assetIdCount" | "2" | + | "assetIdCount" | "2" | \ No newline at end of file diff --git a/tx-cucumber-tests/src/test/resources/features/7_TRACEFOSS-1090.feature b/tx-cucumber-tests/src/test/resources/features/7_TRACEFOSS-1090.feature index e993130f92..b2d7afc365 100644 --- a/tx-cucumber-tests/src/test/resources/features/7_TRACEFOSS-1090.feature +++ b/tx-cucumber-tests/src/test/resources/features/7_TRACEFOSS-1090.feature @@ -10,36 +10,36 @@ Feature: 🪓⭐[BE] Add information to notification inbox # * Add an additional field for severity # # - #h3. Hint - #* BPN name and severity is published over the API that it could be requested by the frontend API . - #* Mapping between BPN number and company name is part of the job response of IRS. - # - #h3. Sprint Planning 2 + #h3. Hint + #* BPN name and severity is published over the API that it could be requested by the frontend API . + #* Mapping between BPN number and company name is part of the job response of IRS. + # + #h3. Sprint Planning 2 #* Add BPN and severity to the investigation response. #Check if *bpn names* of *sender and receiver* are processed correctly for created quality investigations which contains following checks: #* correct creation on sender side #* correct reception on receiver side - @TRACEFOSS-1344 @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: [BE] Check correct processing of bpn names in quality investigation + @TRACEFOSS-1344 @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: [BE] Check correct processing of bpn names 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 | "description" | "Testing BPNs TRACEFOSS-1344" | | "severity" | "MINOR" | - | "type" | "INVESTIGATION" | - Then I check, if quality notification has proper values + | "type" | "INVESTIGATION" | + Then I check, if quality notification has proper values | "description" | "Testing BPNs TRACEFOSS-1344" | | "createdBy" | "BPNL00000003CML1" | | "sendTo" | "BPNL00000003CNKC" | | "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 BPNs TRACEFOSS-1344" | | "createdBy" | "BPNL00000003CML1" | | "sendTo" | "BPNL00000003CNKC" | - | "status" | "RECEIVED" | + | "status" | "RECEIVED" | \ No newline at end of file diff --git a/tx-cucumber-tests/src/test/resources/features/8_TRACEFOSS-608.feature b/tx-cucumber-tests/src/test/resources/features/8_TRACEFOSS-608.feature index f2a1fb0f64..76d0158493 100644 --- a/tx-cucumber-tests/src/test/resources/features/8_TRACEFOSS-608.feature +++ b/tx-cucumber-tests/src/test/resources/features/8_TRACEFOSS-608.feature @@ -4,56 +4,56 @@ Feature: ⭐[TEST] [BE] Set and show notification target date #*I want to* be able to set a target date for my notification while creating it #*so that* I am able to monitor if a reply was given in time. # - #h2. Hints + #h2. Hints #[Concept | https://confluence.catena-x.net/pages/viewpage.action?pageId=69429778] #Check if *targetDate = null* is processed correctly for created quality investigations which contains following checks: #* correct sending of _targetDate_ = *null* #* correct reception on receiver side - @TRACEFOSS-1247 @TRACEFOSS-1920 @TRACEFOSS-1139 @TRACEFOSS-1673 @TRACEFOSS-2715 @TRACEFOSS-2910 @TRACEFOSS-1138 @TRACEFOSS-1101 @TEST-1217 @TRACEFOSS-3128 @TEST-904 @TRACEFOSS-3373 @INTEGRATION_TEST @[QualityInvestigation] - Scenario: [BE] Check correct processing of targetDate = null in quality investigation + @TRACEFOSS-1247 @TRACEFOSS-1920 @TRACEFOSS-1139 @TRACEFOSS-1673 @TRACEFOSS-2715 @TRACEFOSS-2910 @TRACEFOSS-1138 @TRACEFOSS-1101 @TEST-1217 @TRACEFOSS-3128 @TEST-904 @TRACEFOSS-3373 @INTEGRATION_TEST @[QualityInvestigation] + Scenario: [BE] Check correct processing of targetDate = null 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" | "MINOR" | | "description" | "Testing without targetDate TRACEFOSS-1247" | - | "type" | "INVESTIGATION" | - Then I check, if quality notification has proper values + | "type" | "INVESTIGATION" | + Then I check, if quality notification has proper values | "description" | "Testing without targetDate TRACEFOSS-1247" | | "targetDate" | "" | | "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 without targetDate TRACEFOSS-1247" | | "targetDate" | "" | - | "status" | "RECEIVED" | + | "status" | "RECEIVED" | #Check if *targetDate* is processed correctly for created quality investigations which contains following checks: #* correct sending of _targetDate_ #* correct reception on receiver side - @TRACEFOSS-1216 @TRACEFOSS-1920 @TRACEFOSS-1139 @TRACEFOSS-1673 @TRACEFOSS-1138 @TRACEFOSS-1101 @TRACEFOSS-2715 @TRACEFOSS-2910 @TEST-1217 @TEST-904 @TRACEFOSS-3128 @TRACEFOSS-3373 @INTEGRATION_TEST @[QualityInvestigation] - Scenario: [BE] Check correct processing of targetDate in quality investigation + @TRACEFOSS-1216 @TRACEFOSS-1920 @TRACEFOSS-1139 @TRACEFOSS-1673 @TRACEFOSS-1138 @TRACEFOSS-1101 @TRACEFOSS-2715 @TRACEFOSS-2910 @TEST-1217 @TEST-904 @TRACEFOSS-3128 @TRACEFOSS-3373 @INTEGRATION_TEST @[QualityInvestigation] + Scenario: [BE] Check correct processing of targetDate 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" | "MINOR" | | "description" | "Testing targetDate TRACEFOSS-1216" | | "targetDate" | "2099-03-11T22:44:06.333827Z" | - | "type" | "INVESTIGATION" | - Then I check, if quality notification has proper values + | "type" | "INVESTIGATION" | + Then I check, if quality notification has proper values | "description" | "Testing targetDate TRACEFOSS-1216" | | "targetDate" | "2099-03-11T22:44: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-1216" | | "targetDate" | "2099-03-11T22:44:06.333827Z" | - | "status" | "RECEIVED" | + | "status" | "RECEIVED" | \ No newline at end of file diff --git a/tx-cucumber-tests/src/test/resources/features/9_TRACEFOSS-607.feature b/tx-cucumber-tests/src/test/resources/features/9_TRACEFOSS-607.feature index 5ef57a78f9..b4049b83db 100644 --- a/tx-cucumber-tests/src/test/resources/features/9_TRACEFOSS-607.feature +++ b/tx-cucumber-tests/src/test/resources/features/9_TRACEFOSS-607.feature @@ -32,35 +32,36 @@ Feature: ⭐ [BE] Provisioning of Receiver update Quality Investigation over Bac #* correct DECLINATION status on receiver side #* correct reception of status update on sender side #* correct reason on receiver and sender side - @TRACEFOSS-1223 @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: [BE] Check correct processing of DECLINATION of quality notification + @TRACEFOSS-1223 @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: [BE] Check correct processing of DECLINATION of quality notification 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" | "MAJOR" | | "description" | "Testing DECLINATION TRACEFOSS-1223" | - | "type" | "INVESTIGATION" | - Then I check, if quality notification has proper values + | "type" | "INVESTIGATION" | + | "receiverBpn" | "BPNL00000003CNKC" | + Then I check, if quality notification has proper values | "severity" | "MAJOR" | | "description" | "Testing DECLINATION TRACEFOSS-1223" | | "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" | "MAJOR" | | "description" | "Testing DECLINATION TRACEFOSS-1223" | | "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 decline quality notification + When I decline quality notification | "reason" | "declined in TRACEFOSS-1223" | - Then I check, if quality notification has proper values + Then I check, if quality notification has proper values | "status" | "DECLINED" | 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" | "DECLINED" | - | "declineReason" | "declined in TRACEFOSS-1223" | + | "declineReason" | "declined in TRACEFOSS-1223" | \ No newline at end of file From 58c6036c69fa07a108f1d8d9590751951c8a0643 Mon Sep 17 00:00:00 2001 From: Maximilian Wesener Date: Mon, 24 Jun 2024 08:32:16 +0200 Subject: [PATCH 3/4] feature(chore):962 fixed cucumber tests --- CHANGELOG.md | 1 + .../features/2_TRACEFOSS-600.feature | 1 + .../features/3_TRACEFOSS-938.feature | 3 ++- .../features/4_TRACEFOSS-936.feature | 23 +++++++++---------- .../features/6_TRACEFOSS-382.feature | 1 + .../features/7_TRACEFOSS-1090.feature | 1 + .../features/8_TRACEFOSS-608.feature | 5 ++-- 7 files changed, 20 insertions(+), 15 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 677a84ec50..4ac353aef7 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,7 @@ _**For better traceability add the corresponding GitHub issue number in each cha - #965 Implement proxy functionality of the IRS policy store - #962 Changed notification model to new one in frontend/backend - #962 Removed initial notification message for notification flow +- #962 Adapt cucumber test to include the mandatory attributes for creating a quality notification - #753 Refactored message history in notification detail view - XXX updated local deployment documentation 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 index 82ac27ff46..2a9ed06417 100644 --- a/tx-cucumber-tests/src/test/resources/features/2_TRACEFOSS-600.feature +++ b/tx-cucumber-tests/src/test/resources/features/2_TRACEFOSS-600.feature @@ -211,6 +211,7 @@ Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts | "description" | "Testing targetDate TRACEFOSS-1543" | | "targetDate" | "2055-05-30T20:43:06.333827Z" | | "type" | "ALERT" | + | "receiverBpn" | "BPNL00000003CNKC" | Then I check, if quality notification has proper values | "description" | "Testing targetDate TRACEFOSS-1543" | | "targetDate" | "2055-05-30T20:43:06.333827Z" | diff --git a/tx-cucumber-tests/src/test/resources/features/3_TRACEFOSS-938.feature b/tx-cucumber-tests/src/test/resources/features/3_TRACEFOSS-938.feature index a13e02e74b..4a00fb7483 100644 --- a/tx-cucumber-tests/src/test/resources/features/3_TRACEFOSS-938.feature +++ b/tx-cucumber-tests/src/test/resources/features/3_TRACEFOSS-938.feature @@ -42,7 +42,8 @@ Feature: ⭐[TEST] Update Quality Investigation (over EDC) And I create quality notification | "severity" | "MAJOR" | | "description" | "Testing ACCEPTANCE TRACEFOSS-1862" | - | "type" | "INVESTIGATION" | + | "type" | "INVESTIGATION" | + | "receiverBpn" | "BPNL00000003CNKC" | Then I check, if quality notification has proper values | "description" | "Testing ACCEPTANCE TRACEFOSS-1862" | | "status" | "CREATED" | diff --git a/tx-cucumber-tests/src/test/resources/features/4_TRACEFOSS-936.feature b/tx-cucumber-tests/src/test/resources/features/4_TRACEFOSS-936.feature index 3db4edc08f..8df4e0eb84 100644 --- a/tx-cucumber-tests/src/test/resources/features/4_TRACEFOSS-936.feature +++ b/tx-cucumber-tests/src/test/resources/features/4_TRACEFOSS-936.feature @@ -10,9 +10,9 @@ Feature: ⭐[BE] Include reason for receiver and sender investigations #with following object: #{code:java} #{ - # "reason" : { - # "close" : $string, - # "accept": $string, | nullable + # "reason" : { + # "close" : $string, + # "accept": $string, | nullable # "decline": $string | nullable # } #} {code} @@ -25,15 +25,14 @@ Feature: ⭐[BE] Include reason for receiver and sender investigations #* correct reception of status update on sender side #* correct reason on receiver and sender side @TRACEFOSS-1861 @TRACEFOSS-3373 @TRACEFOSS-3128 @TRACEFOSS-2910 @TEST-1217 @TRACEFOSS-2715 @TEST-904 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1101 @INTEGRATION_TEST @[QualityInvestigation] - Scenario: [BE] Check correct processing of CLOSURE of quality investigation + Scenario: [BE] Check correct processing of CLOSURE of 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 | "severity" | "MAJOR" | | "description" | "Testing CLOSURE TRACEFOSS-1861" | | "type" | "INVESTIGATION" | - | "receiverBpn" | "BPNL00000003CNKC" | - Then I check, if quality notification has proper values + Then I check, if quality notification has proper values | "description" | "Testing CLOSURE TRACEFOSS-1861" | | "status" | "CREATED" | When I approve quality notification @@ -46,24 +45,24 @@ Feature: ⭐[BE] Include reason for receiver and sender investigations 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 Then I check, if quality notification has proper values | "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 *ACCEPTANCE* of quality investigations 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-1222 @TRACEFOSS-1920 @TRACEFOSS-1673 @TRACEFOSS-1139 @TRACEFOSS-1138 @TRACEFOSS-1101 @TRACEFOSS-2910 @TRACEFOSS-2715 @TEST-1217 @TEST-904 @TRACEFOSS-3128 @TRACEFOSS-3373 @INTEGRATION_TEST @[QualityInvestigation] - Scenario: [BE] Check correct processing of ACCEPTANCE of quality investigation + @TRACEFOSS-1222 @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: [BE] Check correct processing of ACCEPTANCE of 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 @@ -94,4 +93,4 @@ Feature: ⭐[BE] Include reason for receiver and sender investigations When I am logged into TRACE_X_A application Then I check, if quality notification has proper values | "status" | "ACCEPTED" | - | "acceptReason" | "accepted in TRACEFOSS-1222" | + | "acceptReason" | "accepted in TRACEFOSS-1222" | \ No newline at end of file diff --git a/tx-cucumber-tests/src/test/resources/features/6_TRACEFOSS-382.feature b/tx-cucumber-tests/src/test/resources/features/6_TRACEFOSS-382.feature index 26b0e65acc..12c3fa8efb 100644 --- a/tx-cucumber-tests/src/test/resources/features/6_TRACEFOSS-382.feature +++ b/tx-cucumber-tests/src/test/resources/features/6_TRACEFOSS-382.feature @@ -39,6 +39,7 @@ Feature: Create Request for quality investigation / store in queue | "severity" | "MINOR" | | "description" | "Testing severity TRACEFOSS-1652" | | "type" | "INVESTIGATION" | + | "receiverBpn" | "BPNL00000003CNKC" | Then I check, if quality notification has proper values | "description" | "Testing severity TRACEFOSS-1652" | | "status" | "CREATED" | diff --git a/tx-cucumber-tests/src/test/resources/features/7_TRACEFOSS-1090.feature b/tx-cucumber-tests/src/test/resources/features/7_TRACEFOSS-1090.feature index b2d7afc365..d432fbd304 100644 --- a/tx-cucumber-tests/src/test/resources/features/7_TRACEFOSS-1090.feature +++ b/tx-cucumber-tests/src/test/resources/features/7_TRACEFOSS-1090.feature @@ -28,6 +28,7 @@ Feature: 🪓⭐[BE] Add information to notification inbox | "description" | "Testing BPNs TRACEFOSS-1344" | | "severity" | "MINOR" | | "type" | "INVESTIGATION" | + | "receiverBpn" | "BPNL00000003CNKC" | Then I check, if quality notification has proper values | "description" | "Testing BPNs TRACEFOSS-1344" | | "createdBy" | "BPNL00000003CML1" | diff --git a/tx-cucumber-tests/src/test/resources/features/8_TRACEFOSS-608.feature b/tx-cucumber-tests/src/test/resources/features/8_TRACEFOSS-608.feature index 76d0158493..f3d07809f6 100644 --- a/tx-cucumber-tests/src/test/resources/features/8_TRACEFOSS-608.feature +++ b/tx-cucumber-tests/src/test/resources/features/8_TRACEFOSS-608.feature @@ -10,7 +10,7 @@ Feature: ⭐[TEST] [BE] Set and show notification target date #Check if *targetDate = null* is processed correctly for created quality investigations which contains following checks: #* correct sending of _targetDate_ = *null* #* correct reception on receiver side - @TRACEFOSS-1247 @TRACEFOSS-1920 @TRACEFOSS-1139 @TRACEFOSS-1673 @TRACEFOSS-2715 @TRACEFOSS-2910 @TRACEFOSS-1138 @TRACEFOSS-1101 @TEST-1217 @TRACEFOSS-3128 @TEST-904 @TRACEFOSS-3373 @INTEGRATION_TEST @[QualityInvestigation] + @TRACEFOSS-1247 @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: [BE] Check correct processing of targetDate = null 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' @@ -35,7 +35,7 @@ Feature: ⭐[TEST] [BE] Set and show notification target date #Check if *targetDate* is processed correctly for created quality investigations which contains following checks: #* correct sending of _targetDate_ #* correct reception on receiver side - @TRACEFOSS-1216 @TRACEFOSS-1920 @TRACEFOSS-1139 @TRACEFOSS-1673 @TRACEFOSS-1138 @TRACEFOSS-1101 @TRACEFOSS-2715 @TRACEFOSS-2910 @TEST-1217 @TEST-904 @TRACEFOSS-3128 @TRACEFOSS-3373 @INTEGRATION_TEST @[QualityInvestigation] + @TRACEFOSS-1216 @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: [BE] Check correct processing of targetDate 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' @@ -44,6 +44,7 @@ Feature: ⭐[TEST] [BE] Set and show notification target date | "description" | "Testing targetDate TRACEFOSS-1216" | | "targetDate" | "2099-03-11T22:44:06.333827Z" | | "type" | "INVESTIGATION" | + | "receiverBpn" | "BPNL00000003CNKC" | Then I check, if quality notification has proper values | "description" | "Testing targetDate TRACEFOSS-1216" | | "targetDate" | "2099-03-11T22:44:06.333827Z" | From b2690d985b4137b566185fd80731001749eb25e4 Mon Sep 17 00:00:00 2001 From: Maximilian Wesener Date: Mon, 24 Jun 2024 08:48:59 +0200 Subject: [PATCH 4/4] feature(chore):962 updated documentation. --- .../domain-model-quality-notifications.puml | 33 ++++++++++--------- .../arc42/cross-cutting/erm-trace-x.puml | 32 ++++++++++-------- 2 files changed, 35 insertions(+), 30 deletions(-) diff --git a/docs/src/uml-diagrams/arc42/cross-cutting/domain-model/domain-model-quality-notifications.puml b/docs/src/uml-diagrams/arc42/cross-cutting/domain-model/domain-model-quality-notifications.puml index e4841e2afe..df0378f3e0 100644 --- a/docs/src/uml-diagrams/arc42/cross-cutting/domain-model/domain-model-quality-notifications.puml +++ b/docs/src/uml-diagrams/arc42/cross-cutting/domain-model/domain-model-quality-notifications.puml @@ -6,19 +6,22 @@ skinparam linetype ortho title: Notification Domain class Notification { - bpn : BPN; + id: Long, title : String; type: NotificationType; - notificationId : NotificationId; - notificationStatus : NotificationStatus; - description: String; - createdAt: Instant; - notificationSide: NotificationSide; + status : NotificationStatus; + createdBy: String; + createdByName: String; + createdDate: Instant; + updatedDate: Instant; assetIds: ArrayList(); - closeReason: String; - acceptReason: String; - declineReason: String; - messages: List; + channel: NotificationSide; + sentTo: String; + sentToName: String; + severity: NotificationSeverity; + targetDate: Instant; + messages: List + description: String; } enum NotificationType{ @@ -39,18 +42,16 @@ bpn: String; } class NotificationMessage { id: String - createdBy: String - createdByName: String + sentBy: String + sentByName: String sendTo: String sendToName: String contractAgreementId: String notificationReferenceId: String - targetDate: Instant - severity: NotificationSeverity; edcNotificationId: String; - created: LocalDateTime; - updated: LocalDateTime; + messageDate: Instant; messageId: String; + message: String; status: NotificationStatus; errorMessage: String; } diff --git a/docs/src/uml-diagrams/arc42/cross-cutting/erm-trace-x.puml b/docs/src/uml-diagrams/arc42/cross-cutting/erm-trace-x.puml index 3a313e6a5c..2795af48c6 100644 --- a/docs/src/uml-diagrams/arc42/cross-cutting/erm-trace-x.puml +++ b/docs/src/uml-diagrams/arc42/cross-cutting/erm-trace-x.puml @@ -74,38 +74,42 @@ ENTITY public.notification { + id : int8 GENERATED title : varchar(255) type : varchar(50) - bpn : varchar(255) - close_reason : varchar(1000) - created : timestamp - description : varchar(1000) status : varchar(50) - side : varchar(50) - accept_reason : varchar(1000) - decline_reason : varchar(1000) - updated : timestamp - error_message : varchar(255) + description : varchar(1000) + createdBy: varchar + createdByName: varchar + createdDate: timestamp + updatedDate : timestamp + assetIds: varchar + channel: boolean + sendTo: varchar + sentToName: varchar + severity: int4 + targetDate: instant + messages: notification_message } ENTITY public.notification_message { + id : varchar(255) + sentBy: varchar + sentByName: varchar + contract_agreement_id : varchar(255) + edc_url : varchar(255) notification_reference_id : varchar(255) send_to : varchar(255) created_by : varchar(255) notification_id : bigint, - target_date : timestamp - severity : varchar(255) created_by_name : varchar(255) send_to_name : varchar(255) edc_notification_id : varchar(255) status : varchar(255) - created : timestamp - updated : timestamp + message_date: instant error_message : varchar + message: varchar message_id : varchar(255) - is_initial : boolean }