Test Cases

Reports (Inventory Management)

Test Id

Sub Feature/ Use Case

Test Ideas

Test Type

Test Data

Steps to be executed

Expected Result

QA Review

Dev Review

PM Review

Actual result

Dev Status

QA Status

HLM/2742/01

Reports (Inventory Management)

Check whether the Warehouse manager have a View Reports button on the Home screen

1.Launch the application 2.Enter credentials 3.Click on Login

The Warehouse manager should have a View Reports button on the Home screen

PASS

HLM/2742/02

Reports (Inventory Management)

Check if the Warehouse manager can view reports offline

Functional

1.Launch the application 2.Enter credentials 3.Click on Login

The Warehouse manager should be able to view the reports offline

PASS

HLM/2742/03

Reports (Inventory Management)

Check whether the page navigates to the view reports screen when clicking on the View reports button

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on View Reports button

The page should navigate to the view reports screen when clicking on the View reports button

PASS

HLM/2742/04

Reports (Inventory Management)

Check if the view reports screen has the following cards and are clickable 1. Record Stock Receipt 2. Record stock issued 3.Stock Returned 4. Stock Damaged 5. Stock Loss 6. Stock Reconciliation

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on View Reports button

The view reports screen should have the following cards and should be clickable 1. Record Stock Receipt 2. Record stock issued 3.Stock Returned 4. Stock Damaged 5. Stock Loss 6. Stock Reconciliation

PASS

HLM/2742/05

Reports (Inventory Management)

Check if the user can see the tabular reports for all the stock transactions (inflows and outflows) and stock reconciliation by clicking on the arrow button placed next to every transaction

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on View Reports button 5. Click on arrow button next to the respective transaction

The user should be able to see the tabular reports for all the stock transactions (inflows and outflows) and stock reconciliation by clicking on the arrow button placed next to every transaction

PASS

HLM/2742/06

Reports (Inventory Management)

Check if the report appears in a tabular representation of the data and is scrollable, both vertically and horizontally,

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on View Reports button 5. Click on arrow button next to the respective transaction

The report should appear in a tabular representation of the data and should be scrollable, both vertically and horizontally,

PASS

HLM/2742/07

Reports (Inventory Management)

Check if the following columns are displayed on these reports 1. Record Stock Receipt - Date, Quantity received, Received from 2. Record stock issued - Date, Quantity received, Received from 3.Stock Returned- Date, Quantity returned, Returned from 4. Stock Damaged - Date, Quantity damaged, Received from, Danaged During 5. Stock Loss - Date, Quantity lost, Received from, Lost during 6. Stock Reconciliation - Stock received, stock issued, stock returned, stock lost, stock damaged, stock on hand, manual stock count

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on View Reports button 5.Click on Record Stock Receipt

The following columns should be displayed on these respective reports 1. Record Stock Receipt - Date, Quantity received, Received from 2. Record stock issued - Date, Quantity received, Received from 3.Stock Returned- Date, Quantity returned, Returned from 4. Stock Damaged - Date, Quantity damaged, Received from, Danaged During 5. Stock Loss - Date, Quantity received, Received from, Lost during 6. Stock Reconciliation - Stock received, stock issued, stock returned, stock lost, stock damaged, stock on hand, manual stock count

PASS

HLM/2742/08

Reports (Inventory Management)

Check if columns displayed on reports are according to the type of transaction

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on View Reports button 5. Click on arrow button next to the respective transaction

The columns displayed on reports should be according to the type of transaction

PASS

HLM/2742/09

Reports (Inventory Management)

Check if the data on the reports are reflected appropriately based on the inflows and outflows of the data

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on View Reports button 5. Click on arrow button next to the respective transaction

The data on the reports should be reflected appropriately based on the inflows and outflows of the data

PASS

HLM/2742/10

Reports (Inventory Management)

Check if the Back to Home Button is visible on the Report screens

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on View Reports button 5. Click on arrow button next to the respective transaction

The Back to Home Button should be visible on the Report screens

PASS

HLM/2742/11

Reports (Inventory Management)

Check if clicking on the Back to Home Button page navigates to the home screen

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on View Reports button 5. Click on arrow button next to the respective transaction 6. Click on Back to Home button

By clicking on the Back to Home Button the page should navigates to the home screen

PASS

HLM/2742/12

Reports (Inventory Management)

Check whether the back button component is present on all the screens of the mobile application, and it should be visible and clickable

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on View Reports button 5. Click on arrow button next to the respective transaction 6. Click on Back button

The back button should be present on all the screens of the mobile application, and it should be visible and clickable

PASS

HLM/2742/13

Reports (Inventory Management)

Check whether a appropriate message is displayed if there are no records

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on View Reports button 5. Click on arrow button next to the respective transaction

"No records available" message should be displayed if there are no records on the report screens

PASS

HLM/2742/14

Reports (Inventory Management)

Check if the view reports option is present for warehouse manager only.

Functional

1.Launch the application 2.Enter credentials 3.Click on Login

The view reports option should be only availabe for warehouse manager.

PASS

HLM/2742/15

Reports (Inventory Management)

Check if the sync changes any data on the reports

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4. Create stock related data 5. Click on sync data 6.Click on View Reports button and verify the data

The sync should not change any data on the reports

PASS

HLM/2742/16

Reports (Inventory Management)

Create stock-related data and check if it appears in reports regardless of whether the data is synced or not.

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4. Create stock related data 5.Click on View Reports button and verify the data

Regardless of whether the data is synced or not, the created data should appear accurately in the reports.

PASS

Update User

Test Id

Sub Feature/ Use Case

Test Ideas

Test Type

Test Data

Steps to be executed

Expected Result

QA Review

Dev Review

PM Review

Actual result

Dev Status

QA Status

HLM/1757/01

Update user

Check if the Edit Employee Details option is available on the Details page when clicking on Take Action button

The Edit Employee Details option should be available on the Details page when clicked on Take Action button

PASS

HLM/1757/02

Update user

Check if the page navigates to Edit employee screen when clicked on Edit Employee Details button

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin 3) Click on inbox on HRMS card on the home page 4) Click on the user name to which the updates has to be done 5) Click on Take action button on Details page 6) Click on Edit Employe Details button

The page should navigate to Edit Employe screen when clicked on Edit Employee Details button

PASS

HLM/1757/03

Update user

Check if the user details can edit in bulk on the edit screen

The user details should be able to edit in bulk on the edit screen

HLM/1757/04

Update user

Check whether the user can edit all the details except the User's Name

The user should be able to edit all the details except the User's Name on the Edit Employe screen

PASS

HLM/1757/05

Update user/ Edit Campaign Assignment

