doc: DCM KIT additional content E2E test

[ClosedSourcerer]

Description

Addresse Issues

• [R25.03] DCM: Additional Content E2E Test  sig-release#896

Added

• Added additional E2E Tests to Development View

Changed

• Updated Test - Customer to improve readability
• Updated Test - Supplier to improve readability

Pre-review checks

Please ensure to do as many of the following checks as possible, before asking for committer review:

• DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.
• Copyright and license header are present on all affected files
• IP-Issue created and returned positively

[stephanbcbauer]

Thanks for this PR ⇾ Built it locally ⇾ worked fine
TBH, I am unable to review it on a business level

The DEPENDENCIES file would need an update, and I think we have to create an IP issue for this number of changes.

thx

[ClosedSourcerer]

Thanks for this PR ⇾ Built it locally ⇾ worked fine TBH, I am unable to review it on a business level

Review on a BusinessLevel will be executed by the DCM Expert Group

The DEPENDENCIES file would need an update, and I think we have to create an IP issue for this number of changes.

I created the IP Issue and linked it in the PRs initial comment.

Obviously I do not fully grasp the whole DEPENDENCIES issue yet.
This PR only changes existing markdown files and does not introduce package Ingestion anywhere.
So, assuming that up-to-date DEPENDENCIES are a requirement before merging, the base this PR is build upon should be fine and hence the whole PR as well.

What am I missing?

[stephanbcbauer]

Thanks for this PR ⇾ Built it locally ⇾ worked fine TBH, I am unable to review it on a business level

Review on a BusinessLevel will be executed by the DCM Expert Group

The DEPENDENCIES file would need an update, and I think we have to create an IP issue for this number of changes.

I created the IP Issue and linked it in the PRs initial comment.

Obviously I do not fully grasp the whole DEPENDENCIES issue yet. This PR only changes existing markdown files and does not introduce package Ingestion anywhere. So, assuming that up-to-date DEPENDENCIES are a requirement before merging, the base this PR is build upon should be fine and hence the whole PR as well.

What am I missing?

Cool, thanks. Let's have a short call related to DEPENDENCIES. Here are some hints, what kind of issues there might be:

1. DEPENDENCIES files is not up-to-date. ⇾ There might be changes in the master data ⇾ new libs, versions, status ⇾ Solution: rebase (if someone else already updated the file)
2. New versions libs are used or haven't been analysed by eclipse -> Third Party issue is needed

Solution (for me, what I commit with checking the checkbox (DEPENDENCIES are up-to-date. Dash license tool. Committers can open IP issues for restricted libs.) ⇾ i always run the dash tool locally with this command (root of repository):

java -jar org.eclipse.dash.licenses-1.1.0.jar package-lock.json -project automotive.tractusx -summary ./DEPENDENCIES -review -token your-gitlab-token

This checks for new updates and updates the DEPENDENCIES file and also creates automatically a new issue if needed.

[LukasSchmetz]

As part of the core group, LGTM

[reginePrivat]

thanks for your work

[stephanbcbauer]

@ClosedSourcerer LGTM, you can merge it. THX

[FlorianKretschmer]

thanks for the work