User Story: Delete User Test | User Story ID: US-005
Task: Delete User Testing | Task ID: FET-T-005
Role: Tester Frontend
Tech Stack: Jasmine/ Karma / Jest / Puppeteer / Cypress
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.
FrontEnd Testing Task Details:
Task 1: Unit Test the Delete User functionality.
Perform unit testing for the Delete User. Refer to the parent SRS document for Ids, method definitions and API endpoint specifications.
Task 2: Visual Regression Testing.
Perform visual regression testing on your application.
Task 3: Perform Cross-browser Testing.
Perform cross-browser testing for the application.
Task 4: End to End Testing.
Create E2E testing with the puppeteer. Refer to the parent SRS document for Ids, method definitions and API endpoint specifications.
Content Description: Epic: User Management | Epic ID: E-001 | Sprint: Sprint-1
User Story: Delete User Test | User Story ID: US-005
Task: Delete User Testing | Task ID: FET-T-005
Role: Tester Frontend
Tech Stack: Jasmine/ Karma / Jest / Puppeteer / Cypress
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.
FrontEnd Testing Task Details:
Task 1: Unit Test the Delete User functionality.
Perform unit testing for the Delete User. Refer to the parent SRS document for Ids, method definitions and API endpoint specifications. Task 2: Visual Regression Testing.
Perform visual regression testing on your application. Task 3: Perform Cross-browser Testing.
Perform cross-browser testing for the application. Task 4: End to End Testing.
Create E2E testing with the puppeteer. Refer to the parent SRS document for Ids, method definitions and API endpoint specifications.