Check if the Save button is visible and clickable on Edit Employee screen and Edit Campaign Screen

Functional

The save button should be visible and clickable on Edit Employee screen and Edit Campaign screen

PASS

HLM/1757/06

Update user/ Edit Campaign Assignment

Check whether all the edited details are updated appropriately and are visible on Details screen

Functional

All the edited details should be updated appropriately and should be visible on Details screen

PASS

HLM/1757/07

Edit Campaign Assignment

Check if the Edit Campaign Assignment option is available on the Details page when clicking on Take Action button

The Edit Campaign Assignment option should be available on the Details page when clicked on Take Action button

PASS

HLM/1757/08

Edit Campaign Assignment

Check if the page navigates to Edit Campaign screen when clicked on Edit Campaign Assignment button

Functional

The page should navigate to Edit Campaign screen when clicked on Edit Campaign Assignment button

PASS

HLM/1757/09

Edit Campaign Assignment

Check whether the user can edit all the details on Edit Campaign screen

The user should be able to edit all the on Edit Campaign Screen

PASS

Deactivating user

Test Id

Sub Feature/ Use Case

Test Ideas

Test Type

Test Data

Steps to be executed

Expected Result

QA Review

Dev Review

PM Review

Actual result

Dev Status

QA Status

HLM/1758/01

Deactivating user

Check if we get 3 options when we click on "Take Action" while being in the user details screen.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active user in the "Inbox" view. 6) Click on the "Take Action" button.

PASS

HLM/1758/02

Deactivating user

Check if we get 3 options when we click on "Take Action" while being in the user details screen are clickable.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active user in the "Inbox" view. 6) Click on the "Take Action" button.

3) We should have option called "Inbox" on the "User Management" card. 4) We should see a list of users and their status. 5) The user details screen is loaded with all appropriate user details. 6) We should see 3 options "Edit Campaign Assignment", "Edit Employee Details" and "Deactivate Employee" and each of these options are clickable.

PASS

HLM/1758/03

Deactivating user

Check if the reason for deactivation is a dropdown and is configurable in the deactivate employee screen.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active user in the "Inbox" view. 6) Click on the "Take Action" button. 7) Click on "Deactivate Employee".

PASS

HLM/1758/04

Deactivating user

Check if the effective date is prepopulated in the deactivate employee screen.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active user in the "Inbox" view. 6) Click on the "Take Action" button. 7) Click on "Deactivate Employee".

PASS

HLM/1758/05

Deactivating user

Check if the effective date is editable in the deactivate employee screen.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active user in the "Inbox" view. 6) Click on the "Take Action" button. 7) Click on "Deactivate Employee".

HLM/1758/06

Deactivating user

Check if reason for deactivation and effective date fields are marked as mandatory in the deactivate employee screen.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active user in the "Inbox" view. 6) Click on the "Take Action" button. 7) Click on "Deactivate Employee".

PASS

HLM/1758/07

Deactivating user

Check if the user status changes from active to inactive when we deactivate a user.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active user in the "Inbox" view. 6) Click on the "Take Action" button. 7) Deactivate an employee. 8) Validate the status of the employee in the inbox view.

PASS

HLM/1758/08

Deactivating user

Check if the status of the deactivated user is synced to the mobile app during login.

Functional

1) Launch the mobile application and login as FLW. 2) Navigate to the application URL. Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on the active FLW user (used in step 1 to login to the mobile app) in the "Inbox" view. 6) Click on the "Take Action" button. 7) Deactivate an employee. 8) Validate the status of the employee in the inbox view. 9) Logout of the mobile app and login with the same FLW credentials.

1) User should be able tp login to the mobile app and he should be shown the home screen. He can perform registration and service delivery as well. 3) We should have option called "Inbox" on the "User Management" card. 4) We should see a list of users and their status. 5) The user details screen is loaded with all appropriate user details. 6) We should see 3 options "Edit Campaign Assignment", "Edit Employee Details" and "Deactivate Employee". 7) Selected user gets deactivated. 8) We see that the user status is inactive in the inbox view. 9) We should not be able to login to the mobile app and we should be getting an appropriate error message.

PASS

HLM/1758/09

Deactivating user

Check if we get error message or not if we miss any / all of the mandatory fields in the deactivate employee screen.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active user in the "Inbox" view. 6) Click on the "Take Action" button. 7) Deactivate an employee and do not fill in any mandatory data.

PASS

HLM/1758/10

Deactivating user

Check if we get a confirmation message when we deactivate an employee.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active user in the "Inbox" view. 6) Click on the "Take Action" button. 7) Deactivate an employee by filling in all of "Reason for Deactivation", "Effective Date" , "Order No" and "Remarks".

PASS

HLM/1758/11

Deactivating user

Check if I am unable to deactivate a system admin user when I am logged as a national/provincial/district supervisor, helpdesk user.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active system admin user in the "Inbox" view. 6) Click on the "Take Action" button.

HLM/1758/12

Deactivating user

Check if I am able to deactivate a system admin user when I am logged as a system admin user.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active system admin user in the "Inbox" view. 6) Click on the "Take Action" button. 7) Deactivate an employee.

HLM/1758/13

Deactivating user

Check if the deactivate employee screen is as per the FIGMA requirements.

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active user in the "Inbox" view. 6) Click on the "Take Action" button. 7) Click on "Deactivate Employee". Validate if the UI design is as per the figma.

PASS

HLM/1758/14

Deactivating user

Check that when we click on "Go Back To Home" in the confirmation screen for deactivating a user, we are shown the user details screen

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, validate if we have option called "Inbox" on the "User Management" card. 4) Click on the "Inbox" link. 5) Click on any of the active user in the "Inbox" view. 6) Click on the "Take Action" button. 7) Click on "Deactivate Employee". 8) On the confirmation screen, click on "Go Back To Home".

PASS

Progress Bar

HLM/931/01

Progress bar

Check whether a distributor can see a progress bar on home page

1.Launch the application 2.Enter credentials 3.Click on Login

The distributors should have a progress bar displayed on home page

HLM/931/02

Progress bar

Check if the progress bar displays the daily targets assigned to the user and the records created against that target at a project level

1.Launch the application 2.Enter credentials 3.Click on Login

The progress bar should display the daily targets assigned to the user and the records created against that target at a project level

HLM/931/03

Progress bar

Check if there is an information text above the progress bar stating how much more is required to achieve the target

1.Launch the application 2.Enter credentials 3.Click on Login

An information text above the progress bar should be displayed stating how much more is required to achieve the target

HLM/931/04

Progress bar

Check whether all the details are updated according to the targets achieved by the user (online and offline)

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4. Perform an assigned target 5. Verify the progress bar

All the details should be updated according to the targets achieved by the user 1. Targets required to achieve 2. Completed targets 3. Progress bar

HLM/931/05

Progress bar

Check if the values are reset to zero at 00:00 hours everyday.

Functional

1.Launch the application 2.Enter credentials 3.Click on Login

The values sould be reset to zero at 00:00 hours everyday.

HLM/931/06

Progress bar

Check for the targets not specified

1.Launch the application 2.Enter credentials 3.Click on Login

There should be default targets set

HLM/931/07

Progress bar

Check to see if the information of a deleted household have been removed from the progress bar.

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4. Perform an assigned target and delete that household 5. Verify the progress bar

If a household is created and deleted later on, that household must be removed from the progress bar as well

Search Users

Test Id

Sub Feature/ Use Case

Test Ideas

Test Type

Test Data

Steps to be executed

Expected Result

QA Review

Dev Review

PM Review

Actual result

Dev Status

QA Status

HLM/1759/01

Search Users

Check if we have the user management card has an option to search for the users. Check for all of system admin, national/provincial/district supervisor, helpdesk user roles.

Functional

We should have option called "Search User" on the "User Management" card.

PASS

HLM/1759/02

Search Users

Check if we click on search "Search User" option in the user management card we see the "Search Page". Check for all of system admin, national/provincial/district supervisor, helpdesk user roles.

Functional

3) "Search Page" should be loaded. We should see all the user data registered in the system both active and inactive.

PASS

HLM/1759/03

Search Users

Search by username

Functional

3) "Search Page" should be loaded. We should see all the user data registered in the system both active and inactive. 4) The "Search Page" should be loaded with all relevant data specific to the username being searched for. The result should have only one row as the username is unique.

PASS

HLM/1759/04

Search Users

Search by mobile number

Functional

PASS

HLM/1759/05

Search Users

Search by name

Functional

3) "Search Page" should be loaded. We should see all the user data registered in the system both active and inactive. 4) The "Search Page" should be loaded with all relevant data specific to the name being searched for. The result may include multiple data pertaining to the filtered name.

PASS

HLM/1759/06

Search Users

Filter search by campaign

Functional

PASS

HLM/1759/07

Search Users

Filter search by role

Functional

4) We should see all the user data registered in the system both active and inactive. 5) When we filter the data specific to a role, we should see data of users who are associated to that role only.

PASS

HLM/1759/08

Search Users

Filter search by employment status

Functional

4) We should see all the user data registered in the system both active and inactive. 5) When we filter the data specific to only inactive users, we should see only data for inactive users.

PASS

HLM/1759/09

Search Users

Search with valid combination of username and mobile number

Functional

The "Search Page" should be loaded with all relevant data specific to the combination of valid username and valid mobile number being searched for. The result should have only one row as the username is unique.

PASS

HLM/1759/10

Search Users

Search with valid combination of name and mobile number

Functional

The "Search Page" should be loaded with all relevant data specific to the combination of valid name and valid mobile number being searched for.

PASS

HLM/1759/11

Search Users

Search with valid combination of name and username

Functional

The "Search Page" should be loaded with all relevant data specific to the combination of valid username and valid name being searched for. The result should have only one row as the username is unique.

PASS

HLM/1759/12

Search Users

Check the clear search functionality

Functional

3) We should see all the user data registered in the system both active and inactive. 4) The "Search Page" should be loaded with all relevant data specific to the username being searched for. The result should have only one row as the username is unique. 5) Once we click on "Clear Search", we should see all the user data registered in the system both active and inactive.

PASS

HLM/1759/13

Search Users

Check if provincial supervisor of campaign A can search for users only under campaign A.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of provincial supervisor who is associated with campaign A. 3) On the home screen, click on the option called "Search User" on the "User Management" card. 4) Validate if "By Campaign" dropdown has only one option that is campaign A. 5) Search for a valid user by either of username / mobile number / name who is associated with campaign A. 6) Search for a valid user by using a combination of username and mobile number , mobile number and name, name and username who is associated with campaign A. 7) Search for a valid user by either of username / mobile number / name who is associated with campaign B.

3) We should see all the user data registered in the system both active and inactive, associated only to campaign A. 4) The "By Campaign" dropdown has only one option called campaign A. 5) We should see only users who are searched by either of username / mobile number / name who is associated with campaign A. 6) We should see only users who are searched by combination of username and mobile number , mobile number and name, name and username who is associated with campaign A. 7) We should not get any search results.

PASS

HLM/1759/14

Search Users

Check if district supervisor of campaign A can search for users only under campaign A.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of district supervisor who is associated with campaign A. 3) On the home screen, click on the option called "Search User" on the "User Management" card. 4) Validate if "By Campaign" dropdown has only one option that is campaign A. 5) Search for a valid user by either of username / mobile number / name who is associated with campaign A. 6) Search for a valid user by using a combination of username and mobile number , mobile number and name, name and username who is associated with campaign A. 7) Search for a valid user by either of username / mobile number / name who is associated with campaign B.

PASS

HLM/1759/15

Search Users

Check if system admin / helpdesk user can search for a user irrespective of campaign they are associated with

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin / helpdesk user. 3) On the home screen, click on the option called "Search User" on the "User Management" card. 4) Search for a valid user by either of username / mobile number / name who is associated with campaign A. 5) Search for a valid user by either of username / mobile number / name who is associated with campaign B.

3) We should see all the user data registered in the system both active and inactive, irrespective of their associated campaign. 4) We should see only users who are searched by either of username / mobile number / name who is associated with campaign A. 5) We should see only users who are searched by either of username / mobile number / name who is associated with campaign B.

HLM/1759/16

Search Users

Search Page components

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) On the home screen, click on the option called "Search User" on the "User Management" card. 4) Validate if the following components are present for the Search section a) Text fields : Employee Name, Mobile Number, Username b) Button: Search c) Link: Clear Search 5) Validate if the following components are present for the Filter section a) Filter categories: By Campaign, By Role b) Employment Status: Active checkbox and Inactive checkbox 6) Validate if the following components are present for the results section a) Columns: Username, Name, No. of Roles, Campaign Assigned, Department, Employment Status. b) Links: Against the data in each row of the table for the Username column c) Rows per page d) Pagination e) Page Navigation icons

3) We should see all the user data registered in the system both active and inactive, irrespective of their associated campaign. 4) We see that the following components are present for the Search section a) Text fields : Employee Name, Mobile Number, Username b) Button: Search c) Link: Clear Search 5) We see that the following components are present for the Filter section a) Filter categories: By Campaign, By Role b) Employment Status: Active checkbox and Inactive checkbox 6) We see that the following components are present for the results section a) Columns: Username, Name, No. of Roles, Campaign Assigned, Department, Employment Status. b) Links: Against the data in each row of the table for the Username column c) Rows per page d) Pagination e) Page Navigation icons

PASS

HLM/1759/17

Search Users

Number of rows per page

Functional

3) We should see all the user data registered in the system both active and inactive, irrespective of their associated campaign. 4) We see that the number of rows for the results can be changed by selecting different options from the "Rows" dropdown.

PASS

HLM/1759/18

Search Users

Navigation in results

Functional

3) We should see all the user data registered in the system both active and inactive, irrespective of their associated campaign. 4) We see that the navigation functionality is working fine by clicking on the following options: a) Next page: navigates from current page to next page in the results b) Previous page: navigates from current page to previous page in the results c) First page: navigates from current page to first page in the results d) Last page: navigates from current page to last page in the results

PASS

HLM/1759/19

Search Users

Search with no results

Functional

3) "Search Page" should be loaded. We should see all the user data registered in the system both active and inactive. 4) The "Search Page" should be loaded with no results.

PASS

HLM/1759/20

Search Users

Refresh icon

Functional

4) We should see all the user data registered in the system both active and inactive. 5) When we filter the data specific to a campaign, we should see data of users who are associated to that campaign only. 6) We see that the earlier selected filter is getting cleared. Also we see that the data is seen as in step 4.

PASS

Complaint Actions

Test Id

Sub Feature/ Use Case

Test Ideas

Test Type

Test Data

Steps to be executed

Expected Result

QA Review

Dev Review

PM Review

Actual result

Dev Status

QA Status

HLM/1736/01

Complaint Actions

Check if the complaint summary screen has the complaint details that include 1. Complaint Number 2. Complaint type 3. Complaint Date 4. Complainant name 5. Area 6. Contact number 7. Status 8. Complaint Description

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button

The complaint summary screen should have the complaint details that include 1. Complaint Number 2. Complaint type 3. Complaint Date 4. Complainant name 5. Area 6. Contact number 7. Status 8. Complaint Description

PASS

HLM/1736/02

Complaint Actions

Check if the complaint summary screen has the complaint timeline that includes 1. Assignee details 2. Assigned Date 3. Comments

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button

The complaint summary screen should have the complaint timeline that includes 1. Assignee details 2. Assigned Date 3. Comments

PASS

HLM/1736/03

Complaint Actions

Check if the timeline has the assignee details that include 1. Assignee name 2. Assignee contact number

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button

The timeline should have the assignee details that include 1. Assignee name 2. Assignee contact number

PASS

HLM/1736/04

Complaint Actions

Check if the complaint summary screen has a Take Action button and is functional

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button

The complaint summary screen should have a Take Action button and it should be functional

PASS

HLM/1736/05

Complaint Actions

Check if the details are correct on the mobile web by creating a complaint and syncing from the mobile web

Functional

1.Lauch the application on mobile 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on File complaint Button 6. Select complaint type click on next 7. Enter the complant details 8. Check the Submit button 9. Click on Submit button on confirmation screen 10. Sync the data 11. Navigate to the application URL on mobile 12. Enter credentials and login 13. Click on the complaint on inbox and verify the details

The details as seen in the mobile web should be the same which was entered in the mobile app.

PASS

HLM/1736/06

Complaint Actions

Check if the status is getting synced by Assigning a complaint to another user and then resolving it

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on Assign complaint and choose the user 8. Click on Assign 9. Verify the status 10. Login to L2 user 11. Click on the complaint from inbox 12. Click on Take action button 13. Click on resolve complaint 14. Click on resolve 15. Login to the mobile web and check the status

The status should get synced by Assigning a complaint to another user and then resolving it

PASS

HLM/1736/07

Complaint Actions

Check if the status is getting synced by Assigning complaint to another user and then rejecting it

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on Assign complaint and choose the user 8. Click on Assign 9. Check the status 10. Login to L2 user 11. Click on the complaint from inbox 12. Click on Take action button 13. Click on reject complaint and select the reason 14. Click on Reject 15. Login to the mobile web and check the status

The status should get synced by Assigning a complaint to another user and then rejecting it

PASS

HLM/1736/08

Complaint Actions

Check if the user can see the take action button after a complaint is resolved

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on Resolve complaint 8. Click on resolve button

The user should not see the take action button after a complaint is resolved

PASS

HLM/1736/09

Complaint Actions

Check for creating a complaint and syncing it from mobile, later rejecting the complaint on the web and check details on mobile, again sync on mobile and see the status on mobile

Functional

1.Launch the mobile app. 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on File complaint Button 6. Select complaint type click on next 7. Enter the complaint details 8. Check the Submit button 9. Click on Submit button on confirmation screen 10. Sync the data 11. Navigate to the application URL on mobile browser 12. Enter credentials and login 13. Click on the complaint on inbox 14. Click on Take action button 15. Click on Reject complaint and select the reason 16. Click on Reject 17. Launch the mobile app and check the status 18. Sync data and verify the status

The status should get synced appropriately for creating and rejecting a complaint

PASS

HLM/1736/10

Complaint Actions

Check for creating a complaint & sync from mobile. Assign to L2 on the web and check details on mobile, again sync on mobile and see the status on mobile.

Functional

1.Launch the mobile app. 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on File complaint Button 6. Select complaint type click on next 7. Enter the complaint details 8. Check the Submit button 9. Click on Submit button on confirmation screen 10. Sync the data 11. Navigate to the application URL on mobile browser. 12. Enter credentials and login 13. Click on the complaint on inbox 14. Click on Take action button 15. Click on Assign complaint and select the assignee 16. Click on Assign 17. Launch the mobile app and check the status 18. Sync data and verify the status

The status should get synced appropriately for creating and assigning a complaint

PASS

HLM/1736/11

Complaint Actions

Check if the user can see the take action button after a complaint is Rejected

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on Reject complaint and select the reason for rejection 8. Click on reject button

The user should not see the take action button after a complaint is rejected

PASS

HLM/1736/12

Complaint Actions

Check for the details on the web view by raising a complaint on mobile and canceling it.

Functional

The complaint details should not be available

PASS

HLM/1736/13

Complaint Actions

Check if L2 support user can assign the complaint back to the Helpdesk user

Functional

1.Navigate to the application URL 2.Enter credentials of L2 support user 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Assign the complaint back to helpdesk user

The L2 support user should be able to assign the complaint back to the Helpdesk user

PASS

HLM/1736/14

Complaint Actions

Check if the user is able to click on the open button on complaint card

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button

The user should be able to click on the open button on complaint card

PASS

HLM/1736/15

Complaint Actions

Check if the page navigates to the complaint summary screen when clicking on the open button

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button

The page should navigate to the complaint summary screen when clicking on the open button

PASS

HLM/1736/16

Complaint Actions

Check if the following options are available clicking on the Take action button and are clickable 1. Resolve Complaint 2. Assign complaint 3. Reject Complaint

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button

The following options should be available clicking on the Take action button and should clickable 1. Resolve Complaint 2. Assign complaint 3. Reject Complaint

PASS

HLM/1736/17

Complaint Actions

Check whether clicking on the assign complaint button the Assign complaint screen appears, that includes following fields 1. Date 2. Assign to 3. Additional commands

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on assign complaint button

By clicking on the assign complaint button the Assign complaint screen should appear, that should include following fields 1. Date 2. Assign to 3. Additional commands

PASS

HLM/1736/18

Complaint Actions

Check if the date is auto-captured and is non-editable.

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on assign complaint button

The date should be auto-captured and must be non-editable.

PASS

HLM/1736/19

Complaint Actions

Check if Assign to is a drop down field that shows the assignees list

The Assign to field should be a drop down and has to show the assignees list

PASS

HLM/1736/20

Complaint Actions

Check if Assign button is visible and clickable on Assign complaint popup

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on assign complaint button 8. Choose the assignee and click on Assign button

The Assign button should be visible and clickable on Assign complaint popup

PASS

HLM/1736/21

Complaint Actions

Check if the assign button is enabled all the time

The assign button should be enabled all the time, and should throw an error if the mandatory fields are not entered

PASS

HLM/1736/22

Complaint Actions

Check whether a toaster message appears with the text " Complaint Assigned successfully" when clicking on the assign button

Functional

A toaster message with the text " Complaint Assigned successfully" should appear when clicking on the assign button

PASS

HLM/1736/23

Complaint Actions

Check if the complaint is assigend to the selected assignee

Functional

The complaint should be assigend to the selected assignee

PASS

HLM/1736/24

Complaint Actions

Check if the complaint status changes to ‘Assigned to L2’ when the user assigns the complaint

Functional

The complaint status should change to ‘Assigned to L2’ when the user assigns the complaint

PASS

HLM/1736/25

Complaint Actions

Check whether clicking on the resolve complaint button the resolve complaint screen appears, that includes Additional comments field

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on Resolve complaint button

By clicking on the resolve complaint button the resolve complaint screen should appear, that should include Additional comments field

PASS

HLM/1736/26

Complaint Actions

Check if resolve button is visible and clickable on resolve complaint screen

Functional

The resolve button should be visible and clickable on resolve complaint screen

PASS

HLM/1736/27

Complaint Actions

Check whether a toaster message appears with the text " Complaint Resolved successfully" when clicking on the Resolve button

Functional

A toaster message with the text " Complaint Resolved successfully" should appear when clicking on the resolve button

PASS

HLM/1736/28

Complaint Actions

Check if the complaint status changes to ‘resolved’ when the user clicks on resolve complaint and the complaint is resolved

Functional

The complaint status should change to ‘resolved’ when the user clicks on resolve complaint and the complaint should be resolved

PASS

HLM/1736/29

Complaint Actions

Check whether clicking on the Reject complaint button the reject complaint screen appears, that includes the following fields 1. Reason for Rejection 2. Additional comments

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on Reject complaint button

By clicking on the Reject complaint button the reject complaint screen should appear, that should include the following fields 1. Reason for Rejection 2. Additional comments

PASS

HLM/1736/30

Complaint Actions

Check if Reason for Rejection is a drop down field that shows the reasons list

The Reason for Rejection should be a drop down field and should shows the reasons list for rejection

PASS

HLM/1736/31

Complaint Actions

Check if Reject button is visible and clickable on Reject complaint screen

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on Reject complaint button 8. Click on Reason for rejection dropdown and select a reason 9. Click on Reject button

The Reject button should be visible and clickable on Reject complaint screen

PASS

HLM/1736/32

Complaint Actions

Check whether a toaster message appears with the text " Complaint Rejected successfully" when clicking on the Reject button

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on Reject complaint button 8. Click on Reason for rejection dropdown and select a reason 9. Click on Reject button

A toaster message with the text " Complaint Rejected successfully" should appear when clicking on the Reject button

PASS

HLM/1736/33

Complaint Actions

Check if the complaint status changes to ‘rejected’ when the user clicks on reject button and the complaint is rejected

Functional

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on Reject complaint button 8. Click on Reason for rejection dropdown and select a reason 9. Click on Reject button 10. Check the complaint status

The complaint status should change to ‘rejected’ when the user clicks on reject button and the complaint should be rejected

PASS

HLM/1736/34

Complaint Actions

Check whether an error message with a reminder is generated for mandatory fields

1.Navigate to the application URL 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button 6. Click on Take action button 7. Click on assigne/reject complaint button 8. Check the mandatory fields

An error message with a reminder should be generated for mandatory fields

PASS

HLM/1736/35

Complaint Actions

Check whether all the mandatory fields are having "*" symbol on the text fields or text areas

All the mandatory fields should have "*" symbol on the text fields or text areas

PASS

Creating User

Test Id

Sub Feature/ Use Case

Test Ideas

Test Type

Test Data

Steps to be executed

Expected Result

QA Review

Dev Review

PM Review

Actual result

Dev Status

QA Status

HLM/1756/01

Creating user

Check if System admin, national/provincial/district supervisor, helpdesk users are able to create new users

Functional

System admin, national/provincial/district supervisor, helpdesk users should be able to create new users

PASS

HLM/1756/02

Creating user

Check if Create user option is available and is clickable on user Management card

Functional

Create user option should be available and should be clickable on user Management card

PASS

HLM/1756/03

Creating user

Check if Create user option is available on Search employee screen as well and is clickable

Functional

Create user option should be available on search user screen and should be clickable

PASS

HLM/1756/04

Creating user

Check if the page navigates to New Employee screen when clicked on Create user link

Functional

The page should navigates to New Employee screen when clicked on Create user link

PASS

HLM/1756/05

Creating user

Check whether the following sections are available on the New Employee screen 1. Login Details 2. Personal details 3. Employee Details 4. Jurisdiction Details

The following sections should be available on the New Employee screen 1. Login Details 2. Personal details 3. Employee Details 4. Jurisdiction Details

PASS

HLM/1756/06

Creating user

Check whether the following fields are available in Login Details section and all the fields are mandatory 1. Username 2. Password 3. Confirm password

The following fields should be available in Login Details section and should be mandatory 1. Username 2. Password 3. Confirm password

PASS

HLM/1756/07

Creating user

Check whether the following fields are available in Personal Details section 1. Employee name 2. mobile number 3. Gender ( radio buttons) 4. Date of Birth ( Date picker) 5. email ID ( mandatory field) 6. Correspondence Address

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Check for all the validations for Employee name, mobile number, Gender, Date of Birth, email ID, Correspondence Address fields

The following fields should be available in Personal Details section 1. Employee name 2. mobile number 3. Gender ( radio buttons) 4. Date ( Date picker) 5. email ID ( mandatory field) 6. Correspondence Address

PASS

HLM/1756/08

Creating user

Check whether the following fields are available in Employee Details section 1. Employment Type ( Mandatory dropdown field) 2. Department ( Mandatory dropdown field) 3. Date of employment(Date picker)

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Check for all the validations for Employment Type, Department, Date of employment fields

The following fields should be available in Employee Details section 1. Employment Type ( Mandatory dropdown field) 2. Department (Mandatory) 3. Date of employment(Date picker)

PASS

HLM/1756/09

Creating user

Check whether the following fields are available in Jurisdiction Details section and all the fields are mandatory 1. Boundary Type (dropdown field) 2. Boundary (dropdown field) 3. Role (dropdown field)

The following fields should be available in Jurisdiction Details section and all the fields should be mandatory 1. Boundary Type (dropdown field) 2. Boundary (dropdown field) 3. Role (dropdown field)

PASS

HLM/1756/10

Creating user

Check if the "Add another Jurisdiction" link is available by clicking on which another Jurisdiction section should be added

Functional

The "Add another Jurisdiction" link should be available by clicking on which another Jurisdiction section should be added. User should be able to add more than one Jurisdiction

HLM/1756/11

Creating user

Check if a confirmation popup appears on New Employee screen when clicked on submit button and if it has "Cancel" and "submit" button

Functional

A confirmation popup should appear when clicked on submit button and it should have "Cancel" and "submit" button

HLM/1756/12

Creating user

Check if the page renavigates to New Employe screen and the data is retained when clicked on cancel button

Functional

The page should renavigates to New Employe screen and the data entered earlier should be retained when clicked on cancel button

HLM/1756/13

Creating user

Check if a response screen with the text "Employee created successfully " and Employe ID is displayed by clicking on Submit Button and a New employee is created

Functional

A response screen with the text "Employee created successfully " and Employe ID should be displayed by clicking on Submit Button and a New employee should be created

HLM/1756/14

Creating user

Check if the response screen has the following options and are clickable 1. Go Back To Home link 2. Proceed for campaign assignment

Functional

The response screen should have the following options and should be clickable 1. Go Back To Home link 2. Proceed for campaign assignment

PASS

HLM/1756/15

Creating user

Check if the status of the newly created user is "Active"

Functional

The status of the newly created user should be "Active"

PASS

HLM/1756/16

Creating user

Check if Assign Campaign screen with following fields is displayed when clicked on "Proceed for campaign assignment" button and are mandatory fields 1. Campaign Name (dropdown field) 2. Administrative Area (dropdown field) 3. Assigned from Date (date picker) 4. Assigned till Date (date picker)

The Assign Campaign screen with following fields should be displayed when clicked on "Proceed for campaign assignment" button and all fields should be mandatory 1. Campaign Name (dropdown field) 2. Administrative Area (dropdown field) 3. Assigned from Date (date picker) 4. Assigned till Date (date picker)

PASS

HLM/1756/17

Creating user

Check if the "Add another assignment" link is available by clicking on which another campaign section should be added

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) Click on Proceed for campaign assignment button 7) Click on Add another Assignment link

The "Add another assignment" link should be available and by clicking on that another campaign section should be added

PASS

HLM/1756/18

Creating user

Check if a response screen with the text "Campaign Assigned successfully " and Employe ID is displayed by clicking on Submit Button and the campaigns are assigned

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) Click on Proceed for campaign assignment button 7) Add the required campain details 8) Click on Submit

A response screen with the text "Campaign Assigned successfully " and Employe ID should be displayed by clicking on Submit Button and the campaigns should be assigned

PASS

HLM/1756/19

Creating user

Check if "Go Back To Home" Button is avilable on response screen clicking on which page navigates to Details screen

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) Click on Proceed for campaign assignment button 7) Add the required campain details 8) Click on Submit 9) Click on "Go Back To Home" Button

"Go Back To Home" Button should be avilable on response screen clicking on which the page should navigate to Details screen

PASS

HLM/1756/20

Creating user

Check if the Details screen has all the Details enterd while creating the user

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) Click on Proceed for campaign assignment button 7) Add the required campain details 8) Click on Submit 9) Click on "Go Back To Home" Button

The Details screen should have all the details entered while creating the user including Campaigns assigned under the following sections: 1. Login Details 2. Personal details 3. Employee Details 4. Jurisdiction Details 5. Assignment details

PASS

HLM/1756/21

Creating user

Check if the user can log in to the new account created by entering the credentials given while creating the user on both app and web

Functional

1) Launch the application / navigate to the application URL 2) Login to the application

The user should be able to log in to the new account created by entering the credentials given while creating the user on both app and web

PASS

HLM/1756/22

Creating user

Check if the password is masked on Details screen

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) Click on Proceed for campaign assignment button 7) Add the required campain details 8) Click on Submit 9) Click on "Go Back To Home" Button

The password should be masked on Details screen

PASS

HLM/1756/23

Creating user

Check if Reset Password link is available on details screen by clicking on which OTP verification popup should appear

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) Click on Proceed for campaign assignment button 7) Add the required campain details 8) Click on Submit 9) Click on "Go Back To Home" Button 10) Click on Reset password link

Reset Password link should be available on details screen by clicking on which OTP verification popup should appear

PASS

HLM/1756/24

Creating user

Check if OTP verification popup has the following fields 1. OTP field 2. New password 3. Confirm password

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) Click on Proceed for campaign assignment button 7) Add the required campain details 8) Click on Submit 9) Click on "Go Back To Home" Button 10) Click on Reset password link

The OTP verification popup should have the following fields 1. OTP field 2. New password 3. Confirm password

PASS

HLM/1756/25

Creating user

Check to see if the user receives the OTP to the email address they specified when creating the user for password reset.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) Click on Proceed for campaign assignment button 7) Add the required campain details 8) Click on Submit 9) Click on "Go Back To Home" Button 10) Click on Reset password link

The user should receive the OTP to the email address they specified when creating the user for password reset.

PASS

HLM/1756/26

Creating user

Check to see if a resend OTP link is accessible on the OTP verification popup, after which the user should receive OTP to their email once more.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) Click on Proceed for campaign assignment button 7) Add the required campain details 8) Click on Submit 9) Click on "Go Back To Home" Button 10) Click on Reset password link 11) Click on Resend OTP

A resend OTP link should be accessible on the OTP verification popup, after which the user should receive OTP to their email once more.

PASS

HLM/1756/27

Creating user

Check to see if the password is reset after providing all of the information and clicking on the Reset password button on the OTP verification popup.

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) Click on Proceed for campaign assignment button 7) Add the required campain details 8) Click on Submit 9) Click on "Go Back To Home" Button 10) Click on Reset password link 11) Enter all the required details and click on Reset Password button

The password should be reset after providing all of the information and clicking on the Reset password button on the OTP verification popup.

PASS

HLM/1756/28

Creating user

Check if a common recovery email is linked to each account which will be used for password recovery if the users do no have email IDs linked to their accounts

Functional

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) Click on Proceed for campaign assignment button 7) Add the required campain details 8) Click on Submit 9) Click on "Go Back To Home" Button 10) Click on Reset password link 11) Enter all the required details and click on Reset Password button

A common recovery email should be linked to each account which will be used for password recovery if the users do no have email IDs linked to their accounts

HLM/1756/29

Creating user

Check if username is able to change once created during user creation

1) Navigate to the application URL. 2) Login to the application with the valid credential of system admin, national/provincial/district supervisor, helpdesk user roles. 3) Click on the "Create user" link on user management card 4) Enter the required details and click on submit 5) Click on Submit button on the confirmation popup 6) go to search user and click on a created user link 7) Click on Take action button on details screen 8) Click on "Edit employee details"

Once created during user creation, the username must not be able to change

PASS

HLM/1756/30

Creating user

Check whether an error message with a reminder is generated for mandatory fields

Error message with a reminder should be generated for mandatory fields

PASS

HLM/1756/31

Creating user

Check whether all the mandatory fields are having "*" symbol on the text fields or text areas

All the mandatory fields should have "*" symbol on the text fields or text areas

PASS

Inbox

Test Id

Sub Feature/ Use Case

Test Ideas

Test Type

Test Data

Steps to be executed

Expected Result

QA Review

Dev Review

PM Review

Actual result

Dev Status

QA Status

HLM/1735/01

Inbox

Check if Complainants and helpdesk users are able to navigate to compaint inbox when clicked on complaint button on Home page

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button

Complainants and helpdesk users should be able to navigate to compaint inbox when clicked on complaint button

PASS

HLM/1735/02

Inbox

Check whether the complainant and helpdesk user can view the Complaint inbox

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. View the inbox

The complainant and helpdesk users should be able to view the Complaint inbox

PASS

HLM/1735/03

Inbox

Check if complaint inbox screen has the following components 1. Search 2. Filter 3. Sort

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button and click on search, filter, sort buttons

Complaint inbox screen should have the following components 1. Search 2. Filter 3. sort

PASS

HLM/1735/04

Inbox

Check if File complaint button is visible and clickable on My complaint screen

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on File complaint button

File complaint button should be visible and clickable on My complaint screen

PASS

HLM/1735/05

Inbox

Check whether clicking on File complaint it navigates to complaint type screen

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on File complaint button

Clicking on File complaint it should navigate to complaint type screen

PASS

HLM/1735/06

Inbox

Check if a Search By popup opens when clicked on Search

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on search and check the popup

Search By popup should open when clicked on Search

PASS

HLM/1735/07

Inbox

Check if the search popup have 1. Search parameters( configurable) 2. Search button

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on search and check the popup

Search By popup should have 1. Search parameters( configurable) 2. Search button

PASS

HLM/1735/08

Inbox

Check if user is able to enter data in the search parameters

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. click on search 6. Enter the data to be searched in search parameters

User should be is able to enter data in the search parameters

PASS

HLM/1735/09

Inbox

Check if no results found message/screen is displayed if the search results are not found

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on search 6. Enter the data to be searched in search parameters 7. Click on search

No results found message/screen should be displayed if the search results are not found

PASS

HLM/1735/10

Inbox

Check that the search button is only activated when the user enters data in the search parameters.

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on search 6. Check search button without entering the data to be searched in search parameters

The search button Should only be activated when the user enters data in the search parameters.

PASS

HLM/1735/11

Inbox

Check to see if the search results are displayed after clicking the search button.

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. click on search 6. Enter the data to be searched in search parameters 7.Click on search button

The search results should be displayed after clicking the search button.

PASS

HLM/1735/12

Inbox

Check if a Filters popup opens when clicked on Filters button on inbox

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on Filter button

Filters popup should be open when clicked on Filters button on inbox

PASS

HLM/1735/13

Inbox

Check if the filter popup have 1. Filters for different fields(configurable) 2. Apply button 3. Clear All Button

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on Filter button

Filter popup should have 1. Filters for different fields(configurable) 2. Apply button 3. Clear All Button

PASS

HLM/1735/14

Inbox

Check wheather the popup disappears when clicked on cancel (X)

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on Filter/Search button 6. Click on cancel (X)

The popup should disappears when clicked on cancel (X)

PASS

HLM/1735/15

Inbox

Check that the apply button is only activated when the user adds filters.

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5.Click on Filter button 6.Check apply button without adding any filters

The apply button should be only activated when the user adds filters.

PASS

HLM/1735/16

Inbox

Check if user is able to select the required filters

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on Filter button 6. Select the filters

User should be able to select the required filters

PASS

HLM/1735/17

Inbox

Check to see if the filtered results are displayed after clicking the apply button.

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on Filter button 6. Select the filters 7. Click on Apply button

Filtered results should be displayed after clicking the apply button.

PASS

HLM/1735/18

Inbox

Check if the user is able to clear all filters applied by clicking on clear all button

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. click on Filter button 6. Click on Clear All button

By clicking on "clear all" button User should be able to clear all filters applied

PASS

HLM/1735/19

Inbox

Check if a Sort By popup opens when clicking on the sort button on the inbox

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on sort button

Sort By popup should open when clicked on the sort button on the inbox

PASS

HLM/1735/20

Inbox

Check if the Sort By popup has following options and is clickable 1. Complaint Date (Latest first) 2. Complaint Date (Latest last)

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5.Click on Sort button 6. Check the options

The Sort By popup should have the following options and should be clickable 1. Complaint Date (Latest first) 2. Complaint Date (Latest last)

PASS

HLM/1735/21

Inbox

Check if the Sort By popup has sort button and is functional

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on sort button 6. Click on sort button on Sort By popup

The Sort By popup should have sort button and should be functional

PASS

HLM/1735/22

Inbox

Check if the complains are sorted according to the sort options selected

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on sort button 6. Click on sort button on Sort By popup 7. Check for the sorted complains on inbox

The complains should be sorted according to the sort options selected

PASS

HLM/1735/23

Inbox

Check if complaint inbox screen have the previously logged complaints in the cards format

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button and check for previously logged complaints

Complaint inbox screen should have the previously logged complaints in the cards format

PASS

HLM/1735/24

Inbox

Check for a complainant, the complaints list must consist of only those complaints logged by a particular user’s account.

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button and check for previously logged complaints

For Complainant, the complaints list must consist of only those complaints logged by a particular user’s account.

PASS

HLM/1735/25

Inbox

Check for helpdesk users, the complaints list must consist of the complaints filed by helpdesk users, as well as complaints filed by mobile app users

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button and check for previously logged complaints

For helpdesk users, the complaints list must consist of the complaints filed by helpdesk users, as well as complaints filed by mobile app users

PASS

HLM/1735/26

Inbox

Check if the inbox for all the helpdesk users are common

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button and check the complaints logged

The inbox for all the helpdesk users should be common

PASS

HLM/1735/27

Inbox

Check if Open button is present on every complaint card and is functional

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button from any on the complaint

Open button should be present on every complaint card and should be functional

PASS

HLM/1735/28

Inbox

Check whether clicking on open button it navigates to Complaint details screen

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on open button and check the navigation to complaint details screen

Clicking on open button page should navigate to Complaint details screen

PASS

HLM/1735/29

Inbox

Check whether the back button component is present on the inbox screens of the mobile application, and it should be clickable

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Check for back button on the top left of the screen

The back button should be present on the inbox screens of the mobile application, and it should be clickable

PASS

HLM/1735/30

Inbox

Check if the page redirectes to home page when clicked on back button

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Check for back button on the top left of the screen 6. Click on back button

The page should redirect to home page when clicked on back button

PASS

HLM/1735/31

Inbox

Check whether application works as per requirement when it is in offline mode

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button

Application should work as per requirement when it is in offline mode

PASS

HLM/1735/32

Inbox

Check for the complaint number on the inbox that should be mentioned as "Not generated(Sync required)" when the data is not synced , after syncing the complaint number should be generated

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Create a complaint 5. Check the complaint no on inbox 6. Up Sync data 7. Down sync the data and check the complaint number on inbox

When the data is not synced, the complaint number in the inbox, should say "Not generated(Sync required)"; after syncing, the complaint number should be generated and the number should be shown on inbox

PASS

Logging Complaint

Test Id

Sub Feature/ Use Case

Test Ideas

Test Type

Test Data

Steps to be executed

Expected Result

QA Review

Dev Review

PM Review

Actual result

Dev Status

QA Status

HLM/1726/01

Logging Complaint

Check whether the frontline workers have a complaint button on the Home screen

1.Launch the application 2.Enter credentials 3.Click on Login

The frontline workers should have a complaint button on the Home screen

PASS

HLM/1726/02

Logging Complaint

Check if FLW can navigate to the complaint inbox when clicking on complaint button

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button

FLW should be able to navigate to the complaint inbox when clicking on the complaint button

PASS

HLM/1726/03

Logging Complaint

Check if the complaint screen(inbox) has the following components and is clickable 1. Search 2. Filter 3. Sort 4. File complaint button

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button

The complaint screen should have the following components and should be clickable 1. Search 2. Filter 3. sort 4. File complaint button

PASS

HLM/1726/04

Logging Complaint

Check if the complaint screen has the previously logged complaints with complaint details

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button

The complaint screen should have the previously logged complaints with complaint details

PASS

HLM/1726/05

Logging Complaint

Check to see if the complaint card contains the following information. 1. Complaint Number 2. Complaint Type 3. Complaint Date 4. Area 5. Status

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button and verify the details on the complaint card

The complaint card should contain the following information. 1. Complaint Number 2. Complaint Type 3. Complaint Date 4. Area 5. Status

PASS

HLM/1726/06

Logging Complaint

Check if the Open button is present on every complaint card

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button

The open button should be present on every complaint card

PASS

HLM/1726/07

Logging Complaint

Check whether the complaint Details(summary) page opens when clicking on Open button

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5.Click on open button from any on the complaint

The complaint card should open when clicked on the Open button

PASS

HLM/1726/08

Logging Complaint

Check whether clicking on the File complaint Button, the page navigates to the type of complaint screen

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on File complaint Button and check if it navigates to type of complaint screen

Clicking on the File complaint Button page should navigate to the type of complaint screen

PASS

HLM/1726/09

Logging Complaint

Check to see if the complaint type options are visible and if the radio buttons are clickable on the type of complaint screen.

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on File complaint Button

The complaint type options should be visible and the radio buttons should be clickable on the type of complaint screen

PASS

HLM/1726/10

Logging Complaint

Check if others option is visible and on selecting it a text field should appear below the options

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on File complaint Button 6. Select other option from the type of complaint screen

Others option must be visible and on selecting it a text field should appear below the options

PASS

HLM/1726/11

Logging Complaint

Check if the next button on the Type of complaint screen is functional

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5.Click on File complaint Button 6.Click on next

The next button on the "Type of complaint" screen should be functional

PASS

HLM/1726/12

Logging Complaint

Check whether the complaint detail screen appears by clicking on the next button

Functional

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5.Click on File complaint Button 6.Click on next

The complaint detail screen should appear when clicking on the next button

PASS

HLM/1726/13

Logging Complaint

Check if the Date and Administrative Area fields are visible and auto-captured by the system

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5. Click on File complaint Button 6.Click on next 7.Check the Date and Administrative area details

Date and Administrative Area fields should be auto-captured by the system

PASS

HLM/1726/14

Logging Complaint

Verify that the date field is non-editable.

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5.Click on File complaint Button 6.Click on next 7.Check the Date field

The date field should be non-editable.

PASS

HLM/1726/15

Logging Complaint

Check if the Administrative Area field is editable if other user option is selected and the other user is either at the same boundary or at a child level to the current user's boundary.

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5.Click on File complaint Button 6.Click on next 7.Check area details

Administrative Area field should be editable if other user option is selected and the other user on behalf of whom the complaint is being raised is either in the same boundary or belongs to a child level to the current user's boundary.

PASS

HLM/1726/16

Logging Complaint

Check whether the following options(radio buttons) are available: 1. Myself 2. Other user

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5.Click on File complaint Button 6.Click on next 7.Verify the options

The following options(radio buttons) should be available: 1. Myself 2. Other user

PASS

HLM/1726/17

Logging Complaint

When the user selects the Myself option, check if the user details are auto-populated.

1.Launch the application 2.Enter credentials 3.Click on Login 4.Click on Complaint button 5.Click on File complaint Button 6.Click on next 7.Verify user details

When the user selects the Myself option, the user details should be auto-populated.