[TESTING] Integration E2E Tests for backward compatibility (Happy + Unhappy Path)

[mkanal]

As team
I want to have test for backward compatibility of semantic models
so that we have a good evidence that irs works

Hints / Details

• ...

Acceptance Criteria

• Tests for different traversal semantic models for major release 3.0.0 SLUAB, SLBAB
• Tests for different semantic models for major release 2.0.0 PartAsPlanned, SerialPart 3.0.0 etc.
• This covers creating own testdata with new semantic models in future versions with modifications like SerialPart 3.1.0 or 3.2.1 which does not exists right now

Outcome

• Cucumber Execution Report https://reports.cucumber.io/reports/93e01d62-6730-495a-9279-2e0902c112c6
• Documentation https://github.com/eclipse-tractusx/item-relationship-service/blob/main/docs/concept/%23529-E2E-tests-aspect-version-compatibility/%23529-E2E-tests-aspect-version-compatibility.md

Out of Scope

• ...

[dsmf]

Outcome:

1. • Add aspects needed for the tests to localModels in catena-x-environments: Catena x environments 529 #705
     • merged, branch deleted
     • After merge switch back env branch in ArgoCD
2. • Fix testdata import script and update documentation: Chore/529 fix import script and update documentation #707
3. • Add test data files: Chore/529 testdata files #709
4. • Add version compatibility tests: Chore/529 e2e test backward compatibility #706
     • add tests to Xray
     • check in feature file with references to Xray
5. • Fix documentation: chore(test):[#529] fix SingleLevelBomAsBuilt test documentation #715
6. • Tests also added to Xray, see https://jira.catena-x.net/browse/TRI-2047?jql=summary%20%20~%20%22DEV-TEST%22%20and%20summary%20~%20529%20ORDER%20BY%20%20key
7. • Successful test execution: https://github.com/eclipse-tractusx/item-relationship-service/actions/runs/9597500957

[mkanal]

Review:

• Please link Tests in Xray to suitable Test Plan for Test Execution.
• Evidence for AC 1 & 3. How is this implemented?
• Cucumber Test Execution https://reports.cucumber.io/reports/93e01d62-6730-495a-9279-2e0902c112c6

Tests:
https://jira.catena-x.net/browse/TRI-2050
https://jira.catena-x.net/browse/TRI-2049
https://jira.catena-x.net/browse/TRI-2048
https://jira.catena-x.net/browse/TRI-2047

[dsmf]

@mkanal: as it can be seen in https://jira.catena-x.net/browse/TRI-2047?jql=summary%20%20~%20%22DEV-TEST%22%20and%20summary%20~%20529%20ORDER%20BY%20%20key there is one more test:
https://jira.catena-x.net/browse/TRI-2047

[dsmf]

@mkanal:

Please link Tests in Xray to suitable Test Plan for Test Execution.

Since #371 there is no cucumber xray integration anymore, see

• https://github.com/eclipse-tractusx/item-relationship-service/pull/685/files
• Transfer to Tractus-X Focus topics regarding Post Consortia #223

[dsmf]

@mkanal:

Evidence for AC 1 & 3. How is this implemented?

https://github.com/eclipse-tractusx/item-relationship-service/blob/main/docs/concept/%23529-E2E-tests-aspect-version-compatibility/%23529-E2E-tests-aspect-version-compatibility.md describes how this is implemented.

See the different major semantic model versions in the test data structure (files are linked there). Concerning future versions see the attribute futureAddedAttribute in the test data and the not yet existing model version in the test data:

[mkanal]

Semantic Models like SerialPart are checked against a given schema. Testing agains a new future version will not work in this case. Tests using futureAddedField to simulate a future change in the semantic model are realized only for traversal aspects.

[mkanal]

LGFM
PO acceptance in behalf of @jzbmw