Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Item Relationship Service (IRS) Release 23.12 Test Results Acceptance Criteria #87

Closed
2 tasks done
kelaja opened this issue Oct 6, 2023 · 5 comments
Closed
2 tasks done
Assignees
Labels
foss RM FOSS definition irs Feature/Bug for Item Relationship Service component Prep-PI11 CX-ART PI Preparation Issues for Consortia Planning test results RM test results
Milestone

Comments

@kelaja
Copy link
Contributor

kelaja commented Oct 6, 2023

Release Test Results 23.12

Source in Catena-X Confluence and Expert Contacts here(Source only accessible for Catena-X Consortia members in current transition phase).

  • E2E System Integrations Tests #352

    • To pass the Consortia Gate 4, evidence has to be made available that all test criteria up to and including TRL 4 & TRL 6 have been achieved.
    • Expected evidence = outputs of TRL 4 and TRL 6.
    • Test Management has mapped and described all mandatory tests for Consortia Quality Gates HERE(Source only accessible for Catena-X Consortia members in current transition phase).
    • Please focus on the columns "Derived Criteria" and "Outputs"
    • Document your test results in Catena-X JIRA XRAY
    • Use the fields “DoD” and “Status” (story & solution level) to approve requirements.
    • Interim test results are required after Tests of each Sprint, this is pre-requisite to participate in E2E test phase

    Contact:

    • TEST MANAGEMENT
  • Approval of User Journey #353

    • CX Business Owner confirms: All acceptance criteria met (as defined in PI documentation)
      Relevant evidence is available

    Artifact Repository

    • Jira Solution Level(Source only accessible for Catena-X Consortia members in current transition phase)

    Best Practise

    • PO to obtain BO approval prior to Gate review.
    • BO therefore to evaluate progress by participation at iteration demos.
    • BOs provide E2E test cases.
    • BOs welcome to act as tester.
    • BOs expected to participate in System Demo.

    Contacts:

    • FOSS Product Owners &
    • CX Business Owners
@kelaja kelaja added irs Feature/Bug for Item Relationship Service component test results RM test results foss RM FOSS definition labels Oct 6, 2023
@kelaja kelaja added this to the 23.12 milestone Oct 6, 2023
@kelaja kelaja self-assigned this Oct 6, 2023
@jzbmw jzbmw self-assigned this Oct 16, 2023
@jzbmw jzbmw moved this from Inbox to Backlog in Release Planning Oct 25, 2023
@jzbmw jzbmw added the Prep-PI11 CX-ART PI Preparation Issues for Consortia Planning label Oct 25, 2023
@jzbmw jzbmw moved this from Backlog to Work in progress in Release Planning Oct 26, 2023
@ds-alexander-bulgakov
Copy link

Test results were presented to Bernd Rothbrust today in a meeting. He will get in contact with Kelaja and set a status in this ticket after. Bernd should be done within the next few days.

@BerndRothbrust
Copy link

Approvel not given because Test not Done (Static Testdata not availible).
Actual High Defects:

  • Cancellation of batch jobs sometimes not possible (High)
  • Aspect in the SingleLevelBomasBuild currently not queryable due to a bug in the Symantic HUB - FiX expected in the next release

@ds-alexander-bulgakov
Copy link

ds-alexander-bulgakov commented Nov 9, 2023

Please pay attention to the following notes for more clarification:

  • The cancellation bug #253 is IMO set to "highest"-priority by mistake while copying the ticket from JIRA since the previous priority was medium, see TRI-1719. @jzbmw or @mkanal did you change the priority intentionally? As far as i can see priority "highest" is set by default in git, maybe this is the reason. -> UPDATE: Priority of bugticket has been set to "low".
  • The aspect issue #242 is not a IRS defect but the reason for several failed tests. The issue itself is in SemanticHub.
  • Currently the IRS can not be tested separately due to missing testdata on INT, this is true. But please keep in mind the IRS is used in TRACEFOSS and has been tested within and together with the TRACEFOSS as we already did the whole year previously. This tests are documented in the TRACEFOSS executions, just as a reminder.

@BerndRothbrust
Copy link

Based on the situation that IRS is tested with the tracefoss tests and existing tests could not performend because of "no testdata". It will get on OK for the Tests. But still have known defects and are documented on the changelog as known knows.

So they get an OK with known knows. @kelaja

@jzbmw jzbmw moved this from Work in progress to Done in Release Planning Nov 20, 2023
@PatStra
Copy link

PatStra commented Nov 20, 2023

Business approval granted after live demo on November 20th 2023

@kelaja kelaja closed this as completed Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
foss RM FOSS definition irs Feature/Bug for Item Relationship Service component Prep-PI11 CX-ART PI Preparation Issues for Consortia Planning test results RM test results
Projects
Status: Done
Development

No branches or pull requests

6 participants