User Story: Delete User Widget Integration | User Story ID: US-005
Task: Delete User Integration | Task ID: IE-T-005
Role: Integration Engineer
Tech Stack:
Frontend: Angular 10+/ React 16+
Backend: Springboot / .NET WebAPI / Node
Key points to remember:
The id (for frontend) mentioned in the SRS document should not be modified at any cost. Failing to do may fail test cases.
Remember to check the screenshots provided in the SRS document. Strictly adhere to id mapping and attribute mapping. Failing to do may fail test cases.
Strictly adhere to the proper project scaffolding (Folder structure), coding conventions, method definitions and return types.
Adhere strictly to the API endpoints given in the SRS document.
Note:
You should navigate to the admin side dashboard to see the list of users.
Application assumptions:
To navigate to the admin side, you can store a user type as admin in the database with a username and password as admin.
Use admin/admin as the username and password to navigate to the admin dashboard.
Integration Task Details:
Pre-setup: Ensure you have a master branch to integrate the code for a production build.
Once the integration is completely done move the entire code to the main branch repository.
Task 1: Integrate the Delete User Functionality
Your task in this iteration is to integrate the frontend and backend logic of Delete User along with the respective frontend and backend tests.
To do this,
Replace the mock API endpoints in frontend to point to the backend endpoints
Ensure that the user fields are validated successfully
The response should be 200 ok.
aaruwork
commented
2 years ago
Content Description: Epic: User Management | Epic ID: E-001 | Sprint: Sprint-1
User Story: Delete User Widget Integration | User Story ID: US-005
Task: Delete User Integration | Task ID: IE-T-005
Role: Integration Engineer
Tech Stack:
Frontend: Angular 10+/ React 16+
Backend: Springboot / .NET WebAPI / Node
Key points to remember:
The id (for frontend) mentioned in the SRS document should not be modified at any cost. Failing to do may fail test cases. Remember to check the screenshots provided in the SRS document. Strictly adhere to id mapping and attribute mapping. Failing to do may fail test cases. Strictly adhere to the proper project scaffolding (Folder structure), coding conventions, method definitions and return types. Adhere strictly to the API endpoints given in the SRS document.
Note:
You should navigate to the admin side dashboard to see the list of users.
Application assumptions:
To navigate to the admin side, you can store a user type as admin in the database with a username and password as admin.
Use admin/admin as the username and password to navigate to the admin dashboard.
Integration Task Details:
Pre-setup: Ensure you have a master branch to integrate the code for a production build.
Once the integration is completely done move the entire code to the main branch repository.
Task 1: Integrate the Delete User Functionality
Your task in this iteration is to integrate the frontend and backend logic of Delete User along with the respective frontend and backend tests.
To do this,
Replace the mock API endpoints in frontend to point to the backend endpoints Ensure that the user fields are validated successfully The response should be 200 ok.