You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
E2E Test_01: Provide Master Data to the application
Assigned Team (proposal): PURIS FOSS
E2E Test Description: A PURIS FOSS administrator uses the interfaces to post material and partner data (HTTP POST Endpoints) to the application so that this data can be used as master data to manually update stock information. This test uses externally available interfaces, that are not used for partners.
-The Customer PURIS (Frontend, Backend, EDC) is running
-The Supplier PURIS (Frontend, Backend, EDC) is running
-Both partners are onboarded to the INT environment
Step 1
Action:
-Open the folder "Test_01" in the postman collection. Trigger run folder.
Expected result:
The folder contains two subfoleders - one for the customer and one for the supplier instance.
All tests passed. The following master data has been created:
Items (Material or Product) involved:
Semiconductor
Name: Semiconductor
Material Number Customer: MNR-7307-AU340474.002
Material Number Supplier: MNR-8101-ID146955.001
Material Number Catena-X: 860fb504-b884-4009-9313-c6fb6cdc776b
Control Unit
Name: Central Control Unit
Material Number Customer: MNR-4177-C
Material Number Supplier: MNR-4177-S
Material Number Catena-X: none https://github.com/eclipse-tractusx/puris/blob/main/local/postman/README.md#customerCustomer
Overall the customer has the following information:
BPNL: BPNL4444444444XX
Name: Control Unit Creator Inc.
Site
BPNS: BPNS4444444444XX
Site Name: Control Unit Creator Production Site
Site Address:
BPNA: BPNA4444444444AA
Street and Number: 13th Street 47
Zip Code, City: 10011 New York
Country: USA
Materials available: Semiconductor
Products available: Control Unit
Material Stock 1:
Partner: Semiconductor Supplier (BPNL1234567890ZZ)
Material: Semiconductor
Quantity: 500 pieces
Blocked: true
Location BPNS: BPNS4444444444XX
Location BPNA: BPNA4444444444AA
Order Position Reference:
Customer Order Number: CNbr-1
Customer Order Position Number: C-Pos-1
Supplier Order Number: SNbr-1 https://github.com/eclipse-tractusx/puris/blob/main/local/postman/README.md#supplierSupplier
Overall the supplier has the following information:
BPNL: BPNL1234567890ZZ
Name: Semiconductor Supplier Inc.
Site 1
BPNS: BPNS1234567890ZZ
Site Name: Semiconductor Supplier Inc. Production Site
Site Address:
BPNA: BPNA1234567890AA
Street and Number: Wall Street 101
Zip Code, City: 10001 New York
Country: USA
Site 2
BPNS: BPNS2222222222SS
Site Name: Semiconductor Supplier Inc. Secondary Site
Site Address:
BPNA: BPNA2222222222AA
Street and Number: Sunset Blvd. 345
Zip Code, City: 90001 Los Angeles
Country: USA
Materials available: none
Products available: Semiconductor
Stocks
Product Stock 1:
Partner: Control Unit Creator Inc. (BPNL4444444444XX)
Material: Semiconductor
Quantity: 100 pieces
Blocked: true
Location BPNS: BPNS1234567890ZZ
Location BPNA: BPNA1234567890AA
Order Position Reference:
Customer Order Number: CNbr-2
Customer Order Position Number: C-Pos-2
Supplier Order Number: SNbr-2
Product Stock 2:
Partner: Control Unit Creator Inc. (BPNL4444444444XX)
Material: Semiconductor
Quantity: 400 pieces
Blocked: false
Order Position Reference:
Customer Order Number: CNbr-2
Customer Order Position Number: C-Pos-2
Supplier Order Number: SNbr-2
E2E Test_02: Create EDC Data Offers
Assigned Team (proposal){}: PURIS FOSS
E2E Test Description: ** Check manually if the Offers have been created for the API assets Item Stock Request and Item Stock Response.
Needed Variables:
EDC_SUPPLIER (externally reachable)
BPNL_SUPPLIER
EDC_CUSTOMER
BPNL_CUSTOMER (externally reachable)
Preconditions
The Customer PURIS (Frontend, Backend, EDC) is running
The Supplier PURIS (Frontend, Backend, EDC) is running
Both partners are onboarded to the INT environment
Note: the assets are either created on the application startup OR during partner creation.
Step 1
Actions
Open the folder "Test_02" in the postman collection. Trigger run folder.
Expected Result
The folder runs the following checks, that should succeed:
Customer: (Check in Customer EDC)
There is a contract definition for the Digital Twin Registry restricted to the Supplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
There is a contract definition for the Part Type Information Submodel restricted to the Spplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
There is a contract definition for the Item Stock Submodel restricted to the Spplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
There is a contract definition for the Planned Production Output Submodel restricted to the Spplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
There is a contract definition for the Short Term Material Demand Submodel restricted to the Spplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
There is a contract definition for the Delivery Information Submodel restricted to the Spplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
Query the Catalog of the Supplier:
There is a contract offer for the Digital Twin Registry.
There is a contract offer for the Part Type Information Submodel (Supplier only).
There is a contract offer for the Item Stock Submodel.
There is a contract offer for the Planned Production Output Submodel.
There is a contract offer for the Short Term Material Demand Submodel.
There is a contract offer for the Delivery Information Submodel.
E2E Test_03: Update Stock (Customer)
Assigned Team * (proposal){}: PURIS FOSS{*}
E2E Test Description: ** A PURIS FOSS user updates the stock information in the frontend for both, a customer (Inbound) and a supplier-related (Outbound) stock.
Needed Variables:
Customer Frontend URL
Preconditions
The Customer PURIS (Frontend, Backend, EDC) is running
Both partners are onboarded to the INT environment
Step 1
Actions
Open the PURIS FOSS Customer application.
Expected Result
The application redirects to the INT central IDP instance.
Step 2
Actions
Login with user and password.
Expected Result
User logged in successfully. The user sees at least the following views:
Stock View
Supplier Dashboard
Step 3
Actions
Open Stock View.
Set the following information
Material or Product = select material
Material = Semiconductor
Quantity = 500 pieces
allocated to partner = Semiconductor Supplier
blocked = false
Site, Address = arbitary
Order Position Refernce fields = empty
Expected Result
The table material stock is updated with the given values (added new stock with given values).
Step 4
Actions
Update the Stock to another quantity (e.g. 550).
Expected Result
The material stock has been updated.
E2E Test_03: Update Stock (Supplier)
Assigned Team (proposal){}: PURIS FOSS
E2E Test Description: ** A PURIS FOSS user updates the stock information in the frontend for both, a customer (Inbound) and a supplier-related (Outbound) stock.
Needed Variables:
-Supplier Frontend URL
Preconditions
-The Customer PURIS (Frontend, Backend, EDC) is running.
-The Supplier PURIS (Frontend, Backend, EDC) is running.
-Both partners are onboarded to the INT environment.
-The Customer has a material on stock that is allocated to the customer.
Step 1
Actions
Open the PURIS FOSS Supplier application.
Expected Result
The application redirects to the INT central IDP instance.
Step 2
Actions
Login with user and password.
Expected Result
User logged in successfully. The user sees at least the following views:
-Stock View
-Supplier Dashboard
Step 3
Actions
Open Stock View.
Select Product > in the right table click "Trigger Update" and check the logs of the Supplier Backend.
Expected Result
The Backend contracts the request api of the customer and sends the request.
The system logs the contract negotiation, agreement and transfer.
The Backend logs the response that updates the partner's stock.
After reloading the Stock view, the partner sees the resceived stock in the frontend.
Step 4
Actions
Open the PURIS FOSS Customer application.
Expected Result
The application redirects to the INT central IDP instance.
Step 5
Actions
Login with user and password.
Expected Result
User logged in successfully. The user sees at least the following views:
-Stock View
-Supplier Dashboard
Step 6
Actions
Open Stock View.
Compare the partner's item stock on supplier side with the product stock allocated to the Semiconductor Supplier.
Expected Result
The information is the same.
E2E Test_05: Use Dashboard as Customer and Supplier
Assigned Team(proposal){{}}: PURIS FOSS
E2E Test Description: ** A supplier updates his data in the dashboard, A customer also updates data in the dashboard. Then both parties update the partner-related data and get the updated information.
Needed Variables:
-Supplier Frontend URL
-Customer Frontend URL
Preconditions
-The Customer PURIS (Frontend, Backend, EDC) is running.
The Supplier PURIS (Frontend, Backend, EDC) is running.
Both partners are onboarded to the INT environment.
Step 1
Actions
Open the PURIS FOSS Supplier application.
Expected Result
The application redirects to the INT central IDP instance.
Step 2
Actions
Login with user and password.
Expected Result
User logged in successfully. The user sees at least the following views:
-Stock View
Supplier Dashboard
Step 3
Actions
Open Dashboard
Select Supplier Tab
Select Material Number "MNR-8101-ID146955.001"
Select Production Site "BPNS1234567890ZZ"
Update the value for Shipments by clicking the "+ Create Delivery" button.
In the resulting popup enter your delivery information.
Hit "save" to save your data in the puris database.
Repeat the same process for Planned Production
Keep the window open for step 7
Data
Delivery Information:
Partner: "Control Unit Creator Inc."
Destination: BPNS4444444444XX
Estimated Time of Departure: Today
Estimated Time of Arrival: Tomorrow
Tracking Number: 1Z9829WDE02128
Incoterm: "EXW"
Quantity: 37
Meaurement Unit: pieces
Customer Order Number: "C-Nbr-1"
Customer Oder Position: "PositionId-01"
Supplier Order Number: "S-Nbr-1"
Planned Production:
Estimated Time of Completion: Today at 18:00
Quantity: 99
Measurement Unit: pieces
Partner: "Control Unit Creator Inc."
Customer Order Number: "C-Nbr-1"
Customer Oder Position: "PositionId-01"
Supplier Order Number: "S-Nbr-1"
Expected Result
The inserted data is saved to the database and appears in the respective table cells
Step 4
Actions
Open the PURIS FOSS Customer application.
Expected Result
The application redirects to the INT central IDP instance.
Step 5
Actions
Login with user and password.
Expected Result
User logged in successfully. The user sees at least the following views:
Stock View
Supplier Dashboard
Step 6
Actions
Open Dashboard
Select Customer Tab
Select Material Number "MNR-7307-AU340474.002"
Select Production Site "BPNS4444444444XX"
Update the value for Material Demands by clicking the "+ Create Demand" button.
In the resulting popup enter your demand information.
Hit "save" to save your data in the puris database.
Select the Supplier Site "BPNS1234567890ZZ" from the Supplier Sites dropdown at the top of the page.
Click the "Refresh" button to trigger an EDC request for new data from your supplier.
Refresh the page and add the filters for Materialnumber, Site and Supplier Site again.
Compare the rows for delivery and planned Production with the data entered in step 3. Detailed Data is shown when the individual cells are clicked.
The added Demand is successfully saved to the database and shown in the table.
The data from step 3 is shown in the supplier information table.
Step 7
Actions
Return to the Puris FOSS Supplier application.
Filter by Customer Site "BPNS4444444444XX"
Click "Refresh" to request updated data from the customer.
Refresh the page and re-add the filters to show the customer information table.
Compare the row Demand with the data you entered in Step 6. For detailed information click the respective cell in the table.
Expected Result
The data from step 6 is shown in the customer information table.
E2E Test_02: Create EDC Data Offers
Assigned Team (proposal){}: PURIS FOSS
E2E Test Description: ** Check manually if the Offers have been created for the API assets Item Stock Request and Item Stock Response.
Needed Variables:
EDC_SUPPLIER (externally reachable)
BPNL_SUPPLIER
EDC_CUSTOMER
BPNL_CUSTOMER (externally reachable)
Preconditions
The Customer PURIS (Frontend, Backend, EDC) is running
The Supplier PURIS (Frontend, Backend, EDC) is running
Both partners are onboarded to the INT environment
Note: the assets are either created on the application startup OR during partner creation.
Step 1
Actions
Open the folder "Test_03" in the postman collection. Trigger run folder.
Expected Result
The folder runs the following checks, that should succeed:
Customer: (Check in Supplier DTR)
There is a ShellDescriptor for the Product.
There are the specific asset ids for the scenario customer. (manufacturer, manufacturerPartId, customerPartId, twinType)
There are the specific asset ids for the non-scenario customer. (manufacturer, manufacturerPartId, customerPartId, twinType)
There is a submodel descriptor for the following submodels:
Part Type Information (semantic id is correct)
Item Stock (semantic id is correct)
Planned Production Output (semantic id is correct)
Short Term Material Demand (semantic id is correct)
Delivery Information (semantic id is correct)
The text was updated successfully, but these errors were encountered:
Master Data
E2E Test_01: Provide Master Data to the application
Needed Variables:
-MATERIAL_NUMBER_CUSTOMER
-MATERIAL_NUMBER_SUPPLIER
-EDC_SUPPLIER
-BPNL_SUPPLIER (externally reachable)
-EDC_CUSTOMER
-BPNL_CUSTOMER (externally reachable)
Preconditions:
-The Customer PURIS (Frontend, Backend, EDC) is running
-The Supplier PURIS (Frontend, Backend, EDC) is running
-Both partners are onboarded to the INT environment
Step 1
Action:
-Open the folder "Test_01" in the postman collection. Trigger run folder.
Expected result:
The folder contains two subfoleders - one for the customer and one for the supplier instance.
All tests passed. The following master data has been created:
Items (Material or Product) involved:
Semiconductor
Name: Semiconductor
Material Number Customer: MNR-7307-AU340474.002
Material Number Supplier: MNR-8101-ID146955.001
Material Number Catena-X: 860fb504-b884-4009-9313-c6fb6cdc776b
Control Unit
Name: Central Control Unit
Material Number Customer: MNR-4177-C
Material Number Supplier: MNR-4177-S
Material Number Catena-X: none
https://github.com/eclipse-tractusx/puris/blob/main/local/postman/README.md#customerCustomer
Overall the customer has the following information:
BPNL: BPNL4444444444XX
Name: Control Unit Creator Inc.
Site
BPNS: BPNS4444444444XX
Site Name: Control Unit Creator Production Site
Site Address:
BPNA: BPNA4444444444AA
Street and Number: 13th Street 47
Zip Code, City: 10011 New York
Country: USA
Materials available: Semiconductor
Products available: Control Unit
Material Stock 1:
Partner: Semiconductor Supplier (BPNL1234567890ZZ)
Material: Semiconductor
Quantity: 500 pieces
Blocked: true
Location BPNS: BPNS4444444444XX
Location BPNA: BPNA4444444444AA
Order Position Reference:
Customer Order Number: CNbr-1
Customer Order Position Number: C-Pos-1
Supplier Order Number: SNbr-1
https://github.com/eclipse-tractusx/puris/blob/main/local/postman/README.md#supplierSupplier
Overall the supplier has the following information:
BPNL: BPNL1234567890ZZ
Name: Semiconductor Supplier Inc.
Site 1
BPNS: BPNS1234567890ZZ
Site Name: Semiconductor Supplier Inc. Production Site
Site Address:
BPNA: BPNA1234567890AA
Street and Number: Wall Street 101
Zip Code, City: 10001 New York
Country: USA
Site 2
BPNS: BPNS2222222222SS
Site Name: Semiconductor Supplier Inc. Secondary Site
Site Address:
BPNA: BPNA2222222222AA
Street and Number: Sunset Blvd. 345
Zip Code, City: 90001 Los Angeles
Country: USA
Materials available: none
Products available: Semiconductor
Stocks
Product Stock 1:
Partner: Control Unit Creator Inc. (BPNL4444444444XX)
Material: Semiconductor
Quantity: 100 pieces
Blocked: true
Location BPNS: BPNS1234567890ZZ
Location BPNA: BPNA1234567890AA
Order Position Reference:
Customer Order Number: CNbr-2
Customer Order Position Number: C-Pos-2
Supplier Order Number: SNbr-2
Product Stock 2:
Partner: Control Unit Creator Inc. (BPNL4444444444XX)
Material: Semiconductor
Quantity: 400 pieces
Blocked: false
Order Position Reference:
Customer Order Number: CNbr-2
Customer Order Position Number: C-Pos-2
Supplier Order Number: SNbr-2
E2E Test_02: Create EDC Data Offers
Needed Variables:
Preconditions
Note: the assets are either created on the application startup OR during partner creation.
Step 1
Actions
Open the folder "Test_02" in the postman collection. Trigger run folder.
Expected Result
The folder runs the following checks, that should succeed:
Customer: (Check in Customer EDC)
There is a contract definition for the Digital Twin Registry restricted to the Supplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
There is a contract definition for the Part Type Information Submodel restricted to the Spplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
There is a contract definition for the Item Stock Submodel restricted to the Spplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
There is a contract definition for the Planned Production Output Submodel restricted to the Spplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
There is a contract definition for the Short Term Material Demand Submodel restricted to the Spplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
There is a contract definition for the Delivery Information Submodel restricted to the Spplier BPNL. (has dcat:type, cx-common:vesion, asset:prop:type)
Query the Catalog of the Supplier:
There is a contract offer for the Digital Twin Registry.
There is a contract offer for the Part Type Information Submodel (Supplier only).
There is a contract offer for the Item Stock Submodel.
There is a contract offer for the Planned Production Output Submodel.
There is a contract offer for the Short Term Material Demand Submodel.
There is a contract offer for the Delivery Information Submodel.
E2E Test_03: Update Stock (Customer)
Needed Variables:
Preconditions
Step 1
Actions
Open the PURIS FOSS Customer application.
Expected Result
The application redirects to the INT central IDP instance.
Step 2
Actions
Login with user and password.
Expected Result
User logged in successfully. The user sees at least the following views:
Step 3
Actions
Open Stock View.
Set the following information
Material or Product = select material
Material = Semiconductor
Quantity = 500 pieces
allocated to partner = Semiconductor Supplier
blocked = false
Site, Address = arbitary
Order Position Refernce fields = empty
Expected Result
The table material stock is updated with the given values (added new stock with given values).
Step 4
Actions
Update the Stock to another quantity (e.g. 550).
Expected Result
The material stock has been updated.
E2E Test_03: Update Stock (Supplier)
Needed Variables:
-Supplier Frontend URL
Preconditions
-The Customer PURIS (Frontend, Backend, EDC) is running.
-The Supplier PURIS (Frontend, Backend, EDC) is running.
-Both partners are onboarded to the INT environment.
-The Customer has a material on stock that is allocated to the customer.
Step 1
Actions
Open the PURIS FOSS Supplier application.
Expected Result
The application redirects to the INT central IDP instance.
Step 2
Actions
Login with user and password.
Expected Result
User logged in successfully. The user sees at least the following views:
-Stock View
-Supplier Dashboard
Step 3
Actions
Open Stock View.
Select Product > in the right table click "Trigger Update" and check the logs of the Supplier Backend.
Expected Result
Step 4
Actions
Open the PURIS FOSS Customer application.
Expected Result
The application redirects to the INT central IDP instance.
Step 5
Actions
Login with user and password.
Expected Result
User logged in successfully. The user sees at least the following views:
-Stock View
-Supplier Dashboard
Step 6
Actions
Open Stock View.
Compare the partner's item stock on supplier side with the product stock allocated to the Semiconductor Supplier.
Expected Result
The information is the same.
E2E Test_05: Use Dashboard as Customer and Supplier
Needed Variables:
-Supplier Frontend URL
-Customer Frontend URL
Preconditions
-The Customer PURIS (Frontend, Backend, EDC) is running.
Step 1
Actions
Open the PURIS FOSS Supplier application.
Expected Result
The application redirects to the INT central IDP instance.
Step 2
Actions
Login with user and password.
Expected Result
User logged in successfully. The user sees at least the following views:
-Stock View
Step 3
Actions
Data
Delivery Information:
Partner: "Control Unit Creator Inc."
Destination: BPNS4444444444XX
Estimated Time of Departure: Today
Estimated Time of Arrival: Tomorrow
Tracking Number: 1Z9829WDE02128
Incoterm: "EXW"
Quantity: 37
Meaurement Unit: pieces
Customer Order Number: "C-Nbr-1"
Customer Oder Position: "PositionId-01"
Supplier Order Number: "S-Nbr-1"
Planned Production:
Estimated Time of Completion: Today at 18:00
Quantity: 99
Measurement Unit: pieces
Partner: "Control Unit Creator Inc."
Customer Order Number: "C-Nbr-1"
Customer Oder Position: "PositionId-01"
Supplier Order Number: "S-Nbr-1"
Expected Result
The inserted data is saved to the database and appears in the respective table cells
Step 4
Actions
Open the PURIS FOSS Customer application.
Expected Result
The application redirects to the INT central IDP instance.
Step 5
Actions
Login with user and password.
Expected Result
User logged in successfully. The user sees at least the following views:
Step 6
Actions
Data
Material Demand:
Partner: Semiconductor Supplier Inc.
Expected Supplier Location: "BPNS1234567890ZZ"
Quantity: 99
Measurement Unit: pieces
Day: today
Demand Category: "Default"
Expected Result
The added Demand is successfully saved to the database and shown in the table.
The data from step 3 is shown in the supplier information table.
Step 7
Actions
Expected Result
The data from step 6 is shown in the customer information table.
E2E Test_02: Create EDC Data Offers
Needed Variables:
Preconditions
Note: the assets are either created on the application startup OR during partner creation.
Step 1
Actions
Open the folder "Test_03" in the postman collection. Trigger run folder.
Expected Result
The folder runs the following checks, that should succeed:
Customer: (Check in Supplier DTR)
There is a ShellDescriptor for the Product.
There are the specific asset ids for the scenario customer. (manufacturer, manufacturerPartId, customerPartId, twinType)
There are the specific asset ids for the non-scenario customer. (manufacturer, manufacturerPartId, customerPartId, twinType)
There is a submodel descriptor for the following submodels:
Part Type Information (semantic id is correct)
Item Stock (semantic id is correct)
Planned Production Output (semantic id is correct)
Short Term Material Demand (semantic id is correct)
Delivery Information (semantic id is correct)
The text was updated successfully, but these errors were encountered: