diff --git a/.github/workflows/xray-cucumber-association.yaml b/.github/workflows/xray-cucumber-association.yaml new file mode 100644 index 0000000000..39686eef46 --- /dev/null +++ b/.github/workflows/xray-cucumber-association.yaml @@ -0,0 +1,100 @@ +# Copyright (c) 2024 Contributors to the Eclipse Foundation +# +# See the NOTICE file(s) distributed with this work for additional +# information regarding copyright ownership. +# +# This program and the accompanying materials are made available under the +# terms of the Apache License, Version 2.0 which is available at +# https://www.apache.org/licenses/LICENSE-2.0. +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT +# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the +# License for the specific language governing permissions and limitations +# under the License. +# +# SPDX-License-Identifier: Apache-2.0 + +name: "[BE][TEST][E2E] Cucumber - Association" + +on: + workflow_dispatch: # Trigger manually + schedule: + - cron: "0 0 * * *" + +jobs: + build: + runs-on: ubuntu-latest + + steps: + - uses: actions/checkout@v4 + + - name: Set up JDK 17 + uses: actions/setup-java@v4 + with: + java-version: '17' + distribution: 'temurin' + + - name: Cache maven packages + uses: actions/cache@v4 + with: + path: ~/.m2 + key: ${{ runner.os }}-m2-${{ hashFiles('**/pom.xml') }} + restore-keys: ${{ runner.os }}-m2 + + - name: Download Feature Files + id: download + env: + JIRA_USERNAME: ${{ secrets.ASSOCIATION_TX_JIRA_USERNAME }} + JIRA_PASSWORD: ${{ secrets.ASSOCIATION_TX_JIRA_PASSWORD }} + # JIRA filter 11349: project = "[TR] FOSS - Open Source (Impl.)" AND issuetype = Test AND "Test Type" = Cucumber AND status = Ready AND labels = INTEGRATION_TEST AND (environment ~ DEV OR environment ~ "INT") + # Downloads all feature files of cucumber tests inside TRI project + run: | + token=$(curl -H "Content-Type: application/json" -X POST \ + --data "{ \"client_id\": \"$JIRA_USERNAME\",\"client_secret\": \"$JIRA_PASSWORD\" }" \ + https://xray.cloud.getxray.app/api/v2/authenticate | tr -d '"') + + export HTTP_RESULT=$(curl -s --show-error -w "%{http_code}" --header "Authorization: Bearer $token" \ + "https://xray.cloud.getxray.app/api/v2/export/cucumber?filter=10005&fz=true" -o features.zip) + + [[ $HTTP_RESULT == 200 || $HTTP_RESULT == 400 ]] + echo "::set-output name=http_response::$HTTP_RESULT" + + - name: install tx-models + run: mvn install -pl tx-models + + # Required step due to fact that jira will name feature files differently with each feature added and that will cause duplicate test runs + - name: Cleanup repository feature files + if: ${{ steps.download.outputs.http_response == '200' }} + #working-directory: tx-cucumber-tests + run: | + rm -r tx-cucumber-tests/src/test/resources/features/* + + - name: Build with Maven + if: ${{ steps.download.outputs.http_response == '200' }} + env: + KEYCLOAK_HOST: ${{ secrets.ASSOCIATION_KEYCLOAK_HOST }} + SUPERVISOR_CLIENT_ID: ${{ secrets.ASSOCIATION_SUPERVISOR_CLIENT_ID }} + SUPERVISOR_PASSWORD: ${{ secrets.ASSOCIATION_SUPERVISOR_PASSWORD }} + E2E_TXA_HOST: ${{ secrets.ASSOCIATION_E2E_TXA_HOST }} + E2E_TXB_HOST: ${{ secrets.ASSOCIATION_E2E_TXB_HOST }} + #working-directory: tx-cucumber-tests + run: | + unzip -o tx-cucumber-tests/features.zip -d tx-cucumber-tests/src/test/resources/features + mvn -pl tx-models,tx-cucumber-tests --batch-mode clean install -D"cucumber.filter.tags"="@trace-x-automated" -P association + + - name: Submit results to Xray + if: ${{ always() && steps.download.outputs.http_response == '200' }} + env: + JIRA_USERNAME: ${{ secrets.ASSOCIATION_TX_JIRA_USERNAME }} + JIRA_PASSWORD: ${{ secrets.ASSOCIATION_TX_JIRA_PASSWORD }} + run: | + token=$(curl -H "Content-Type: application/json" -X POST \ + --data "{ \"client_id\": \"$JIRA_USERNAME\",\"client_secret\": \"$JIRA_PASSWORD\" }" \ + https://xray.cloud.getxray.app/api/v2/authenticate | tr -d '"') + + curl --request POST \ + --header 'Content-Type: application/json' \ + --header "Authorization: Bearer $token" \ + --data-binary '@tx-cucumber-tests/report.json' \ + "https://xray.cloud.getxray.app/api/v2/import/execution/cucumber" diff --git a/tx-cucumber-tests/pom.xml b/tx-cucumber-tests/pom.xml index 0b39a20118..c197c4a9b7 100644 --- a/tx-cucumber-tests/pom.xml +++ b/tx-cucumber-tests/pom.xml @@ -35,6 +35,47 @@ SPDX-License-Identifier: Apache-2.0 true + + + + consortia + + true + + + + + org.apache.maven.plugins + maven-surefire-plugin + + + BPNL00000003CML1 + BPNL00000003CNKC + + + + + + + + association + + + + org.apache.maven.plugins + maven-surefire-plugin + + + BPNL000000000UKM + BPNL000000000DWF + + + + + + + + diff --git a/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/TraceabilityTestStepDefinition.java b/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/TraceabilityTestStepDefinition.java index d73993b2d0..c62ece2643 100644 --- a/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/TraceabilityTestStepDefinition.java +++ b/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/TraceabilityTestStepDefinition.java @@ -53,7 +53,7 @@ import static org.eclipse.tractusx.traceability.test.tooling.TraceXEnvironmentEnum.TRACE_X_A; import static org.eclipse.tractusx.traceability.test.tooling.TraceXEnvironmentEnum.TRACE_X_B; import static org.eclipse.tractusx.traceability.test.validator.TestUtils.normalize; -import static org.eclipse.tractusx.traceability.test.validator.TestUtils.wrapStringWithTimestamp; +import static org.eclipse.tractusx.traceability.test.validator.TestUtils.wrapStringWithUUID; @Slf4j public class TraceabilityTestStepDefinition { @@ -61,8 +61,8 @@ public class TraceabilityTestStepDefinition { private RestProvider restProvider; private Long notificationID_TXA = null; private Long notificationID_TXB = null; - protected static final String BPN_TXA = "BPNL00000003CML1"; - protected static final String BPN_TXB = "BPNL00000003CNKC"; + protected static final String BPN_TXA = System.getProperty("txa.bpn"); + protected static final String BPN_TXB = System.getProperty("txb.bpn"); private String notificationDescription = null; private List requestedAssets; private List testAssets; @@ -96,7 +96,7 @@ public void iCreateQualityNotification(DataTable dataTable) { throw MissingStepDefinitionException.missingAssetDefinition(); } - notificationDescription = wrapStringWithTimestamp(input.get("description")); + notificationDescription = wrapStringWithUUID(input.get("description")); final Instant targetDate = input.get("targetDate") == null ? null : Instant.parse(input.get("targetDate")); @@ -127,7 +127,7 @@ public void iEditQualityNotification(DataTable dataTable) { throw MissingStepDefinitionException.missingAssetDefinition(); } - notificationDescription = wrapStringWithTimestamp(input.get("description")); + notificationDescription = wrapStringWithUUID(input.get("description")); final Instant targetDate = input.get("targetDate") == null ? null : Instant.parse(input.get("targetDate")); diff --git a/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/EnvVariablesResolver.java b/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/EnvVariablesResolver.java index c5ecd71b62..7ac5d95b3a 100644 --- a/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/EnvVariablesResolver.java +++ b/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/EnvVariablesResolver.java @@ -21,23 +21,38 @@ public class EnvVariablesResolver { - public static String getSupervisorClientId() { - return System.getenv("SUPERVISOR_CLIENT_ID"); + public static final String ASSOCIATION_SUPERVISOR_TX_A_CLIENT_ID = "ASSOCIATION_SUPERVISOR_TX_A_CLIENT_ID"; + public static final String ASSOCIATION_SUPERVISOR_TX_A_PASSWORD = "ASSOCIATION_SUPERVISOR_TX_A_PASSWORD"; + public static final String ASSOCIATION_SUPERVISOR_TX_B_CLIENT_ID = "ASSOCIATION_SUPERVISOR_TX_B_CLIENT_ID"; + public static final String ASSOCIATION_SUPERVISOR_TX_B_PASSWORD = "ASSOCIATION_SUPERVISOR_TX_B_PASSWORD"; + + public static String getSupervisorClientIdTracexA() { + return System.getenv(ASSOCIATION_SUPERVISOR_TX_A_CLIENT_ID); + } + + public static String getSupervisorPasswordTracexA() { + return System.getenv(ASSOCIATION_SUPERVISOR_TX_A_PASSWORD); + } + + public static String getSupervisorClientIdTracexB() { + return System.getenv(ASSOCIATION_SUPERVISOR_TX_B_CLIENT_ID) == null + ? System.getenv(ASSOCIATION_SUPERVISOR_TX_A_CLIENT_ID) : System.getenv(ASSOCIATION_SUPERVISOR_TX_B_CLIENT_ID); } - public static String getSupervisorPassword() { - return System.getenv("SUPERVISOR_PASSWORD"); + public static String getAssociationSupervisorTxBPassword() { + return System.getenv(ASSOCIATION_SUPERVISOR_TX_B_PASSWORD) == null + ? System.getenv(ASSOCIATION_SUPERVISOR_TX_A_PASSWORD) : System.getenv(ASSOCIATION_SUPERVISOR_TX_B_PASSWORD); } public static String getKeycloakHost() { - return System.getenv("KEYCLOAK_HOST"); + return System.getenv("ASSOCIATION_KEYCLOAK_HOST"); } public static String getTX_A_Host() { - return System.getenv("E2E_TXA_HOST"); + return System.getenv("ASSOCIATION_E2E_TXA_HOST"); } public static String getTX_B_Host() { - return System.getenv("E2E_TXB_HOST"); + return System.getenv("ASSOCIATION_E2E_TXB_HOST"); } } diff --git a/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/rest/Authentication.java b/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/rest/Authentication.java index 5ea204cf1a..8b0b745601 100644 --- a/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/rest/Authentication.java +++ b/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/rest/Authentication.java @@ -40,12 +40,28 @@ public class Authentication { private String clientSecret; private String keycloakHost; - Authentication() { - clientId = EnvVariablesResolver.getSupervisorClientId(); - clientSecret = EnvVariablesResolver.getSupervisorPassword(); + private Authentication() { + clientId = EnvVariablesResolver.getSupervisorClientIdTracexA(); + clientSecret = EnvVariablesResolver.getSupervisorPasswordTracexA(); keycloakHost = EnvVariablesResolver.getKeycloakHost(); } + public static Authentication authenticationForTracexA(){ + Authentication authentication = new Authentication(); + authentication.clientId = EnvVariablesResolver.getSupervisorClientIdTracexA(); + authentication.clientSecret = EnvVariablesResolver.getSupervisorPasswordTracexA(); + authentication.keycloakHost = EnvVariablesResolver.getKeycloakHost(); + return authentication; + } + + public static Authentication authenticationForTracexB(){ + Authentication authentication = new Authentication(); + authentication.clientId = EnvVariablesResolver.getSupervisorClientIdTracexB(); + authentication.clientSecret = EnvVariablesResolver.getAssociationSupervisorTxBPassword(); + authentication.keycloakHost = EnvVariablesResolver.getKeycloakHost(); + return authentication; + } + public String obtainAccessToken() { final Map oauth2Payload = new HashMap<>(); oauth2Payload.put("grant_type", "client_credentials"); diff --git a/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/rest/RestProvider.java b/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/rest/RestProvider.java index 047fe1c914..9282e37ce7 100644 --- a/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/rest/RestProvider.java +++ b/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/tooling/rest/RestProvider.java @@ -63,11 +63,10 @@ public class RestProvider { @Getter private TraceXEnvironmentEnum currentEnv; - private final Authentication authentication; + private Authentication authentication; public RestProvider() { host = null; - authentication = new Authentication(); RestAssured.config = RestAssuredConfig.config().objectMapperConfig(new ObjectMapperConfig().jackson2ObjectMapperFactory( (type, s) -> new ObjectMapper() @@ -84,9 +83,11 @@ public RestProvider() { public void loginToEnvironment(TraceXEnvironmentEnum environment) { if (environment.equals(TRACE_X_A)) { host = EnvVariablesResolver.getTX_A_Host(); + authentication = Authentication.authenticationForTracexA(); currentEnv = TRACE_X_A; } else if (environment.equals(TRACE_X_B)) { host = EnvVariablesResolver.getTX_B_Host(); + authentication = Authentication.authenticationForTracexB(); currentEnv = TRACE_X_B; } System.out.println(host); @@ -249,16 +250,17 @@ public List getReceivedNotifications() { return given().spec(getRequestSpecification()) .contentType(ContentType.JSON) .when() - .body("{\n" + - " \"pageAble\": {\n" + - " \"size\": 1000 \n" + - " },\n" + - " \"searchCriteria\": {\n" + - " \"filter\": [\n" + - " \"channel,EQUAL,RECEIVER,AND\"\n" + - " ]\n" + - " }\n" + - "}") + .body(""" + { + "pageAble": { + "size": 1000\s + }, + "searchCriteria": { + "filter": [ + "channel,EQUAL,RECEIVER,AND" + ] + } + }""") .post("/api/notifications/filter") .then() .statusCode(HttpStatus.SC_OK) diff --git a/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/validator/TestUtils.java b/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/validator/TestUtils.java index 4de6dc6462..0cdadc5907 100644 --- a/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/validator/TestUtils.java +++ b/tx-cucumber-tests/src/test/java/org/eclipse/tractusx/traceability/test/validator/TestUtils.java @@ -19,8 +19,10 @@ package org.eclipse.tractusx.traceability.test.validator; -import java.time.Instant; +import lombok.extern.slf4j.Slf4j; + import java.util.Map; +import java.util.UUID; import java.util.regex.Matcher; import java.util.regex.Pattern; import java.util.stream.Collectors; @@ -29,9 +31,8 @@ public class TestUtils { private static final String UNIQUE_SEPARATOR = ":-:"; - public static String wrapStringWithTimestamp(String string) { - - return UNIQUE_SEPARATOR + string + UNIQUE_SEPARATOR + Instant.now(); + public static String wrapStringWithUUID(String string) { + return UNIQUE_SEPARATOR + string + UNIQUE_SEPARATOR + UUID.randomUUID(); } public static String unWrapStringWithTimestamp(String string) { 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 deleted file mode 100644 index b4cb1dc9a9..0000000000 --- a/tx-cucumber-tests/src/test/resources/features/10_TRACEFOSS-2354.feature +++ /dev/null @@ -1,81 +0,0 @@ -@TRACEFOSS-2354 -Feature: 👍[BE][TABLE_FEATURE] Implementation of Sorting in table views - #h2. Clarification - # * (/) [~steffen.duering@bmw.de] should cascading sorting be enabled ? --> [~martin.kanal@doubleslash.de]   If possible yes. Could also be done in a further development if not possible - # * (/) [~steffen.duering@bmw.de] On which result set the sorting shall be implemented (current page vs / complete resultset? ) - #-->[~martin.kanal@doubleslash.de]  complete resultset would be great. Is it possible? - # - #h2. Business Value - # # (y) [ ] {*}User-business value:{*}: - # # (y) [ ] *Risk reduction:* - # # (y) [ ] *Regulatory value:* - # # (y) [ ] *Commercial value:* - # # (y) [ ] *Market value:* - # # (y) [ ] *Efficiency value:* - # # (y) [ ] *Future value:* - # - #h2. User Story - # - #*As a user* of Trace-X - #*I want* to be able to sort within the table views - #*so that* I only see relevant data and I'm able to better handle big amount of data - # - #--> This User Story should cover all *Backend* tasks that are necessary to cover the funcionalities in the frontend - #h2. Outcome - # - #- (/) User can sort for any colums in UI (within all table views --> parts, other parts) - #- (/) Multiple sort functionalities can be set for ascending and descending according to concept for different attributes on the same time - #- (/) enable reset of sorting - #- (/) Cascading multi-column sorting on multiple columns (Number is showing the sort order) - #- (/) Sorting of columns is based on complete resultset  - #- (/) Swagger API documentation is updated and available on DEV - #- (/) Cover specific columns where cascading sorting might causes conflict (Takeing the semantic under account) - #h2. Mockup - # - #!screenshot-1.png|thumbnail! - #h2. NFR - # - #* - #h2. Hints / Details / Design Sketch : - # - #* - Then I check, if only assets with are responded - - Examples: - | owner-filter | - | "SUPPLIER" | - | "CUSTOMER" | - | "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 deleted file mode 100644 index 99c359e636..0000000000 --- a/tx-cucumber-tests/src/test/resources/features/11_TRACEFOSS-1125.feature +++ /dev/null @@ -1,69 +0,0 @@ -@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-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 - | "severity" | | - | "description" | "Testing severity TRACEFOSS-1220" | - | "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 - | "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 - | "severity" | | - | "description" | "Testing severity TRACEFOSS-1220" | - | "status" | "RECEIVED" | - 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" | - - Examples: - |severity| - |"MINOR"| - |"MAJOR"| - |"CRITICAL"| - |"LIFE-THREATENING"| \ No newline at end of file diff --git a/tx-cucumber-tests/src/test/resources/features/1_CXTM-301,CXTM-300,CXTM-299,CXTM-298(+15).feature b/tx-cucumber-tests/src/test/resources/features/1_CXTM-301,CXTM-300,CXTM-299,CXTM-298(+15).feature new file mode 100644 index 0000000000..8189ae675f --- /dev/null +++ b/tx-cucumber-tests/src/test/resources/features/1_CXTM-301,CXTM-300,CXTM-299,CXTM-298(+15).feature @@ -0,0 +1,493 @@ +Feature: + + @TEST_CXTM-301 @trace-x-automated + Scenario: TRACEFOSS-1216 [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 + | "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 + | "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 + | "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 + | "description" | "Testing targetDate TRACEFOSS-1216" | + | "targetDate" | "2099-03-11T22:44:06.333827Z" | + | "status" | "RECEIVED" | + + @TEST_CXTM-300 @trace-x-automated + Scenario Outline: TRACEFOSS-1220 [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 + | "severity" | | + | "description" | "Testing severity TRACEFOSS-1220" | + | "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 + | "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 + | "severity" | | + | "description" | "Testing severity TRACEFOSS-1220" | + | "status" | "RECEIVED" | + 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" | + + Examples: + |severity| + |"MINOR"| + |"MAJOR"| + |"CRITICAL"| + |"LIFE-THREATENING"| + + @TEST_CXTM-299 @trace-x-automated + Scenario Outline: TRACEFOSS-1221 [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: + | owner-filter | + | "SUPPLIER" | + | "CUSTOMER" | + | "OWN" | + + @TEST_CXTM-298 @trace-x-automated + Scenario: TRACEFOSS-1222 [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 + | "severity" | "MAJOR" | + | "description" | "Testing ACCEPTANCE TRACEFOSS-1222" | + | "type" | "INVESTIGATION" | + 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 + | "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 + | "severity" | "MAJOR" | + | "description" | "Testing ACCEPTANCE TRACEFOSS-1222" | + | "status" | "RECEIVED" | + When I acknowledge quality notification + Then I check, if quality notification has proper values + | "status" | "ACKNOWLEDGED" | + When I accept quality notification + | "reason" | "accepted in TRACEFOSS-1222" | + 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 + | "status" | "ACCEPTED" | + | "acceptReason" | "accepted in TRACEFOSS-1222" | + + @TEST_CXTM-297 @trace-x-automated + Scenario: TRACEFOSS-1223 [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 + | "severity" | "MAJOR" | + | "description" | "Testing DECLINATION TRACEFOSS-1223" | + | "type" | "INVESTIGATION" | + 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 + | "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 + | "severity" | "MAJOR" | + | "description" | "Testing DECLINATION TRACEFOSS-1223" | + | "status" | "RECEIVED" | + When I acknowledge quality notification + Then I check, if quality notification has proper values + | "status" | "ACKNOWLEDGED" | + When I decline quality notification + | "reason" | "declined in TRACEFOSS-1223" | + 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 + | "status" | "DECLINED" | + | "declineReason" | "declined in TRACEFOSS-1223" | + + @TEST_CXTM-294 @trace-x-automated + Scenario: TRACEFOSS-1247 [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 + | "severity" | "MINOR" | + | "description" | "Testing without targetDate TRACEFOSS-1247" | + | "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 + | "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 + | "description" | "Testing without targetDate TRACEFOSS-1247" | + | "targetDate" | "" | + | "status" | "RECEIVED" | + + @TEST_CXTM-291 @trace-x-automated + Scenario Outline: TRACEFOSS-1539 [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 + | "severity" | | + | "description" | "Testing severity TRACEFOSS-1539" | + | "type" | "ALERT" | + 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 + | "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 + | "severity" | | + | "description" | "Testing severity TRACEFOSS-1539" | + | "status" | "RECEIVED" | + 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" | + + Examples: + |severity| + |"MINOR"| + |"MAJOR"| + |"CRITICAL"| + |"LIFE-THREATENING"| + + @TEST_CXTM-289 @trace-x-automated + Scenario: TRACEFOSS-1543 [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 + | "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 + | "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 + | "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 + | "description" | "Testing targetDate TRACEFOSS-1543" | + | "targetDate" | "2055-05-30T20:43:06.333827Z" | + | "status" | "RECEIVED" | + + @TEST_CXTM-288 @trace-x-automated + Scenario: TRACEFOSS-1544 [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" | + Then I check, if quality notification has proper values + | "severity" | "MAJOR" | + | "description" | "Testing ACCEPTANCE TRACEFOSS-1544" | + | "status" | "CREATED" | + 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 + | "severity" | "MAJOR" | + | "description" | "Testing ACCEPTANCE TRACEFOSS-1544" | + | "status" | "RECEIVED" | + When I acknowledge quality notification + Then I check, if quality notification has proper values + | "status" | "ACKNOWLEDGED" | + When I accept quality notification + | "reason" | "accepted in TRACEFOSS-1544" | + 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 + | "status" | "ACCEPTED" | + And I check, if quality notification has proper values + | "acceptReason" | "accepted in TRACEFOSS-1544" | + + @TEST_CXTM-287 @trace-x-automated + Scenario: TRACEFOSS-1545 [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" | + Then I check, if quality notification has proper values + | "severity" | "MAJOR" | + | "description" | "Testing DECLINATION TRACEFOSS-1545" | + | "status" | "CREATED" | + 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 + | "severity" | "MAJOR" | + | "description" | "Testing DECLINATION TRACEFOSS-1545" | + | "status" | "RECEIVED" | + When I acknowledge quality notification + Then I check, if quality notification has proper values + | "status" | "ACKNOWLEDGED" | + When I decline quality notification + | "reason" | "declined in TRACEFOSS-1545" | + 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 + | "status" | "DECLINED" | + And I check, if quality notification has proper values + | "declineReason" | "declined in TRACEFOSS-1545" | + + @TEST_CXTM-286 @trace-x-automated + Scenario: TRACEFOSS-1546 [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" | + Then I check, if quality notification has proper values + | "description" | "Testing without targetDate TRACEFOSS-1546" | + | "targetDate" | "" | + | "status" | "CREATED" | + 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 + | "description" | "Testing without targetDate TRACEFOSS-1546" | + | "targetDate" | "" | + | "status" | "RECEIVED" | + + @TEST_CXTM-284 @trace-x-automated + Scenario: TRACEFOSS-1652 [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 + | "severity" | "MINOR" | + | "description" | "Testing severity TRACEFOSS-1652" | + | "type" | "INVESTIGATION" | + Then I check, if quality notification has proper values + | "description" | "Testing severity TRACEFOSS-1652" | + | "status" | "CREATED" | + | "assetIdCount" | "2" | + 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 + | "description" | "Testing severity TRACEFOSS-1652" | + | "status" | "RECEIVED" | + | "assetIdCount" | "2" | + 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" | + | "assetIdCount" | "2" | + + @TEST_CXTM-283 @trace-x-automated + Scenario: TRACEFOSS-1670 [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" | + | "type" | "ALERT" | + Then I check, if quality notification has proper values + | "description" | "Testing severity TRACEFOSS-1670" | + | "status" | "CREATED" | + | "assetIdCount" | "2" | + 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 + | "description" | "Testing severity TRACEFOSS-1670" | + | "status" | "RECEIVED" | + | "assetIdCount" | "2" | + 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" | + | "assetIdCount" | "2" | + + @TEST_CXTM-282 @trace-x-automated + Scenario: TRACEFOSS-1861 [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 + | "description" | "Testing CLOSURE TRACEFOSS-1861" | + | "status" | "CREATED" | + 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 + And I check, if quality notification has proper values + | "status" | "RECEIVED" | + 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" | + + @TEST_CXTM-281 @trace-x-automated + Scenario: TRACEFOSS-1862 [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" | + Then I check, if quality notification has proper values + | "description" | "Testing ACCEPTANCE TRACEFOSS-1862" | + | "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 + + @TEST_CXTM-280 @trace-x-automated + Scenario: TRACEFOSS-1863 [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" | + Then I check, if quality notification has proper values + | "description" | "Testing ACCEPTANCE TRACEFOSS-1863" | + | "status" | "CREATED" | + 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 + And I check, if quality notification has proper values + | "status" | "RECEIVED" | + 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" | + + @TEST_CXTM-279 @trace-x-automated + Scenario: TRACEFOSS-1864 [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" | + 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 + + @TEST_CXTM-273 @trace-x-automated + Scenario: TRACEFOSS-3354 [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' + And I create quality notification + | "severity" | "MAJOR" | + | "description" | "Testing ACCEPTANCE TRACEFOSS-1864" | + | "type" | "ALERT" | + | "title" | "Initial title" | + 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 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" | + + 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 deleted file mode 100644 index cc0f44d4b0..0000000000 --- a/tx-cucumber-tests/src/test/resources/features/1_TRACEFOSS-1393.feature +++ /dev/null @@ -1,64 +0,0 @@ -@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 *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 - 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' - And I create quality notification - | "severity" | "MAJOR" | - | "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 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" | - - #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] - 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 \ 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 deleted file mode 100644 index 2a9ed06417..0000000000 --- a/tx-cucumber-tests/src/test/resources/features/2_TRACEFOSS-600.feature +++ /dev/null @@ -1,266 +0,0 @@ -@TRACEFOSS-600 -Feature: ⭐ [BE][QUALITY_ALERTS] Enable Quality Alerts - #h2. User Story - # - #*As a* user - #*I want to* be able to use all quality alerts - #*so that* can report quality problems in upstream visibility. - #h2. Outcome - # * (x) Quality Alerts are implementd (HAPPY PATH) - # - #h2. Consolidation for pbis - # * TRACEFOSS-1388 - # - #h2. Sprint Planning 2 - # * Part 1 -> Pull Request 1 - # ** Make sure to not duplicate code instead of base class or reuse existing logic (e.g. state transitions) - # ** Implement a service - # ** Publisher Service - # ** Receiver Service - # ** Implement a repository - # * Part 2 -> Pull Request 2 ( Do not start with it before PR 1 is merged) - # ** Make sure all condiitions which exclude quality alerts are removed - # ** Make sure that the existing api which creates a contract will be able to create it for quality alerts - # *** /api/edc/notification/contract - # ** Make sure that the logic of receiver side does filter for quality alert assets (currently only for quality investigations) - # ** Send alert from a to b - # ** Send alert from b to a - # * Part 3 -> Pull Request 3 -> Enable frontend -> [~martin.maul@doubleslash.de]  - # ** [https://github.com/catenax-ng/tx-traceability-foss/pull/264/files#diff-de4cfce80ee64138f3cdf6ab0af7b29aed8687212738a0a2d18567e29e7b9472R31] - # **   - - #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-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" | - 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 - And I check, if quality notification has proper values - | "status" | "RECEIVED" | - 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" | - - #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] - 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" | - | "sendTo" | "BPNL00000003CNKC" | - | "status" | "CREATED" | - 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 - | "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-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" | "" | - | "status" | "CREATED" | - 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 - | "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-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" | - | "status" | "CREATED" | - 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 - | "severity" | "MAJOR" | - | "description" | "Testing DECLINATION TRACEFOSS-1545" | - | "status" | "RECEIVED" | - When I acknowledge quality notification - Then I check, if quality notification has proper values - | "status" | "ACKNOWLEDGED" | - When I decline quality notification - | "reason" | "declined in TRACEFOSS-1545" | - 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 - | "status" | "DECLINED" | - And I check, if quality notification has proper values - | "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] - 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" | - | "status" | "CREATED" | - 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 - | "severity" | "MAJOR" | - | "description" | "Testing ACCEPTANCE TRACEFOSS-1544" | - | "status" | "RECEIVED" | - When I acknowledge quality notification - Then I check, if quality notification has proper values - | "status" | "ACKNOWLEDGED" | - When I accept quality notification - | "reason" | "accepted in TRACEFOSS-1544" | - 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 - | "status" | "ACCEPTED" | - And I check, if quality notification 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-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 - | "severity" | "MINOR" | - | "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" | - | "status" | "CREATED" | - 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 - | "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-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 - | "severity" | | - | "description" | "Testing severity TRACEFOSS-1539" | - | "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 - | "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 - | "severity" | | - | "description" | "Testing severity TRACEFOSS-1539" | - | "status" | "RECEIVED" | - 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" | - - Examples: - |severity| - |"MINOR"| - |"MAJOR"| - |"CRITICAL"| - |"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 deleted file mode 100644 index 4a00fb7483..0000000000 --- a/tx-cucumber-tests/src/test/resources/features/3_TRACEFOSS-938.feature +++ /dev/null @@ -1,54 +0,0 @@ -@TRACEFOSS-938 -Feature: ⭐[TEST] Update Quality Investigation (over EDC) - #h2. User Story - # - #*As* Supervisor - #*I want* to be able to update a quality investigation that I received - #*so that* the corresponding partner knows in which status the notification is on my side. - #h2. Hints / Details / . Hints & NFR (Technical, Design & Content))* :  - # - #1. BPN B receives a notification - #2. BPN B updates notification - #3. BPN A receives notification update with corresponding status - # * The right notification asset needs to be looked up in the Catalog offer of the counter side - # * Lookup based on asset:props - # * Keep in mind that some fields are optional and might be empty - # ** Handle based on documentation / agreement like for send/receive - # ** E.g. "information" will be empty for Update from REC to ACK - # * Utilize EDC Update functionality in order to send investigation update over EDC from BNP B to BPN A. - # - #Docs: [Notification Update Docu|https://confluence.catena-x.net/pages/viewpage.action?pageId=69429778#id-(TRS)[Release3]%F0%9F%93%9CTraceabilityApp(ImplementationSpecification)-HttpPOSTendpointtoupdateanotification] - # - #!screenshot-1.png|thumbnail! - #h2. TODO: - # * (-) Fill out description - # * (-) Fill out Story Points - # * (-) Assign an Assignee - # * (-) define Acceptance Criteria - # * (-) [DoR |https://confluence.catena-x.net/pages/viewpage.action?pageId=917505]  - # - #h2. LOP - # * (/) [~thomas.braun3@zf.com] Update AC and describe error handling, retry and rollback. - # * (/) Add pbi for "Close notification on sender side". --> TRACEFOSS-961 - - #Check if *CANCELLATION* of quality investigations 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-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" | - | "receiverBpn" | "BPNL00000003CNKC" | - Then I check, if quality notification has proper values - | "description" | "Testing ACCEPTANCE TRACEFOSS-1862" | - | "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 \ 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 deleted file mode 100644 index 8df4e0eb84..0000000000 --- a/tx-cucumber-tests/src/test/resources/features/4_TRACEFOSS-936.feature +++ /dev/null @@ -1,96 +0,0 @@ -@TRACEFOSS-936 -Feature: ⭐[BE] Include reason for receiver and sender investigations - #*As a* Dev - # - #*I want to* update contract of: - # - #/investigations/created (sender side of notifications) - #/investigations/received (receiver side of notifications) - # - #with following object: - #{code:java} - #{ - # "reason" : { - # "close" : $string, - # "accept": $string, | nullable - # "decline": $string | nullable - # } - #} {code} - #Where for accept and decline reason, it's either one or another. Reasons are passed from receiver to sender and from sender to receiver via EDC and stored in the database. - # - #*so that* the information provided with the update is also stored and provided to sender and receiver sides. - - #Check if *CLOSURE* of quality investigations is processed correctly which contains following checks: - #* 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 - 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 - | "description" | "Testing CLOSURE TRACEFOSS-1861" | - | "status" | "CREATED" | - 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 - And I check, if quality notification has proper values - | "status" | "RECEIVED" | - 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" | - - #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-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 - | "severity" | "MAJOR" | - | "description" | "Testing ACCEPTANCE TRACEFOSS-1222" | - | "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 - | "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 - | "severity" | "MAJOR" | - | "description" | "Testing ACCEPTANCE TRACEFOSS-1222" | - | "status" | "RECEIVED" | - When I acknowledge quality notification - Then I check, if quality notification has proper values - | "status" | "ACKNOWLEDGED" | - When I accept quality notification - | "reason" | "accepted in TRACEFOSS-1222" | - 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 - | "status" | "ACCEPTED" | - | "acceptReason" | "accepted in TRACEFOSS-1222" | \ No newline at end of file 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 deleted file mode 100644 index 1f90a5a94e..0000000000 --- a/tx-cucumber-tests/src/test/resources/features/5_TRACEFOSS-1625.feature +++ /dev/null @@ -1,49 +0,0 @@ -@TRACEFOSS-1625 -Feature: [BE][FE]Handling of several parts in one quality alert - #*As* a user - #*I want* to be able to create and response quality alerts with several parts as one alert - #*So that* quality alerts with several parts are able to be processed on either sender or receiver side correctly - # - #*Outcome* - #* quality alerts are created on sender side as one alert even with several parts - #* quality alerts with several parts are sent correctly as one alert to the receiver - #* receiver creates one alert with several parts as sent - #* receiver and sender can change status and update each other for alerts with several parts - # - #*Additional information* - #Currently quality alerts with several parts are created correctly as one alert on the sender side but are created as own alert for each part on the receiver side. - #(!) Quality-Investigations are processed correctly! - - #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-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" | - | "type" | "ALERT" | - | "receiverBpn" | "BPNL00000003CNKC" | - Then I check, if quality notification has proper values - | "description" | "Testing severity TRACEFOSS-1670" | - | "status" | "CREATED" | - | "assetIdCount" | "2" | - 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 - | "description" | "Testing severity TRACEFOSS-1670" | - | "status" | "RECEIVED" | - | "assetIdCount" | "2" | - 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" | - | "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 deleted file mode 100644 index 12c3fa8efb..0000000000 --- a/tx-cucumber-tests/src/test/resources/features/6_TRACEFOSS-382.feature +++ /dev/null @@ -1,62 +0,0 @@ -@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 - #As a user - # - #I want to be able to create a quality investigation for selected parts with a description of the defect - # - #to notify the corresponding supplier(s) of the parts about a possible quality issue that needs to be investigated. The requests should be stored in a queue with status pending and not be directly send to the supplier(s). - # - #  - # - #*Detailed description* - # - #The user can create a quality investigation for one or more parts. The description added in the pop up will be added to every part. Once the user creates a quality investigation he will get an information that there is one or more investigations pending for distribution. - #The user can click on the information and will directy be redirected to pending Queue in his Quality investigation inbox. - # - #  - # - #*Additional info* - # * - Description: free text, max length: 1000  - # * - Hint: Pending state and store in Queue because *later* we might set up a rights an role concept and only specific role (Supervisor) is able to send Notifications to partners. - - #Check if *several parts* in one investigation are processed correctly which contains following checks: - #* 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 - 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 - | "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" | - | "assetIdCount" | "2" | - 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 - | "description" | "Testing severity TRACEFOSS-1652" | - | "status" | "RECEIVED" | - | "assetIdCount" | "2" | - 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" | - | "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 deleted file mode 100644 index d432fbd304..0000000000 --- a/tx-cucumber-tests/src/test/resources/features/7_TRACEFOSS-1090.feature +++ /dev/null @@ -1,46 +0,0 @@ -@TRACEFOSS-1090 -Feature: 🪓⭐[BE] Add information to notification inbox - #As a *User* - # - #I want to have added the information of severity, send to (BPN / name), and received from (BPN / name) as additional columns to the notifications inbox - # - #so that I am able to see on the first sign who/whom the notification was sent to as well as the severity. - #h3. Outcome - # * Add an additional field for bpn name (sender + receiver) - # * 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 - #* 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 - 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 - | "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" | - | "sendTo" | "BPNL00000003CNKC" | - | "status" | "CREATED" | - 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 - | "description" | "Testing BPNs TRACEFOSS-1344" | - | "createdBy" | "BPNL00000003CML1" | - | "sendTo" | "BPNL00000003CNKC" | - | "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 deleted file mode 100644 index f3d07809f6..0000000000 --- a/tx-cucumber-tests/src/test/resources/features/8_TRACEFOSS-608.feature +++ /dev/null @@ -1,60 +0,0 @@ -@TRACEFOSS-608 -Feature: ⭐[TEST] [BE] Set and show notification target date - #*As a* User - #*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 - #[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-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' - And I create quality notification - | "severity" | "MINOR" | - | "description" | "Testing without targetDate TRACEFOSS-1247" | - | "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 - | "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 - | "description" | "Testing without targetDate TRACEFOSS-1247" | - | "targetDate" | "" | - | "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-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' - And I create quality notification - | "severity" | "MINOR" | - | "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" | - | "status" | "CREATED" | - 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 - | "description" | "Testing targetDate TRACEFOSS-1216" | - | "targetDate" | "2099-03-11T22:44:06.333827Z" | - | "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 deleted file mode 100644 index b4049b83db..0000000000 --- a/tx-cucumber-tests/src/test/resources/features/9_TRACEFOSS-607.feature +++ /dev/null @@ -1,67 +0,0 @@ -@TRACEFOSS-607 -Feature: ⭐ [BE] Provisioning of Receiver update Quality Investigation over Backend API - #As a Supervisor - #I want to be able to update a quality investigation that I received - #So that the corresponding partner knows in which status the notification is on my side. - # - #*Additional information* - # * Update from RECEIVED to ACKNOWLEDGED without further input - # * Update from ACKNOWLEDGED to ACCEPTED with text information - # * Update from ACKNOWLEDGED to DECLINED with text information - # * No Update to CLOSED possible on Receiver side (Once the Notification is closed it is read-only and could not be changed/modified any more ) - # - #*Workflow Diagram* - # - #!NotificationStatusWorkflow.png|thumbnail! - #h2. Backend Topics - # - #  - #h2. Sprint Planning 2:  - # * Backend: 5 SP - # * Frontend: 5 SP - # - #h3. Backend - # * Endpoint "Create Notification" [~jedrzej.serwa@partner.doubleslash.de]  Please update this  - # * Endpoint "Status Update" - # * Endpoint "" - # * Real-time notification - # - #  - - #Check if *DECLINATION* of quality investigations 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-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 - | "severity" | "MAJOR" | - | "description" | "Testing DECLINATION TRACEFOSS-1223" | - | "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 - | "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 - | "severity" | "MAJOR" | - | "description" | "Testing DECLINATION TRACEFOSS-1223" | - | "status" | "RECEIVED" | - When I acknowledge quality notification - Then I check, if quality notification has proper values - | "status" | "ACKNOWLEDGED" | - When I decline quality notification - | "reason" | "declined in TRACEFOSS-1223" | - 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 - | "status" | "DECLINED" | - | "declineReason" | "declined in TRACEFOSS-1223" | \ No newline at end of file