-
Notifications
You must be signed in to change notification settings - Fork 10
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
[PURIS FOSS] Enhance UI #916
Comments
Some hints from Release Management (@ther3sa) and Tractus-X Project Lead (@stephanbcbauer)
|
Overview What's the benefit?
What are the Risks/Dependencies ?
Detailed explanation
Proposed improvements
Feature Team
Acceptance Criteria
Criteria 3 Test Cases Test Case: E2E Test_05: Use Dashboard as Customer and Supplier Preconditions The Supplier PURIS (Frontend, Backend, EDC) is running. Expected Result Step 2 Expected Result Supplier Dashboard Partner: "Control Unit Creator Inc." Estimated Time of Completion: Today at 18:00 Expected Result Step 4 Expected Result Step 5 Expected Result Stock View Partner: Semiconductor Supplier Inc. Expected Result Step 7 |
Took over into description and did some formatting |
Overview
Explain the topic in 2 sentences
UI has been reworked to React but still has some bad user experience. Update UI to follow the updated mockup.
What's the benefit?
What are the Risks/Dependencies ?#
Detailed explanation
Current implementation
Proposed improvements
Feature Team
Contributors
Committers
User Stories
Acceptance Criteria
Test Cases
Test Case: E2E Test_05: Use Dashboard as Customer and Supplier
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:
Preconditions
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:
Step 3
Actions
Data
Delivery Information:
Planned Production:
Expected Result
The inserted data is saved to the database and appears in the respective table cells
Step 4
Actions
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:
Expected Result
Step 7
Actions
Expected Result
The data from step 6 is shown in the customer information table
The text was updated successfully, but these errors were encountered: