Kshreyas/TA_RTM
07
1requirement_desc,test_cases2" There is a login page that would allow the users to log in to the application. Below three users can log in to the PMS application and will see their respective home screens: -Admin,Super Admin,User.",1. Enter valid Username and Password into their respective boxes then click on Log in button and check for log in. 2. Ensure that user is not logged in PMS application after entering invalid Username and Password 3. Ensure that user is not get logged in PMS application after entering valid Username and invalid Password 4. Ensure that user is not get logged in PMS application after entering invalid Username and valid Password 5. Ensure that If user enters incorrect data in any one of the field and click on login then validation message will appear as Invalid username or password. 6. Examine that null field will not be accepted as both the fields are mandatory and user will be notify regarding empty field by showing validation message. 7. Determine that all the entered data will be cleared on hitting reset button. 8. Ensure that all the text on buttons and fields is correct and clearly visible 3"After successful login, PMS dashboard will be displayed to the specific user depending on their roles.","1. To check that user's dashboard all tabs which present on home page are proper aligned . 2. Ensure that user can apply for admin generated policies by click on 'Apply' button. 3. Ensure that user can logout successfully from the application using Logout option which will be displayed after clicking on the user profile. 4. To ensure that all tabs that appear on the Super Admin and Adminuser's home page are properly aligned. 5. On the main screen of the dashboard, check to the previous and next navigation arrows functionality. 6. Make sure that the Super Admin and Admin user can successfully logout of the application using the Logout option, which will be available after clicking on the user profile. 7. Check that Admin or Super admin can see count of total numbers of policies, published policies and under reviewed policies on dashboard. 8. Ensure that Admin and Super admin can see all created policies on dashboard with their details in tabular form. 9. Check that particular entries has displayed after selecting number from dropdown. "4" This section includes a button to create the policy form. On clicking, the Create policy button, the screen moves to the Policy Details section.",1. Make sure that when Admin or Super Admin clicks on 'Create Policy' button they should be able to see policy form. 2. Check that a Admin can be created policy successfully with all required information. 3. Make sure that a Super Admin can be created policy successfully with all required information. 5"View History will allow the Super Admin/Admin to view the actions of the Users. If the user accepts any policy, the Super Admin/Admin will be able to view the same in the View History button.","1. Ensure that alignment of view history button, texts and font which are present on homepage are proper. 2. Ensure that the admin or super admin can effectively view the history of a policy. 3. Check the search functionality, super admin or admin is able to search entered result to the view history. "6The Super Admin / Admin will be able to pose restrictions on the type of passwords the users can use to access the PMS application.,1. Make sure that password policy is updating when Super Admin click on 'Update' button and Password policy updated successfully pop up message displaying. 2. Confirm that all dropdown values are blanked out after Super Admin clicking on the Reset button. 3. Ensure that password policy is updating when Admin click on 'Update' button and Password policy updated successfully pop up message displaying. 4. Observe that all dropdown values are blanked out after Admin clicking on the Reset button. 7The Notification bell icon would display the information based on any updates performed by the Admin/Super Admin. The Super Admin will get notifications when: • The admin has sent a policy for review. • If the Admin published a policy. The admin w...,1. See that Super Admin can view notification when admin sending the policy for review and when admin publishing the new policy after clicking on bell icon. 2. Ensure that Admin can view notification when Super admin rejecting the policy and when super admin publishing the policy after clicking on bell icon. 8" The Super Admin, Admin and User can search policies to view the specific policy.","1. Check to see if the Super Admin can search for policies; if not, look for the message No matching records found. 2. Ensure that user can search for policies; if not, look for the message No matching records found. 3. Ensure that user can search for policies; if not, look for the message No matching records found. "9Accept button will allow the user to accept an individual policy.,1. Ensure that the user is able to select 'Terms and Conditions' checkbox then clicking on 'Submit' button. 10"Authorized user log's into the system using valid ID and password. The login process must validate that, the provided credentials grants access to authorized users only.","1. Verify that the user can access the appropriate dashboard by providing accurate credentials and clicking the login button. 2. Ensure that the user is unable to login, on providing incorrect data in any one of the fields. 3. Examine how the login button works when a valid username and an invalid password are entered. 4. Make sure that user will not be able to login by providing invalid data in both the fields 5. Ensure that if user enters incorrect data in any one of the field and click on login button then, validation message will appear as Invalid username or password 6. Check that user must be able to see an alert message if user miss to enter data in username field. 7. Examine that the null field will not be accepted as both fields are mandatory, and the user will be notified regarding the empty field by showing a validation message. 8. Determine that all the entered data will be cleared on hitting reset button. 9. Ensure that all the text on buttons and fields is correct and visible. 10. Determine the functionality of Password Visibility icon when user clicks on it. "11"Admin Dashboard provides an overview of existing batches which are categorized based on the status, list of trainings which are created for the users, list of draft batches- which are yet to be published, and list of trainers, defining their expertise a...","1. Ensure that the batches count appear on overview card is same as batches appear on that particular tab/card. 2. To edit batch or remove any batch, ensure that kebab icon on draft batches card shows the options on mouse hover on it. 3. For doing changes in details of draft batches we have to check that edit option is working properly or not? 4. Check if user want to delete batch then user is able to do it by using remove option appear after mouse hover on kebab icon 5. Examine that in order to see all the batches available in draft batches card, see all option is enable. 6. If user wants to see all the details of draft batches then by using view more option user is able to see the details. 7. Cross icon work like a remove option on draft batch card so to delete any batch cross icon must be working. 8. See all button should be enable to see all the available trainings on trainings card. 9. On each training card there is a edit button to edit the details of that particular training. 10. Ensure that on clicking view more option user is able to see all the details of that training. 11. Check the functionality of cross icon used to delete the training by clicking on it. 12. Examine the working of cross icon If user want to delete the training which is in use. 13. Test that on clicking See all button list of all the trainer is appear. 14. Examine the functionality of view button to see the details of individual trainer. 15. Check the functioning of notification bell if there are no notifications. 16. Analyze the functionality of notification bell if there are multiple notifications 17. Check the functionality of What's New feature to see whether it is taking tour as per newly implemented functionalities flow. "12"This module is develop for admin to add syllabus for particular training, create new trainings for employees for various delivery modes such as online , offline, workshop, on- job. Admin can also create trainings for different training types such as sof...","1. Check the functionality of add syllabus button used to create syllabus for training. 2. To make changes in details of syllabus like to add topic or to change duration of any topic, admin must be able to do it by using edit icon available in action column of syllabus data table. 3. If user want to cross check the added details or to view the syllabus details check that user can be do it by using view icon. 4. Ensure that as we are providing options to add , edit and view syllabus then there must be option available to delete any unwanted syllabus 5. Examine how the delete icon works ,If user want to delete the syllabus which is already used for any training. 6. Analyze the functionality of cross(X) icon and cancel button, if user filled data in all the fields and clicked on cancel button or closed the window. 7. Check if user entered any valid data in search field to search then data related to that searched data is appear. 8. Examine the functionality of search field if user entered invalid data in search field to search 9. Demonstrate that the next (>>) indicator is active in order to move to the next page and if current page is last page then next indicator is disable. 10. If the user wants to go back to the previous page, make sure the previous indicator (<<) is active and if the user is on the first page, make sure it is disabled. 11. Check that the current page number is highlighted. 12. Ensure the size of numbers, font , color is as per specification. 13. Test the functionality of show entries dropdown whether it is showing selected number of entries. 14. To navigate from one page to another, make sure that the breadcrumb is working properly. 15. Check the functionality of add button available on training module used to create new training. 16. Examine the functioning of add training button if user keep one of the field unselected or null. 17. If user added invalid data in any field while creating training then analyze the working of add button. 18. Ensure the functionality of add button, if user added invalid data in acronym field. 19. If user exceeds the limit of text field then ensure that user must be informed by showing validation message below respective text field. 20. If user not entered acronym in proper format then it must be informed by showing validation message below the acronym field. 21. Demonstrate the functionality of cross icon and cancel button. 22. To ensure the functionality of edit icon, change any details from edit training window and click on update. 23. Check the functioning of edit icon if user keep one of the field blank 24. Examine that how edit icon works if user entered invalid data in any field of edit training window 25. Verify that on exceeding text limit of any field, user must be informed by showing validation message. 26. Ensure that view icon is functional and check that all the training details are as per user entered 27. Check the functionality of link added to view syllabus details 28. Determine the functionality of delete icon if user click on delete icon to delete the unwanted trainings. 29. Examine the delete functionality if user want to delete the training which is already in use. 30. Check if user entered any valid data in search field to search then data related to that searched data is appear. 31. Examine the functionality of search field if user entered invalid data in search field to search 32. Demonstrate that the next (>>) indicator is active in order to move to the next page and if current page is last page then next indicator is disable. 33. If the user wants to go back to the previous page, make sure the previous indicator (<<) is active and if the user is on the first page, make sure it is disabled. 34. Check that the current page number is highlighted. 35. Ensure that the size of numbers, font and color is as per specification. 36. Test the functionality of show entries dropdown whether it is showing selected number of entries. 37. To navigate from one page to another, make sure that the breadcrumb is working properly. 38. Check the functionality of add button used to add questions for different training topic. 39. Analyze the functionality of edit icon, used to edit added questions for specific training topic. 40. Make sure that in edit window, training topic is read only, user must be unable to access it or change it. 41. Check the functionality , if user entered questions for a specific training topic and closed the window or clicked on the cancel button then data must be refreshed. 42. Analyze the functionality of view icon, on clicking it user must be able to see the added questions for training topic. 43. Make sure that on clicking delete icon user must be able to delete the questions for that particular training topic. 44. Check if user keep one of the question text field blank or null and clicked on add button. 45. Analyze the functionality if user try to add feedback questions for previously same training topic. 46. Make sure that uploading excel functionality is working properly. 47. Check the functionality of cancel button if user uploaded excel file and then clicked on cancel button. 48. Ensure that on clicking Download sample excel button , user is able to download sample excel for syllabus. 49. Verify that on clicking delete icon user must be able to delete that particular topic/subtopic. 50. Check that delete icon is on proper place 51. Check the edit icon functionality, on clicking it whether user is able to make changes in already added syllabus. 52. Check the functionality of view icon, whether it is showing accurate data in proper field or not. 53. Check that after adding syllabus how that added syllabus appear in data table. "13" Admin shall have access to create and modify, cancel or delete the existing batches if required. Differentiating the batches as per their respective status shall be mentioned in the individual tabs.","1. Examine the functioning of Add New Batch button if user has not added training and directly adding the batch. 2. Determine the functionality of Add New Batch button if user has not added trainer and directly adding batch except for online delivery mode. 3. Ensure that validation message must be raised if user keep one of the field blank or unselected 4. Check the functionality of validation message if user entered end date less than start date 5. Make sure that if user entered end time less than start time then validation message must be raised. 6. Check the functionality of Add button by filling all the details in add new batch window. 7. Analyze the functionality if user filled all the details and clicked on save draft button. 8. Check the functionality of back button if user filled all the details and click on back button 9. Check the functionality of (X) cross icon used to close the window. 10. Make sure that for editing batch details , edit option is working properly 11. Determine the functionality of Update button if user keep one of the field blank in edit batch window. 12. Analyze the functionality of validation message if user entered end date less than the start date. 13. Check the functionality if user entered End time less than the start time 14. Check the functionality if user make some changes in details and clicked on update button. 15. Examine the functionality of save draft button if user done changes in batch details and clicked on it. 16. Check whether the changes are updated by making some changes in batch details and clicking on back button or closed the window. 17. Make sure that view more option is clearly visible on mouse hover on batch card 18. Ensure that the view more option is functional. 19. Examine the working of nominees option visible on mouse hover on batch card. 20. Check the functionality of (X) cross icon or close button used to close the window. 21. Determine the functionality of (X) icon available on batch card used to cancel the batch. 22. Check the functionality of draft batches tab. 23. To update batch make sure that edit option is working properly. 24. Check the functionality if user modify some details of batch and click on update button 25. Ensure that on editing details if user click on save draft button then that batch appear in draft batches itself with updated changes. 26. Make sure that if user changes batch details and clicked on back button or close the window then changes will not update. 27. Examine the functionality of view more option whether it is showing proper details associated with that particular field. 28. Check in view batch details window, syllabus link is functional or not? 29. Analyze the functionality of cross(X) icon, whether on clicking it user is able to delete that particular batch permanantly? 30. Check the functionality of completed batches tab, is it showing only the batches whose duration is completed? 31. Test the functionality of view more option whether it is showing accurate detail in front of specific field name. 32. Ensure that syllabus link is functional and on clicking it showing syllabus details. 33. To see the list of all employees those have attended the batch, make sure that participant button is working properly. 34. Examine the functionality of cancelled batches tab 35. Analyze the functionality of view more option by clicking on it 36. Test the working of cross(X) icon available on batch card used to delete the particular batch. 37. Check the functionality of batch calendar button in order to see all the scheduled batches of the month. 38. Examine the functionality of month and year dropdown available on batch calendar page 39. Analyze the working of search field 40. Check the functionality of download button available on batch calendar. 41. Demonstrate that the next (>>) indicator is active in order to move to the next page and if current page is last page then next indicator is disable. 42. If the user wants to go back to the previous page, make sure the previous indicator (<<) is active and if the user is on the first page, make sure it is disabled. 43. Check that the current page number is highlighted. 44. Ensure that the size of numbers, font and color is as per specification. 45. Test the functionality of show entries dropdown whether it is showing selected number of entries. 46. To navigate from one page to another, make sure that the breadcrumb is working properly. 47. Check the functionality of Final Report button, on clicking it user must be able to download final report of all completed batches. 48. Analyze that on downloading final report , it will show accurate data in proper format. 49. Check the font , font size and color of Final Report button. 50. Check the functionality of download button appear on clicking view more. "14"List of raised nomination by the employees for particular training batch shall be populated in the tabular format, admin shall be authorized to accept or reject such nominations, batch progress report of particular employee must be accessible for admin.","1. Ensure that admin is able to see all the details of the nomination by clicking on view icon. 2. Make sure that on clicking on accept icon , nomination must be accepted. 3. Check the working of reject icon from action column, whether nomination gets rejected by clicking on it. 4. Check if user entered any valid data in search field to search then data related to that searched data is appear. 5. Examine the functionality of search field if user entered invalid data in search field to search 6. Demonstrate that the next (>>) indicator is active in order to move to the next page and if current page is last page then next indicator is disable. 7. If the user wants to go back to the previous page, make sure the previous indicator (<<) is active and if the user is on the first page, make sure it is disabled. 8. Check that the current page number is highlighted. 9. Ensure that the size of numbers, font and color is as per specification. 10. Test the functionality of show entries dropdown whether it is showing selected number of entries. 11. To navigate from one page to another, make sure that the breadcrumb is working properly. 12. Check the functionality of filter applied for batch code, whether it is showing data of selected batch code only or not? 13. Make sure that on click event of progress report button , all the accepted nomination data is appear with completed training progress report in percentage. 14. Check the functionality of batch code filter , whether it is showing data for selected batch code only. 15. In order to save data in excel format , check that the download button is working properly and showing accurate data with respective field. 16. To see the rejected nominations data, ensure that the reject history button is working properly. 17. Make sure that data appear in reject history must be in proper font , size and alignment. "15" In this my calendar user can check the weekly work schedule. in this can be displayed the monthly calendar which has shows the holidays, appointments of that user as well as if the user is CO,HOD,FREELANCER, FDM then other employees schedule also check.","1. The user has access to the My Calendar, Block Appointment, and Appointments Summary in thecalendar and appointment modules. 2. Some modules, such as Package Builder, Set Policy, Set a Working Schedule, appointment ledgers, etc., are restricted to theuser. 3. Ensure that user has access to create and do modifications in particular operations of each and every module from the calendar and appointments. 4. Ensure that the user is able to see by default the name of the clinic and doctor if the user has not selected any option from the dropdown. 5. Examine the functionality that if user selected only clinic name then by default there own name is appear on the select physiotherapist dropdown. 6. The Clinic and Physiotherapist dropdown are displayed in the My Calendar module after clicking the View Working Schedule card. 7. By selecting a clinic from the list of clinic names under My Calendar, the employees' names from that clinic are added to the list of available physiotherapists. 8. The related physiotherapist schedule for that month can be displayed on the calendar with various colorsby selecting the physiotherapist selection from the My Calendar dropdown list. 9. Analyze the functionality that FDM is able to see the schedule of all the employees associated with that particular clinic. 10. Ensure that FDM is able to see their own schedule by default, if he/she not selected any options from any dropdown. 11. Examine the day on which the appointment was booked to see whether any other appointments have been completely booked 12. Look up the day of the selected date to see how many appointments are already scheduled or are available to be scheduled. 13. Check the Time and booked or empty slots for any selected date. 14. In order to see a different icon for each location ensure that the icon changes if the user set the schedule as a clinic or home or hybrid. 15. Check that if user opens the View Working Schedule then by default he/she is able to see the schedule for that current week. 16. To view the holiday as a different weekday is indicated by the lime green color and ensure that on that day no appointment is scheduled. 17. Take a look at that user is able to see available dates for booking appointments as indicated with the green color dot. 18. Make sure that the day on which the user has not set a work schedule and is unable to book the appointments is indicated by light grey color and no box around it. 19. On the monthly calendar, the particular date on which appointments are booked fast and in progress to book all the appointments that date is indicated by the orange color dot. 20. Make sure that the date for which status of a booking an appointment is almost full, that indicates with the red color dot. "16 Admin login The admin will enter the valid credentials and hit “Login” button. Admin will be able to reset the provided credentials.,1. Determine that user will be able to navigate to the respective dashboard by hitting login button by entering valid credentials. 2. Ensure that the functionality of the login button on entering a Invalid username and valid password. 3. Determine the functionality of the login button on entering a valid username and invalid password. 4. Make sure that user will not be able to log in by providing invalid data in both fields. 5. Examine without selecting the checkbox admin can get logged in with valid data. 6. Make sure that the Reset button resets the form or application to its default state when clicked. 7. Examine that clicking the Reset button on an empty form has no effect. 8. Ensure that if the user enters incorrect data in any one of the fields and click on login then the validation message will appear as Invalid username or password. 9. Check that user must be able to see the alert message if the user miss out to enter data in username field. 10. Examine that the null field will not be accepted as both fields are mandatory and the user will notify regarding the empty field by showing a validation message. 17Setup schedule for yourself and all employees in your clinic. Allow patients to book appointments based on your schedule.,"1. Users will not be able to view Set Working Schedule sub-module in the Calendar & Appointments module, since they do not have access to it. 2. Users will not be able to view Set Working Schedule sub-module 3. Users will be able to view Set Working Schedule page, since they possess access to it. 4. Users will not be able to view Set Working Schedule page 5. ADD FIRST CLINIC: User navigates to Clinic Schedule Setup without clicking on +ADD FIRST CLINIC , directly hits the NEXT button 6. User navigates to Clinic Schedule Setup clicks on +ADD FIRST CLINIC and fills the form to add a Clinic, and hit NEXT button 7. User navigates to Clinic Schedule Setup clicks on +ADD FIRST CLINIC and fills the form to add a Clinic. 8. User navigates to Clinic Schedule Setup clicks on +ADD FIRST CLINIC and fills the form to add a Clinic, Clinic is added, then user attempts to add another Clinic. 9. On clicking the Clinic module, Select Clinic Dropdown will be auto-selected, employees checkboxes will be checked and clicks on NEXT button. 10. On clicking the Clinic module,Select Clinic Dropdown will be selected, employees checkboxes will not be checked and clicks on NEXT button. 11. ADD AN EMPLOYEE: User clicks on Select Clinic dropdown, selects base, clicks on + Add an Employee button, landing on the Registration page for adding the role of the employee. 12. CLINIC APPOINTMENT DURATION: User will click on NEXT button without selecting any time slot. 13. User selects one time slot from the given slots and clicks on next button. 14. User attempts to select multiple time slots in a single try and clicks on NEXT button. 15. User selects a valid start time and a valid end time, and clicks on Finish button, in the Set Working Hours page. 16. User selects an invalid start time and an invalid end time, and clicks on Finish button, in the Set Working Hours page. 17. User selects an invalid end time first and a valid start time later, in the Set Working Hours page . 18. In Enable Working Days form, User selects all the day slots, and hits finish button. (Mon-Sun) 19. In Enable Working Days form, When none of the day slots are selected user hits finish button. 20. User selects a invalid end time first and a valid start time later, in the Set Working Hours page . 21. CLINIC SPECIFIC: Assuming a user has scheduled an enabled day slot in the set working hours, they can duplicate the same schedule to another enabled slot or multiple slots. 22. Assuming a user has scheduled an enabled day slot in the set working hours, they cannot duplicate the same schedule to another disabled slot or multiple slots. 23. User attempts to set a schedule on the disabled working day slots, in the set working hours page. 24. In the Edit Profile page, Assign clinic dropdown list, the user selects desired the clinic out of the number of clinics present. 25. In the Edit Profile page, Assign Clinic dropdown list, the user selects the clinic out of the number of clinics present. 26. In the Edit Profile page, Assign Clinic dropdown list, the user selects all the clinics out of the number of clinics present. 27. In the Edit Profile page, Assign Clinic dropdown list, the user selects none of the clinics out of the number of clinics present. 28. METHOD 1: In Manage Employees, user can add employees, user clicks the +, fills the details using Add an Employee Manually and manages to successfully add an employee and assign a clinic. 29. In Manage Employees, user can add employees, user clicks the +, fills the details using Add an Employee Manually and manages to successfully add an employee and assign a multiple clinics 30. In Manage Employees, if user wishes to discard a Clinic, the schedule of the clinic will be cancelled, and the clinic would no longer be associated with the employee. 31. The user does not select/add any Clinic so the flow would not move any further. 32. METHOD 2: In Clinic Schedule Setup, User auto selects the clinic, and the list of employees are displayed. And the selected employees are assigned to the -selected clinic 33. The user does not select any clinic so the flow would not move any further. 34. METHOD 3: In Clinic Schedule Setup, user clicks Set Working Schedule, user select a desired clinic from Select a Physio to view their schedule. 35. The user does not select any clinic so the flow would not move any further. 36. In Set Working Schedule, in the Select Employees page, user can select a desired employee, if he has work scheduled in another clinic, it will show schedule present. If the user selects employee whose schedule is already present, the employee's... 37. In Set Working Schedule, in the Select Employees page, user can select multiple employees, if employees' have work scheduled in different clinics, it will show schedule present. If the user selects multiple employees whose schedules are alrea... 38. In Set Working Schedule, in the Select Employees page, user can select multiple employees, if employees' have no work scheduled in different clinics olr Clinic, it will not show schedule present. If the user selects an employee the schedule w... 39. In Set Working Schedule, in the Select Employees page, user can select none of the employees, the flow would not move forward. 40. There will be a message on the screen that reads Schedule present if an employee's working day has already been scheduled and another business user wants to allocate that individual to their firm. The revised schedule will be applied to the emplo... 41. If multiple employees' working days are already scheduled and business user wants to assign those employees to their business, it will say Schedule present on the screen. If the user still choose those employees, the new schedule will take effec... 42. The new schedule will be the default for the selected employee if the working day of an employee is not scheduled and a different business wishes to allocate the employee to their business. In this case, it will not indicate Schedule present. 43. The user does not select any employee for their business so the flow would not move any further. 44. The user can view a summary of the schedule by selecting the Clinic and the employees after the schedule and click on BACK TO CALENDER AND APPOINTMENT MODULE 45. In addition to having proper user interface (UI), the user should be able to access the cart including the schedule policy and accessibility as well as its desired paragraph or text should be present without any spell mistake. "18"In this user can add themselves in the application and for that they required some information like the Name, address, e-mail id, phone number, Graduation information, Post-Graduation information, PAN number, GST Number, bank details like Account holder...","1. Roles that can register via Sign Up and approval will be needed from Pheal Web: Clinic Owner (Including Business) Practicing Physiotherapist 2. Roles that can be register from Manage Employee flow: Practicing Physiotherapist Internship/Observer ship Front Desk Manager 3. User clicks the Okay, Let's Begin button to move further to the registration 4. User skips the Okay, Let's Begin button, and page doesn't move further. 5. On clicking the Okay, Let's Begin button, the Where do you work page appears, user can chooses work from a private clinic, a hospital or Freelance. 6. User Clicks Clinic Owner, it lands to the What is your role page?, the basic information of a Practicing physiotherapist is displayed. Here, the user chooses to click the Select button, then further move on to registration. 7. User Clicks Clinic Owner, it lands to the What is your role? page, The user can also choose to click the arrow to the right, to view various roles and selects the I am a Practicing Physiotherapist role, the basic information of a Practicing physio... 8. User Clicks Clinic Owner,it lands to the What is your role? page, The user can also choose to click the arrow to the right, to view various roles and selects the I am a physiotherapy Intern role, the basic information of a physiotherapy Intern is... 9. User Clicks Clinic Owner,it lands to the What is your role? page, The user can also choose to click the arrow to the right, to view various roles and selects the I am a front desk manager role, the basic information of a front desk manager is disp... 10. User can click on + Add Photo, where the user would be able to upload their photo, it will redirect to your device from where the user uploads the photo in JPEG or PNG format. 11. User can click on + Add Photo, where the user would be able to upload their photo, it will redirect to your device from where the user uploads the photo that is not in JPEG or PNG format. 12. User can click on + Add Photo, where the user would be able to upload their photo, it will redirect to your device from where the user does not upload the photo at all. 13. The user clicks the change link, under Where do you work? Clinic, the page redirects to the Where do you work? page for the user's ease. 14. The user does not click, the change link, the user will not navigate any further remaining on the same page. 15. The user clicks the change link, under What is your role? Clinic Owner, the page redirects to the Let's get to know what your role is in the clinic page for the user's ease of navigation. 16. The user does not click, the change link, the user will not navigate any further remaining on the same page. 17. Mandatory field: User clicks on Full Name field, enters the Full Name , including only the characters. 18. User clicks on Full Name field, enters the Full Name , including alphanumeric characters. 19. User clicks on Full Name field and does not enter the Full Name, leaves the field blank. 20. Mandatory field: User clicks on Email Address field, enters a valid email id. 21. User clicks on Email Address field, does not enter a valid email id. 22. User clicks on Email Address field, does not enter any email id. 23. Mandatory field: For the Mobile Number field, while selecting the country code, a dropdown list is displayed with the different countries, country codes and their respective flags. User enters a valid mobile number by selecting a valid country code. 24. For the Mobile Number field, while selecting the country code, a dropdown list is displayed with the different countries, country codes and their respective flags. User enters an invalid mobile number by selecting a valid country code. 25. User does not enter any value in the Mobile Number field. 26. Mandatory field: By clicking on the checkbox for the notification updates or any promotional offers, the user receives offers on their WhatsApp application. 27. The user chooses not to select the checkbox for WhatsApp notifications 28. Mandatory field: For the Pin code field, user enters a valid six-digit pin code. 29. For the Pin code field, user enters an invalid six-digit pin code. 30. For the Pin code field, user does not enter any value in the field. 31. Mandatory field: When the user clicks on the Date of Birth field, a calendar would be displayed from where the user can make a valid selection. Where the minimum age criteria is greater than or equal to 21 years; The date of birth should be less than ... 32. When the user clicks on the Date of Birth field, a calendar would be displayed from where the user can make an invalid selection. 33. The user does not click on the Date of Birth field, and does select any date of birth. 34. Mandatory field: The user can click on the Gender dropdown, the user can make a valid selection. 35. The user does not click on the Gender dropdown and chooses not to make any selection. 36. Mandatory field: User clicks on Select Type of Cases You Treat dropdown, user chooses from a list of specializations by clicking on one or more checkboxes. 37. User clicks on Select Type of Cases You Treat dropdown, user chooses from a list of specializations by clicking on all the checkboxes or clicks Select all option from the list. 38. User does not select any specialization from the Select Type of Cases You Treat dropdown. 39. On clicking the Next Button, if any of the mandatory fields are invalid or skipped by the user, pop-ups will be displayed to fill the respective field. Only in case of valid scenarios the user would be able to navigate to the Next Page i.e. Education I... 40. As soon as the user moves from the Basic Information to the Education Information, the progress bar on the top of the page would be highlighted in green for the Basic Information page. 41. GRADUATION: Mandatory field: User clicks the University of Graduation field and enters the valid University. 42. User clicks the University of Graduation field and enters an invalid University. 43. User does not enter any value in the University of Graduation field. 44. Mandatory field: User chooses the valid course from the Course For Graduation drop down. The user must ideally select BPT Course. 45. User chooses the invalid course from the Course For Graduation drop down. 46. User does not select any course from the Course For Graduation drop down. 47. Mandatory field: User enters their valid year of graduation in the Year of Graduation field. 48. User enters an invalid year of graduation in the Year of Graduation field. 49. User does not enter any year of graduation in the Year of Graduation field. 50. Mandatory field: The user uploads a valid certificate of graduation in the Upload Certificate of Graduation in the acceptable JPEG,PNG or PDF formats. 51. The user uploads an invalid certificate of graduation in the Upload Certificate of Graduation in other unacceptable formats. 52. The user doesn't upload any file. 53. To add a Post Graduation, the user would click the + sign. User clicks the University of Post Graduation field and enters an valid University. 54. User clicks the University of Post Graduation field and enters an invalid University. 55. User does not enter any value in the University of Post Graduation field. 56. User chooses the valid course from the Course For Post Graduation drop down. The user must ideally select MPT Course. 57. User chooses the invalid course from the Course For Post Graduation drop down. 58. User does not select any course from the Course For Post Graduation drop down. 59. User enters their valid year of graduation in the Year of Post Graduation field. There should be a minimum gap of 2 years, in the Year of Post Graduation and Year of Post Graduation 60. User enters an invalid year of graduation in the Year of Post Graduation field. 61. User does not enter any year of graduation in the Year of Post Graduation field. 62. The user uploads a valid certificate of graduation in the Upload Certificate of Post Graduation in the acceptable JPEG,PNG or PDF formats. 63. The user uploads an invalid certificate of graduation in the Upload Certificate of Post Graduation in other unacceptable formats. 64. The user doesn't upload any file. 65. To add a Certification, the user would click the + sign. User clicks the University of Certification field and enters an valid University. 66. User clicks the University of Certification field and enters an invalid University. 67. User does not enter any value in the University of Certification field. 68. User chooses the valid course from the Course For Certification drop down. The user must ideally select MPT Course. 69. User chooses the invalid course from the Course For Certification drop down. 70. User does not select any course from the Course For Certification drop down. 71. User enters their valid year of graduation in the Year of Certification field. There should be a minimum gap of 2 years, in the Year of Certification and Year of Certification 72. User enters an invalid year of graduation in the Year of Certification field. 73. User does not enter any year of graduation in the Year of Certification field. 74. The user uploads a valid certificate in the Upload Certificate Proof in the acceptable JPEG,PNG or PDF formats. 75. The user uploads an invalid certificate in the Upload Certificate Proof in other unacceptable formats. 76. The user doesn't upload any file. 77. On clicking the Next Button, if any of the mandatory fields are invalid or skipped by the user, pop-ups will be displayed to fill the respective field. Only in case of valid scenarios the user would be able to navigate to the Next Page i.e. Business In... 78. On clicking the Next Button, if any of the mandatory fields are invalid or skipped by the user, pop-ups will be displayed to fill the respective field. Only in case of valid scenarios the user would be able to navigate to the Next Page i.e. Business In... 79. User enters an invalid PAN number and PAN Name in the Enter PAN Number and Enter Full Name as per PAN Card fields respectively. 80. User doesn't enter any value in the PAN Number or the Name in Enter PAN Number and Enter Full Name as per PAN Card fields respectively. 81. Mandatory field: User clicks on the Click here to verify PAN Number link for verifying the PAN. 82. User does not click on the Click here to verify PAN Number link for verifying the PAN. 83. Mandatory field: The user uploads a valid PAN Card in the Upload PAN Card in the acceptable JPEG,PNG or PDF formats. 84. The user uploads an invalid certificate of graduation in the Upload PAN Card in other unacceptable formats. 85. The user doesn't upload any file. 86. Mandatory field: While filling the GST Information, in Do you have a GSTIN? field, the user needs to opt if they possess a GSTIN or not, by clicking on YES or NO respectively. User clicks YES. 87. While filling the GST Information, in Do you have a GSTIN? field, the user needs to opt if they possess a GSTIN or not, by clicking on YES or NO respectively. User clicks NO. 88. Mandatory field: The user uploads a valid GST certificate in the Select a file from your device in the acceptable JPEG,PNG or PDF formats. 89. The user uploads an invalid GST certificate in the Select a file from your device in other unacceptable formats. 90. The user doesn't upload any file. 91. Mandatory field: If the user clicks NO, the user enters a valid Business Entity information in the Business Entity Information field. 92. If the user clicks NO, the user enters an invalid Business Entity information in the Business Entity Information field. 93. Mandatory field: If the user clicks NO, the user enters a valid Business Entity Address in the Business Entity Address field. 94. If the user clicks NO, the user enters an invalid Business Entity Address in the Business Entity Address field. 95. Mandatory field: User enters a valid beneficiary name in the Beneficiary Name field. This field only accepts characters. 96. User enters an invalid beneficiary name in the Beneficiary Name field. 97. User does not enter any value in the Beneficiary Name field. 98. Mandatory field: User enters a valid account number, in the Enter Account Number field. 99. User enters an invalid account number, in the Enter Account Number field. 100. User does not enter any number, in the Enter Account Number field. 101. Mandatory field: User enters a valid IFSC Code, in the IFSC Code field. 102. User enters an invalid IFSC Code, in the IFSC Code field. 103. User does not enter any Code, in the IFSC Code field. 104. Mandatory field: User clicks on the Click here to verify your IFSC Code link for verifying the PAN. 105. User does not click on the Click here to verify your IFSC Code link for verifying the PAN. 106. User skips filling the Business & Banking Information, by clicking the SKIP NOW button. In this case, when the user logs in, he will have to fill the Business & Banking Information first, only then the user will be able to proceed any further. 107. User doesn't skip filling the Business & Banking Information, and doesn't click the SKIP NOW button. 108. On clicking the Next Button, if any of the mandatory fields are invalid or skipped by the user, pop-ups will be displayed to fill the respective field. Only in case of valid scenarios the user would be able to navigate to the Next Page i.e. Set Passwor... 109. As soon as the user moves from the Business Information to the Set Password, the progress bar on the top of the page would be highlighted in green till the Business Information page. 110. On clicking the Next button, user will land to the Set Password page, where user will enter an invalid password in the Password field. 111. Once the user sets password in the Password field, user will confirm the password, by entering an invalid password in the Confirm Password. 112. Mandatory field: The user clicks on the Complete Registration button and the completes the registration process. 113. On clicking the Next button, user will land to the Set Password page, where user will enter an either a valid or an invalid password in the Password field. 114. Once the user sets password in the Password field, user will confirm the password, by entering the a password in the Confirm Password, that doesn't match the Password field. 115. The user clicks on the Complete Registration button and the registration process is incomplete. 116. On clicking the Next button, user will land to the Set Password page, where user will NOT enter a password in the Password field. 117. User will NOT enter a password in the Confirm Password field. 118. The user clicks on the Complete Registration button and the registration process is incomplete. 119. Mandatory field: On clicking the Next button, user will land to the Set Password page, where user will enter a valid password in the Password field. 120. Mandatory field: Once the user sets password in the Password field, user will confirm the password, by entering the same valid password in the Confirm Password. 121. Mandatory field: The user clicks on the Complete Registration button and the completes the registration process. 122. Post, successful registration, a Successful registration message will be displayed on the screen. Along with a Back to Login button, where the user clicks the button and the page navigates to the Login page. 123. Post, successful registration, a Successful registration message will be displayed on the screen. Along with a Back to Login button, where the user does NOT click the button and the flow would not move any further. 124. As soon as the user moves from the Educational Information to theBusiness & Banking information, the progress bar on the top of the page would be highlighted in Yellow for the Basic Information page. 125. User check registration screen header spelling and name of the screen 126. User check the size of information cart of CO, PP,PI AND FDM as per provided Xd 127. Check the name alignment and placement of the Practicing physio or chosen role name for registration 128. Check the name reflecting or shown should be same as chosen role name for registration "19 The system shall support the creation of new (CAAMS) accounts for users whose names contain special characters or symbols. The process of creating these accounts shall be handled by a BOT to ensure accuracy and compliance with data entry requirements.,1. Verify the successful creation of the account when Applicant Name has & character 2. Verify the successful creation of the account when Applicant Name has single inverted comma 3. Verify the successful creation of the account when Applicant Name doesn't have special character 20" Admins have access to the sub module to view,download, print employee’s pay slip.",1. Evaluate the 'Payslip' tab functionality when Admin clicks on it. 2. Examine the 'Year' dropdown functionality of 'Payslip' module. 3. Make sure the 'Month' dropdown functionality of 'Payslip' module. 4. Determine the 'Go' button functionality of 'Payslip' module. 5. Confirm the 'Download' button functionality of the 'Payslip' module. 6. Certify the 'Print' button functionality of 'Payslip' module. 21" “Paysqaure output” submodule is developed to add monthly payslip sheet for employees. Functionalities like download and edit, and monthly salary report added. In “Paysqaure output report” module has two tabs i.e. “Upload Payslip” and ...",1. Ensure that the admin can upload the Excel file only in .xlsx format using the upload functionality. 2. Confirm the 'Download' button functioning. 3. Examine the uploaded data is proper as in the excel file using 'Edit' button. 4. Evaluate admin can replace the already present data in any field using the 'Edit' functionality. 5. Make sure the admin can close the Update Bank Details popup window by clicking the close button. 6. Validate the Show entries functionality on every data table under the Upload Payslip module. 7. Validate the admin can search the records by using the search functionality. 8. Validate the admin can edit the payslip records by using edit button. 9. Make sure the working of upload button with an unsupported file format. 10. Make sure all the data present in the excel file while uploading is displaying in the tabular format in the paysquare output module by clicking on the edit button. 11. Make sure how the upload functionality operates if column names are saved in the case-sensitive format in the Excel sheet. 12. Evaluate the edit page presence of the pay-square output module. 13. Confirm the Generate Intern Salary Report button is clickable. 14. Examine admin can generate all intern's records by clicking on the Generate Intern Salary Report button. 22" The Search Payslip module's aim is to search for employee payslip details by entering the employee's staff ID, financial year, and month..",1. Evaluate the Search Payslip tab which is present under the 'Payslip Output' module is clickable. 2. Confirm that the breadcrumbs are place on top of the page is functional. 3. Make sure that the current page location is highlighted in the breadcrumbs. 4. Confirm Staff Id field only accepts the number inputs. 5. Examine the Year dropdown workability. 6. Evaluate admin can search the payslip for an employee for a specific year and month. 7. Make sure the functionality of the Month dropdown. 8. Examine the Back button functionality from the Search payslip screen. 9. Make sure of the Next button working from the Search payslip page. 23"This module will be displaying employee’s previous appraisal information in the table format. Actions like “View”, ‘Reminder’ and appraise admin should be able to perform task in an appraisal dashboard.","1. Make sure Employee salary revision, Annual salary history, and Graphical representation buttons are available on the screen with proper alignment and labelling. 2. Confirm that the admin can view the Active and Inactive records. 3. Examine that the entries for the selected number are in the show entries. 4. Ensure that admin can search the data in the search box and output display in the tabular format. 5. Make sure that display a pop-up screen of appraisal details for the employee after clicking on the view icon. 6. Examine that admin can download the appraisal report by clicking on the Download button. 7. Ensure that the admin has access to the Appraisal screen by clicking on the Appraise button. 8. Make sure that the admin can view the appraisal reminder details/form of the employee by clicking the reminder icon. 9. Ensure that all fields are editable except staff id and employee name in add reminder pop window and also make sure about how add reminder works. 10. Verify that pagination is available at the bottom of the page. 11. Determine admin can edit the updated salary details using the Edit functionality present in the View button. 12. Examine the alignment of the Inactive tab screen present under the Appraisal module and also confirm the table present on the screen has the date of departure column along with other columns. 13. Examine that the entries for the selected number are in the show entries. 14. Ensure that admin can search the data in the search box and output display in the tabular format. 15. Make sure that display a pop-up screen of appraisal details for the employee after clicking on the view icon. 16. Ensure that the admin has access to the Appraisal screen by clicking on the Appraise button. 17. Make sure that the admin can view the appraisal reminder details/form of the employee by clicking the reminder icon. 18. Ensure that all fields are editable except staff id and employee name in add reminder pop window and also make sure about how add reminder works. 19. Verify that pagination is available at the bottom of the page. 20. Confirm 'Back' button's working present on the Employee Salary Details screen for the Inactive records. "24 The purpose of this module is to enter salary revision details.,"1. Make sure that after clicking the appraise button, it redirects to the appraisal screen or not. 2. Ensure that excluding 'Effective Date' all other fields will be disabled after selecting the Salary Revision as 'No'. 3. Examine that the the fields are eligible to get modified if Admin selects Yes option from the 'Salary Revision' dropdown. 4. Make sure that the admin can select the revision types from the 'Revision Type' dropdown box. 5. Evaluate that the Effective date had changes automatically according to the selection of the 'Revision Type'. and make sure admin can select the dates manually also. 6. Ensure that the Revised Gross Earning (CTC) field accepts a maximum of 8-digit integer numbers in decimal format. 7. Examine the error messages when the admin tries to click the Next and Revise buttons without inputting the CTC. 8. Confirm that the variable pay field is editable and accepts only numeric values. 9. Ensure that the administrator can select an employee's designation from the New Designation field dropdown. 10. Make sure that all data will save, and admin will redirect to the 'Salary Revision' screen by clicking on the Revise button. 11. Check that the admin will redirect to the previous page by clicking on the Back button. 12. Make sure the functionality of view icon for the non completed appraisal entries. "25To display salary breakup table and salary distribution rate. Admin can update salary distribution rate.,1. Confirm admin will land on 'Salary Revision' tab screen when 'Revise' button clicked from the Appraisal tab screen. 2. Ensure the Admin is able to update the 'Salary Distribution Rate %'. 3. Confirm that the 'Salary Break-Up' will update as per the 'Salary Distribution Rate'. 4. Examine all data will update and the Appraisal Letter screen will appear by clicking on the 'Update & Next' button. 5. Evaluate how the 'Preview' button functions when the admin clicks on it. 6. Confirm that the 'Back' button takes the admin to the 'Appraisal' screen. 26 The “Appraisal Letter” module is created to send an appraisal letter to an employee. Functionality like selecting appraisal letter and email template is added.,"1. Examine the functionality of 'Appraisal Letter' tab. 2. Evaluate the Admin can see selected employee's information on 'Appraisal' screen header. 3. Ensure 'Select template' dropdown workability 4. Make sure the email is sent successfully to the employee with correct information. 5. In the Letter Generated On calendar, make sure the admin can only choose dates that are greater than the current date. 6. Confirm how the Appraisal Letter Email Date field works. 7. Ensure the functioning of the Select Email Template dropdown from the 'Appraisal' screen. 8. Make sure 'Preview' button gives the selected 'Appraisal Letter' and 'Appraisal email' preview with Back and Download buttons. 9. Confirm the Download button on the Preview screen downloads the all Appraisal information in PDF format. 10. Admin can re-navigate to the 'Appraisal' screen using the 'Back' button from the 'Preview' screen, confirm this. 11. Ensure the toggle button can enable and disable the 'Letter head preview' from the preview screen. 12. Evaluate the working of the 'Final preview' button without saving the selected templates of Appraisal. 13. Confirm that the admin has the ability to use the Save button to save the chosen templates and data. 14. Examine the 'Back' button from the 'Appraisal' screen can lead admin to the salary revision screen. 15. 'Final preview' button gives the right to admin to navigate on the final 'Appraisal letter' process. 16. Make sure all the saved data of the Appraisal letter and email displays correctly. 17. Download button can download the Appraisal letter and email in the PDF format. 18. Toggle button can enable/disable the Letter head preview, check that. 19. Confirm that the 'Back' button on the page redirects admin to the previous screen. 20. Examine the functionality of the 'Send Increment Letter' button. 21. Ensure that the Selected Template for Appraisal letter and Email can not be saved until the official email ID, Date of birth, and Pan card number are present in the RMS for an employee. "27 User will be eligible to access the application after successful login and will visit Full open list under module open list as default dashboard page.,1. Validate the login function when a user enters the valid credentials. 2. Validate the login function when a user enters Invalid credentials. 28" User will need patient's name, mobile number and a dropdown for selecting the physiotherapist.","1. Ensure that user has access to create and do modifications in particular operations of each and every module from the calendar and appointments. 2. The user has an access to open the Block appointment module in the calendar and appointments. 3. In the block appointment module, the user needs to fill in some information to enroll new patients in the business. 4. Without filling any information in the new patient form if the user clicks on the Next button. 5. The user just fills the Full name on the form and clicks on the Next button of the form 6. In case a user has just filled the Full name and assigned the Physiotherapist for that patient from the dropdown and clicks on the Next button 7. The user who has blocked an appointment for the patient, if the user enters the full name and mobile number without assigning the physio clicks on the Next button. 8. To add the new patient and also to block the appointment, the user needs to enter certain information about patient. 9. The user can book an appointment for his/her existing patient only. 10. The user tries to block an appointment for the patient who has existing at the clinic but is treated by the other physiotherapist. 11. The user have an access to block appintment for the patient which has already existing patient of any physiotherapist of the clinic. 12. The user has to block appointments for a particular time for the existing patient of the clinic. 13. The FDM can block the appointment for the patient of any employee of the clinic. 14. With the registered app user option, the user can block the appointments for patients which have been treated by another business clinic. 15. The physio can block the appointment of the patient through the registered app user option. 16. On the screen of select physiotherapist, with the default selected screen the physio names are displayed. 17. The user selected the base name, and for there related physiotherapist name are needs to be displayed on the screen. 18. FDM can work in only one clinic, that’s why default clinic name are selected and which employees are working for that clinic that physiotherapist names details are shows 19. The user can book an appointment for themselves patients and for that condition the automaticly the name will be selected and the screen is shows the select slots. 20. The physiotherapist has set the schedule for clinic then on the select slots screen only clinic option has access. 21. In case a user is working as only home visits then the Home visits screen and selected base are displayed on the screen. 22. To select the slots of the particular physiotherapist, needs the select the clinic or home option, it's an important for clinic or home visits. 23. The Physiotherapist has to block the appointment for his/her patient there needs to select the slots. 24. The user needs to check the Confirmation details of the blocking appointments and clicks on the confirm button. 25. In case the information is displayed that is wrong then the user go back and change accordingly and again complete the flow. 26. The user wants to book an appointment for an existing patient and after that he/she confirms the blocked appointment details. "29 The system shall provide a mechanism to regularly check and validate the indexing of Large Objects (LOBs) in the Information Processing System (IPS). This functionality is essential to ensure that LOBs are correctly indexed and can be efficiently retrie...,1. Verify the Indexing of all LOBs in IPS when the policy is not declined 2. Verify the Indexing of LOB in IPS in case policy is declined and more than one LOB is available among the priority list. 3. Verify the Indexing of LOB in IPS in case policy is declined and LOB is other than priority list. 30"The system shall provide functionality to create tasks in the (CAAMS) for policies that have undergone processing, and their associated Large Objects (LOBs) are indexed. This functionality is essential to ensure that post-processing tasks are initiated...","1. Verify that Bot has created the Caams task for every LOB, for successful non declination cases submission. 2. Verify that Bot has not created the Caams task for the LOB submission and policy is declined. "31" The system shall provide functionality to update Large Object (LOB) Product and LOB Subtype information in the (CAAMS). This functionality is essential to keep LOB information accurate and up-to-date, reflecting changes or modifications as needed.","1. Verify Lob Product field is updated in CAAMS after successful lob submissions 2. Verify LobSubType field is updated in CAAMS after successful lob submissions. 3. Verify Lob SubType field is updated in CAAMS after successful lob submissions for multiple lob submissions. 4. Verify for General liability(GL) Lob to pass lob subtype and verify the lob subtype is being reflected in CAAMS, 5. Verify for General Liability(GL) Lob, not to pass the lob subtype in Extract UI and verify the lob product is being reflected in CAAMS, "32" The system shall provide functionality to update Contact Name and Contact Phone Number information in the (CAAMS). This functionality is essential to keep contact information accurate and up-to-date, reflecting changes or modifications as needed.",1. Verify to ensure that the contact name reflected in CAAMS when passed in Contact Name (WC Accord) Field 2. Verify to ensure that the contact number in CAAMS when passed in PhoneNumber (WC Accord) Field 33The system shall ensure that Large Objects (LOBs) submitted in the (CAAMS) are accurately and promptly reflected in the Underwriting Workstation (UWWS). This functionality is crucial to provide underwriters with up-to-date information for processing and...,1. Verify all the lob submitted in CAAMS are reflected in UWWS applications. 34 Request raised by the employees for training batches can be approved or rejected by the administrator also admin shall be able to get a view of requests based on the status.,"1. Make sure that on clicking view icon, view training request popup window open and all the details of request are appear. 2. Test the functioning of accept request icon, on clicking it training request must be accepted. 3. Check if user click on reject request icon then Request Rejected Successfully! popup appear and status appear as rejected in data table. 4. Ensure that once user perform action on training request then only view icon appear in action column. 5. Check if user entered any valid data in search field to search then data related to that searched data is appear. 6. Examine the functionality of search field if user entered invalid data in search field to search. 7. Demonstrate that the next (>>) indicator is active in order to move to the next page and if current page is last page then next indicator is disable. 8. If the user wants to go back to the previous page, make sure the previous indicator (<<) is active and if the user is on the first page, make sure it is disabled. 9. Check that the current page number is highlighted. 10. Ensure the size of numbers, font , color is as per specification. 11. Test the functionality of show entries dropdown whether it is showing selected number of entries. 12. To navigate from one page to another, make sure that the breadcrumb is working properly. 13. Check the functionality of status filter , whether it is showing data for selected status only. "35 Same login page for admin and employee. Allow users to login successfully with valid credentials and access the application to take advantage of various facilities and services provided by RNT organization,1. To verify that the user can successfully navigate to the Main Dashboard by entering valid credentials and clicking the login button. 2. Ensure that the user cannot log in when providing incorrect data in any of the fields. 3. Validate the functionality of login button on entering valid username and invalid password 4. Make sure that user will not be able to login by providing invalid data in both the fields 5. To ensure that the user is presented with an alert message if they fail to enter data in any of the login field 36"With the help of service management system employee and admin can request for the IT services, and admin user has access to provide, accept and resolve those tickets sent by the employees and admin as well, as per ServiceNow ticketing tool",1. Verify the service management system application and by hitting on that user navigates to the dashboard of the RNT Service Management System 37"The admin user can effectively manage incident requests by allowing them to create incident requests for themselves or on behalf of other employees, view incident requests based on different statuses, and successfully resolve them.",1. To verify whether the admin user can see the list of all submodules under the Incident module by clicking on it. 38" Allow the admin user to create new incident record with prefilled unique incident request number, Caller name, Category- dropdown, Subcategory dropdown, Configuration item, Channel dropdown, State drop down, Impact dropdown, Urgency dropdown, Assignment...",1. To ensure that the admin user can view the incident record form by accessing the Create New Incident submodule 2. Examine the purpose of caller field the admin user can see the list only after entering valid data 3. To ensures that the admin user can initiate the incident request creation process and provide all the necessary information to raise the request. 4. Check the performance of Submit button without filling mandatory fields 5. Validate that admin user can upload the screenshot of the issue from their system 6. Click and check the functionality of breadcrumbs present on the page 39"Admin user has access to see the created incident requests in tabular form list with search and sort functionality, And admin user can resolve those incidents by clicking on incident number and filling the resolution information like, Resolved by, Resol...","1. Evaluate that admin is navigating on Assigned By Me incident record list by pressing on Assigned By Me submodule 2. Click and check the functionality of breadcrumbs present on the page 3. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries of incidents appear only 4. Ensure that selected number of entries from the dropdown must be appear only 5. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 6. Validate that by clicking on pagination buttons admin user is navigating to respective page or not 7. By clicking on Incident Number, Confirm the process of Update button, the admin user can edit all the fields excluding Caller and Number and also admin can add the work notes 8. Make sure that admin user can resolve the incident ticket by updating the fields and filling the Resolution Information 9. Check the functioning of Resolved state without filling the Resolution Information 10. Examine the purpose of Reset button, the updated data should get clear only, by clicking on it 11. Verify the functioning of Update button without filling the mandatory fields "40 Admin user has access to resolve the incident requests which are assigned to him display in tabular format list with search and sort functionality and export to PDF functionality enabled with it. admin user can update the incident request Resolution Inf...,"1. Validate the functioning of Assigned To Me submodule by clicking on it the list of incidents assigned to the respective person should get open 2. Click and check the functionality of breadcrumbs present on the page 3. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries of incidents appear only 4. Ensure that selected number of entries from the dropdown must be appear only 5. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 6. Validate that by clicking on pagination buttons admin user is navigating to respective page or not 7. By clicking on Incident Number, Confirm the process of Update button, the admin user can edit all the fields excluding Caller and Number and also admin can add the work notes 8. Make sure that admin user can resolve the incident ticket by updating the fields and filling the Resolution Information 9. Check the functioning of Resolve state without filling the Resolution Information 10. Test the functionality of Update button without filling the mandatory fields 11. Make sure the functioning of Reset button by changing or adding the data "41"Admin module to add new vendor, trainer with respect to the added vendor, mode of batches to delivered for user, category of trainings. Added details in the admin module must be presented in the existing modules selection.","1. To add data in training type submodule, make sure that the Add button is working properly. 2. Check the functionality of edit icon if user want to make changes in already existing data. 3. Examine the functionality of delete icon if user want to delete data which is not in use. 4. Analyze the delete functionality if user want to delete data which is in use. 5. Check if user entered any valid data in search field to search then data related to that searched data is appear. 6. Examine the functionality of search field if user entered invalid data in search field to search 7. Demonstrate that the next (>>) indicator is active in order to move to the next page and if current page is last page then next indicator is disable. 8. If the user wants to go back to the previous page, make sure the previous indicator (<<) is active and if the user is on the first page, make sure it is disabled. 9. Check that the current page number is highlighted. 10. Ensure the size of numbers, font , color is as per specification. 11. Test the functionality of show entries dropdown whether it is showing selected number of entries. 12. To navigate from one page to another, make sure that the breadcrumb is working properly. 13. Analyze the functionality of add button used to add delivery mode in delivery mode submodule 14. Ensure the functionality of edit icon, if user wants to modify already existing delivery mode. 15. Check the functionality of delete icon if user wants to delete delivery mode which is not in use. 16. Check the functionality of delete icon if user want to delete delivery mode which is in use. 17. Examine the functionality of add button if user added already existing delivery mode. 18. Determine the functionality of Add button if user added data which is already existing. 19. Analyze the functionality of Add button if user want to add data in vendor submodule 20. Determine the functionality of edit icon if user wants to modify existing data. 21. Check if user wants to delete vendor data which is not in use. 22. Examine delete icon functionality if user wants to delete vendor details which is in use. 23. Determine the functionality of add button if user added data which is already existing. 24. If user want to add data in trainer submodule, make sure that add button is functional. 25. If user wants to modify details of any trainer, then make sure that user must be able to do that by using edit icon. 26. Check the functionality of delete icon if user want to delete trainer data which is not in use. 27. Check the functionality ,If user want to delete trainer data which is currently in use. 28. Examine the functionality of add button if user added duplicate entry. 29. Check that name of the submodule , icon of edit and delete functionality are appear properly in alignment or not. 30. Check the functionality of adding external trainer. 31. Analyze the functionality of edit icon used to edit external trainer details. "42" Admin user has access to see the open incidents list created by admin and employee in tabular form with search, sort and export to PDF functionality enabled with it. Resolution Information:- By clicking on incident number from the list admin user can f...","1. Verify that the Open submodule functions as intended by clicking on it; a list of all Open incidents made by user and admin should appear 2. Check the operating purpose of Breadcrumbs, admin user can navigate to the respective page by hitting on it 3. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries of incidents appear only 4. Ensure that selected number of entries from the dropdown must be appear only 5. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 6. Validate that by clicking on pagination buttons admin user is navigating to respective page or not 7. By clicking on Incident Number, Confirm the process of Update button, the admin user can edit all the fields excluding Caller and Number and also admin can add the work notes 8. Make sure that admin user can resolve the incident ticket by updating the fields and filling the Resolution Information 9. Check the functioning of Resolve state without filling the Resolution Information 10. Test the functionality of Update button without filling the mandatory fields 11. Make sure the functioning of Reset button by changing or adding the data "43"Admin user has access to see the unassigned incidents list created by admin and employee in tabular form with search, sort and export to PDF functionality enabled with it. Resolution Information:- By clicking on incident number from the list admin user...","1. Test the functionality of Open-Unassigned submodule, the list of the incident tickets which are not assigned to anyone can open by clicking 2. Click and check the functionality of breadcrumbs present on the page 3. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries of incidents appear only 4. Ensure that selected number of entries from the dropdown must be appear only 5. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 6. Validate that by clicking on pagination buttons admin user is navigating to respective page or not 7. By clicking on Incident Number Confirm the process of Update button, the admin user can edit all the fields excluding Caller and Number and also admin can add the work notes 8. Make sure that admin user can resolve the incident ticket by updating the fields and filling the Resolution Information 9. Check the functioning of Resolve state without filling the Resolution Information 10. Make sure the functioning of Reset button by changing or adding the data 11. Ensure that without filling the mandatory field incident should not get update "44" Admin user has access to see the unassigned incidents list created by admin and employee in tabular form with search, sort and export to PDF functionality enabled with it. admin user can update the incident request","1. Check that the Resolved submodule functions as intended by clicking on it; a list of all Resolved incidents resolved by user and admin appears on the screen 2. Check the operating purpose of Breadcrumbs, admin user can navigate to the respective page by hitting on it 3. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries of incidents appear only 4. Ensure that selected number of entries from the dropdown must be appear only 5. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 6. Validate that by clicking on pagination buttons admin user is navigating to respective page or not 7. Make sure the functionality of Update button, by changing and adding the information 8. Verify the purpose of Close button, by pressing on it the Incident request should get closed 9. Evaluate the functionality of Update button without filling mandatory fields 10. Make sure the functioning of Reset button by changing or adding the data "45"Admin user has access to see the all incident requests list in tabular form with search, sort functionality enabled with it. Admin user can update the incident request. Resolution Information:- By clicking on incident number from the list admin user ...","1. Make sure that by hitting on All submodule the admin user is navigating to the All incidents list 2. Examine the incident ticket which having the state Closed that record will be read only and should not get update 3. Check the operating purpose of Breadcrumbs, admin user can navigate to the respective page by clicking on it 4. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries of incidents appear only 5. Ensure that selected number of entries from the dropdown must be appear only 6. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 7. Validate that by clicking on pagination buttons admin user is navigating to respective page or not 8. By clicking on Incident Number Confirm the process of Update button, the admin user can edit all the fields excluding Caller and Number and also admin can add the work notes 9. Make sure that admin user can resolve the incident ticket by updating the fields and filling the Resolution Information 10. Check the functioning of Resolve state without filling the Resolution Information 11. Evaluate the functionality of Update button without filling mandatory fields 12. Make sure the functioning of Reset button by changing or adding the data "46"Employee can create self incident request and can see the created incident request in tabular format list and also view the incident request status like, Resolved, In-process",1. By clicking on Incident module the submodules present in that can be display 47" Allow the Employee user to create new incident record with prefilled unique incident request number, and opened date and time, read only Caller name, State dropdown, Urgency dropdown, short description. While clicking on another tab or module a popup w...","1. Evaluate that the Employee user can see the incident record form by hitting on Create New Incident submodule 2. Make sure the alignment of all the fields are proper or not 3. Check and validate that the Caller, Number and Opened fields are read only 4. Check and make sure that the Closed field is not clickable and empty 5. Validate the functioning of the Submit button by filling the necessary data 6. Ensure the performance of Submit button without filling mandatory fields 7. Examine the working of Reset button, by clicking on it, the incident record page should get reset 8. Click and check the functionality of breadcrumbs present on the page "48" Employee user can view the created incidents record in tabular format list with search, sort functionality enabled with it.","1. Confirm that by pressing on All submodule, the list of all created incidents should get appear 2. Check the operating purpose of breadcrumbs, user can navigate to desired page with single click 3. Examine by entering valid data then regarding entries of incidents should appear on the page 4. Ensure the performance of Show Entries by selecting the number then same or if not available then less than selected number of entries get visible 5. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 6. Make sure by clicking on paginations user is navigating to respective pages 7. By clicking on Incident Number confirm the process of Update button, user can update the state and urgency, upload the attachments and also post the additional comments 8. By pressing on Incident number confirm the functioning of Reset button that user can reset the updated data 9. By clicking on Incident Number Ensure the performance of Back button, user should navigate to the back page 10. Evaluate that user can resolve the self created incidents by selecting the state Resolved 11. Test the functionality of Reopen button without posting the additional comments 12. Verify and validate by posting the additional comments and clicking on Reopen button the incident ticket should get reopen 13. Make sure by clicking on Close button, the incident should get closed "49"Admin user should be able to view clickable cards named Incidents Opened today, Unassigned Incidents, Overdue Incidents, Open Incidents, Incidents not updated for 7 days, Open incidents older than 30 days, filter based on Incident priority, Incident sta...","1. Check the Overview submodule, by clicking on it the Incident overview page can display 2. Verify the purpose of Incident Opened Today card, by clicking on it the incidents created by today can display 3. Confirm the process of Show entries dropdown by selecting the number, same or if not available then less than the selected number of entries can display 4. Test the Search textbox is functioning fine while entering the valid data 5. By inputting invalid data into the Search textbox test the operating purpose of search field 6. Determine the operating function of paginations and by hitting on it admin can navigate to respective pages 7. Verify the feature of Breadcrumbs, by pressing on it user can navigate to desired page 8. Test the functionality of Open Incidents Grouped graph by selecting the filter from Group By dropdown observe the functioning of graph 9. Test the functionality of Open Incidents older than 30 days graph by selecting the filter from Group By dropdown list observe the functioning of graph 10. Verify the Incidents per week graph by hovering the mouse on pointer the incident raised count of the week should appear 11. Check the functioning of all the filters by selecting the item from the dropdown the cards get sorted respectively 12. By clicking on Incident Number, Confirm the process of Update button, the admin user can edit all the fields excluding Caller and Number and also admin can add the work notes and additional comments 13. Make sure that admin user can resolve the incident ticket by updating the fields and filling the Resolution Information 14. Check the functioning of Unassigned Incidents by clicking on it the list of unassigned incident should get display 15. Confirm the process of Show entries dropdown by selecting the number, same or if not available then less than the selected number of entries can display 16. Test the Search textbox is functioning fine while entering the valid data 17. By inputting invalid data into the Search textbox test the operating purpose of search field 18. Determine the operating function of paginations and by hitting on it admin can navigate to respective pages 19. Verify the feature of Breadcrumbs, by pressing on it user can navigate to desired page 20. By clicking on Incident Number, Confirm the process of Update button, the admin user can edit all the fields excluding Caller and Number and also admin can add the work notes and additional comments 21. Make sure that admin user can resolve the incident ticket by updating the fields and filling the Resolution Information 22. Check the functioning of Overdue Incidents card by clicking on it the list of Incidents which are not resolved by last 10 days will get display 23. Confirm the process of Show entries dropdown by selecting the number, same or if not available then less than the selected number of entries can display 24. Test the Search textbox is functioning fine while entering the valid data 25. By inputting invalid data into the Search textbox test the operating purpose of search field 26. Determine the operating function of paginations and by hitting on it admin can navigate to respective pages 27. Verify the feature of Breadcrumbs, by pressing on it user can navigate to desired page 28. By clicking on Incident Number, Confirm the process of Update button, the admin user can edit all the fields excluding Caller and Number and also admin can add the work notes and additional comments 29. Make sure that admin user can resolve the incident ticket by updating the fields and filling the Resolution Information 30. Determine the working of Open Incidents card, confirm it by pressing on it the all over data of incidents requests should visible 31. Confirm the process of Show entries dropdown by selecting the number, same or if not available then less than the selected number of entries can display 32. Test the Search textbox is functioning fine while entering the valid data 33. By inputting invalid data into the Search textbox test the operating purpose of search field 34. Determine the operating function of paginations and by hitting on it admin can navigate to respective pages 35. Verify the feature of Breadcrumbs, by pressing on it user can navigate to desired page 36. By clicking on Incident Number, Confirm the process of Update button, the admin user can edit all the fields excluding Caller and Number and also admin can add the work notes and additional comments 37. Make sure that admin user can resolve the incident ticket by updating the fields and filling the Resolution Information 38. Establish the incidents which are not updated by 7 days is visible only, by hitting on the Incidents not updated for 7 days card 39. Confirm the process of Show entries dropdown by selecting the number, same or if not available then less than the selected number of entries can display 40. Test the Search textbox is functioning fine while entering the valid data 41. By inputting invalid data into the Search textbox test the operating purpose of search field 42. Determine the operating function of paginations and by hitting on it admin can navigate to respective pages 43. Verify the feature of Breadcrumbs, by pressing on it user can navigate to desired page 44. By clicking on Incident Number, Confirm the process of Update button, the admin user can edit all the fields excluding Caller and Number and also admin can add the work notes and additional comments 45. Make sure that admin user can resolve the incident ticket by updating the fields and filling the Resolution Information 46. Test the functionality of Open Incidents older than 30 days card, by pressing on it the incident which are not resolved should get display 47. Confirm the process of Show entries dropdown by selecting the number, same or if not available then less than the selected number of entries can display 48. Test the Search textbox is functioning fine while entering the valid data 49. By inputting invalid data into the Search textbox test the operating purpose of search field 50. Determine the operating function of paginations and by hitting on it admin can navigate to respective pages 51. Verify the feature of Breadcrumbs, by pressing on it user can navigate to desired page 52. By clicking on Incident Number, Confirm the process of Update button, the admin user can edit all the fields excluding Caller and Number and also admin can add the work notes and additional comments 53. Make sure that admin user can resolve the incident ticket by updating the fields and filling the Resolution Information "50"Employee shall be able view the list the completed, ongoing courses. Relevant recommended courses based on the employee designation shall be displayed. Notification to get the update of actions performed over the user's request.","1. Check the count appear in overview is accurate or not? 2. Check the functionality of recommended courses tab, in which all the courses which are recommended for specific role or multiple role are appear in this tab. 3. Examine the functionality of ongoing courses tab, in which all the trainings which are currently active are appear as well as progress status of particular training is appear in percentage with duration date on training card. 4. Determine the functionality of completed courses tab, in which all the courses which duration is complete and the courses for which user have submitted progress as 100% with certificate(For online course) are appear. 5. Analyze the functionality of dropdowns if user wants to see the batches according to selected month and year. 6. Examine the functionality of search field if user entered valid data to search. 7. Analyze the search field functionality if user entered invalid data to search. 8. Check the functionality of What's new button. "51" List of ongoing training batches, pinned batches and so far attended batches to be displayed of respective employees as per status of batch, employee shall have access to select the batches as per monthly or yearly basis in Training Calendar module.","1. Make sure that the user can apply for a batch, and after clicking apply, the user must navigate to the pending nominations tab in the Enrolled batches module. 2. If user want to see the details of batches then ensure that user is able to see details by using view more option visible on mouse hover on batch card. 3. Ensure the functionality of pin, if user click on pin visible on mouse hover on batch card then user must be navigate to pinned batches tab. 4. Check the functionality of pinned batches, on clicking on pin that batch must be unpinned and user navigate to training batches tab also that unpinned batch appear in training batches tab. 5. Ensure that in pinned batches tab, apply now button is visible on mouse hover on batch card and user also able to apply for that batch. 6. In order to see all the details of attended batch, ensure that view more option is clearly visible and able to show all the details of batch. 7. If user wants to re-attend any course then user is able to attend by using visit link option available on batch card, check the functionality of visit link option. 8. Check the functionality of progress circle chart, whether it is showing accurate progress percentage on mouse hover on batch card. 9. Examine the functionality of search field if user entered valid data to search. 10. Examine the functionality of search field if user entered invalid data to search. 11. Analyze the month and year dropdown functionality, whether it is showing accurate batches according to selected month and year or not? 12. Make sure that breadcrumbs appear on page are functional. 13. If user wants to apply for already applied batch then ensure that on clicking apply button popup appear as Already Applied! 14. Analyze that initially if user clicked on training calendar module then month and year dropdown shows the current month and year. "52"Accepted, rejected and pending nominations of the employees are categorized in respective tabs based on their status, employee shall have access to view the list of nominations on monthly or yearly basis in Enrolled Training module.","1. Test the functionality of pending nominations tab by clicking on it. 2. Analyze the functionality of accepted nomination tab. 3. Check the View more button functionality , whether it is showing all the details of batch. 4. Determine the functionality of submit progress button 5. Analyze the functionality of view more option visible on mouse hover on batch card. 6. Examine the working of rejected nomination tab 7. Make sure that view more option is able to show all the batch details available in rejected nomination tab. 8. Determine the functionality of cancelled nomination tab. 9. Ensure the view more option functionality visible on mouse hover on batch card. 10. Ensure the functionality of the month and year dropdown, if user wants to see the nominations according to the selected month and year. 11. Examine the functionality of search field, if user entered valid data to search. 12. Determine the functionality of search field if user entered invalid data to search. 13. To navigate from current page to any other page , make sure that the breadcrumb is working properly. 14. Check the functionality of skip button and close window icon used to avoid feedback. 15. Check the functionality of start rating button. 16. Make sure that there is no skip or close window icon for offline batch as it is compulsory for offline trainings. 17. Check the functionality for online batch, if user has not added certificate and assignment and directly clicked on submit progress button. 18. Analyze the functionality if user has added assignment and certificate but still user click on upload certificate button and click on cancel. 19. Check the functionality for offline batch, if user has not uploaded certificate and assignment and directly click on submit progress button. "53"Employee shall be authorized to raise a new training request stating the training topic, delivery mode of training, shortlisting the type of training along with stating the justification of training. Track the status of request raised for training sessi...","1. Check the functionality if user want to raise request by using New Training Request button. 2. Examine the functionality of validation message , if user exceeds the limit of training topic text field. 3. Determine the functionality if user exceeds the limit of business justification field. 4. If user kept one of the field blank and click on raise request button. 5. Check if user entered invalid data in any field and click on raise request button 6. Check the navigation functionality that if user raised request then initially that request must be appear in pending request tab. 7. Check the functionality of the reset button used to clear all the entered or selected data. 8. Check the functionality of view button available on training request card in pending request tab 9. Check the functionality of month and year dropdown used to see raised training request calendar wise. 10. Check the functionality of search field by entering valid data in it. 11. Analyze the functionality of search field by entering invalid data in it. "54" This module is only accessible to the admin. Admin can generate bank reports and for the further bank process. After submitting the report, the bank will give a bank response, admin will upload the bank response salary details of the employees for the m...","1. Examine that the admin can select the year for generating the Bank report for that year from the Year dropdown. 2. Ensure that the admin can choose the month for generate the report. 3. Make sure that when admin click on generate report button without selecting an employee, a pop-up message display on screen. 4. Confirm the Show Entries functionality. 5. Evaluate that the edit icon is available to edit the records except the processed records. 6. Ensure that using the checkbox functionality, the admin can Select/Deselect a specific record or all of the records. 7. Make sure admin can search the data using the search functionality. 8. Confirm the selection of statuses from the Status dropdown and display the appropriate results accordingly. 9. Confirm the Bank Status Report button can be clicked and causes a pop-up window to appear by using it. 10. Check that admin can search the data in the search box and output display in the tabular format. 11. Make sure that the admin can download the bank status report (Processed and not processed) by clicking the download button. 12. Confirm that pagination is workable as expected. 13. Make sure the popup window can close after clicking the close button or close icon. 14. Examine the entries for the selected number in the show entries. 15. Confirm that the admin can view and edit the status of Not processed employees data by clicking on the view icon. 16. Evaluate that the breadcrumbs are placed on top of the page and its functioning. 17. Evaluate the admin can navigate to next and previous page by Next and Back button as well as from pagination also. 18. Ensure the consultant details will appear by clicking on Consultant tab. 19. Examine the columns for the Consultant records. 20. Validate the admin can generate the consultant records using the Generate Report button. 21. Confirm the admin can search the records using search functionality. 22. Examine the Salary Account Check screen. 23. Validate the Upload Bank Excel functionality. 24. Validate the Search functionality. 25. Examine the columns on the Salary Account Check screen. 26. Make sure the admin can edit the Salary account details. 27. Make Sure the title of the Submodules under the Bank Report module. 28. Determine the workability of the Next and Back buttons as well as the pagination. 29. Evaluate the newly added payslip employees, on-hold employees, and released employees displayed in the Not Initiated tab. 30. Examine Bank response processed employees displayed in the Processed tab. 31. Check the partial salary and not processed status of employees displayed in the Issues tab. 32. Verify the workability of the Settle button for Not processed and processed status under the Issues tab. 33. Evaluate the functionality of the Active tab. 34. Evaluate the functionality of the process steps numbers present in the bank report module. 35. Make sure the alignment and data present in the dashboard table of the salary account check home screen. 36. Confirm the Enter Narration Details popup appear after clicking on Generate Report button when admin selects an employees. 37. Make sure that by entering the Debit Narration and Credit Narration details admin can Generate Excel Report. 38. Evaluate with inaccurate Debit and Credit narration details admin can generate the bank report for employees. 39. Evaluate that the admin can upload the bank status report for the specific year and month for which the payslip has already been uploaded to the paysquare output. 40. Examine admin can upload the bank response file other than .xlsx format. 41. Make sure that a popup window with a duration dropdown to map the bank response to the correct month and year appears when the admin uploads the bank response file. 42. Confirm the popup window contains all the data in tabular format along with proper alignment of the table. 43. Evaluate the 'Submit Bank Report' button's functionality present on the popup window. 44. Confirm the upload buttons' functionality using accurate and legitimate data. 45. Make sure the 'Back' buttons working present on the 'Bank Output' screen. 46. Evaluate the 'Submit' button functioning when the admin completes all the steps for the Bank report process. "55" The use of “reminder” module is to remind to appraise employees on selected date. This module is developing to view the list of reminders added in appraisal module dashboard. The features will be edit, search, and dismiss the reminders. This module ...","1. Make sure all appraisal reminders are present in the tabular format or not. 2. Ensure that the breadcrumbs are placed on top of the page. 3. Examine the few records that will appear on one page by utilizing the 'Show Entries' feature. 4. Evaluate that admin can search the data in the search box and output will display in the tabular format. 5. Confirm that pagination is available at the page's bottom and make sure how it works. 6. Make sure that the admin may select the From and To dates to search the records. 7. Ensure whether admin can reset the selected From and To dates. 8. Make sure that the edit icon is available to edit the details for individual entries. 9. Check all fields are editable except Employee ID and Name in the Edit Reminder form, and try to edit the form. 10. Make sure that the dismiss icon is available to dismiss the reminder for individual entries. 11. Make sure that admin can add the comment for dismissing the reminder. 12. Evaluate that the admin can dismiss the reminder. 13. Ensure that the Reminder is set for a specific amount of time. 14. Confirm that the set reminder employees will appear in the 'Reminder' module. 15. Examine the Reminder date can only be set between the 'From' and 'To' dates. 16. Make sure under the template module reminder status as Upcoming, Expired and Dismiss are present. 17. Examine the admin can cancel the reminder. 18. Ensure that the reminder expires after a certain period of time. 19. Make sure that the entries are displayed in the scheduler log when the remainder date is passed. 20. Ensure all the entries have Mail sent successfully status will be displayed in the scheduler log with a blank Action column. 21. Examine Mail sent failed status entries displayed with a Resend button to resend the mail. 22. Evaluate the functionality of the Resend mail button for the mail failed employee entries. "56 In the template module admin will be able to create letter template of appraisal e-mail and appraisal letter. In this module table will display of created templates.,"1. Ensure that the correct breadcrumbs are placed on top of the 'Template' page. 2. Confirm the functioning of the entries dropdown for the selected number in the show entries. 3. Evaluate that admin can search the data in the search box and searched output displays in the tabular format. 4. Ensure that after selecting one option from the dropdown list, data will be shown in tabular format. 5. Confirm that the admin can view the previously created template. 6. Evaluate that the previously created template can be edited by the admin. 7. Examine admin can delete the created template using 'Delete' button. 8. Make sure that pagination is available at the page's bottom and check it's functioning. 9. Ensure Admin can create a new template using the 'Create Template' button. 10. Ensure all the alignments of the template page are as per the design documents. 11. Confirm that the template of the Appraisal letter or Appraisal email are appear on the Appraisal Letter screen under the Appraisal module. 12. Examine the workability of Close button on the Add Template page. 13. Make sure that all the list of the letter types clearly visible without the spelling mistakes. "57" Project Information System is a web application designed for the admin of an organization, that helps keeps track of all the project, teams, and customer-related information. It displays an overview of all the active projects and customers in the form o...","1. Examine the outcome when the Login button is clicked while the User ID and Password fields are both blank. 2. To view the outcomes, click the Login button when the User ID field is empty and the Password field is filled in. 3. When the user inputs the User ID and keeps the password field blank, check the login functionality. 4. Check the response when an invalid User ID and Password are entered and the Login button is clicked. 5. When an invalid User ID and valid Password are entered and the Login button is clicked examine the response. 6. Ensure that the user can view their profile photo, access another user's profile using the proxy option, and log out from the application by selecting the Logout option available in their name dropdown menu. 7. Ensure that the user can view the list of active customers' data after clicking the Active Customers button in the Overview section. 8. Check the response when a valid User ID and invalid Password are entered and the Login button is clicked. 9. Make sure that the users can navigate to the RNT dashboard using their valid credentials. 10. Ensure that only the admin gets access to the PINS application once successfully login into the RNT dashboard. 11. Examine that the OVERVIEW section is displaying a donut chart to determine the project's current progress. 12. Check the Attention Required section, which presents the data table that gives the list of Customers with their specific projects and their alerts on the PINS Dashboard. 13. Examine the data table under the HEALTH STATUS section showing the project and the status of scheduled variance and effort variance on the PINS dashboard. 14. Make sure that the UPCOMINGMILESTONES section shows the upcomingmilestone for that particular project with their date on the PINS dashboard. 15. Make sure that the dropdown menu with options is available provided for the Show Entries capability to display many entries on a single page. 16. Check to see if the search feature displays the right results if the user enters any text in the field. 17. Check that the search field displays the error message No matching record found if the user inputs incorrect data. 18. Make sure the View functionality shows the customer's detailed information which is not editable. 19. Examine that after clicking the Finish button, the user is directed to the List of Active Customers page. 20. Ensure that the user can navigate to the PINS dashboard using the PINS navigation functionality. 21. Make sure the user can view the list of active Projects data after clicking the Active projects button in the Overview section. 22. Examine the dropdown menu with options available provided for the Show Entries capability to display many entries on a single page. 23. Check to see if the search feature displays the right results if the user enters any text in the field. 24. Check that the search field displays the error message No matching record found if the user inputs incorrect data. 25. Make sure the View functionality shows the project's detailed information of a specific item. 26. Examine that after clicking the Finish button, the user is directed to the List of Active Projects page. 27. Make sure the user can navigate to the PINS dashboard using the PINS navigation functionality. 28. Make sure the user can navigate to the RNT dashboard using the Home navigation functionality. 29. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 30. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 31. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 32. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. "58The Customer Management Module will enable the admin to add new customer details and the project associated with the customer. The admin can edit or view already added customers. The list of customers can also be viewed in this module.,"1. Examine whether the Customer Management module includes the List of Customers page, where the customer details are displayed under the data table in their respective columns. 2. Make sure the user can navigate to the RNT dashboard using the Home navigation functionality. 3. Ensure that the user can navigate to the PINS dashboard using the PINS navigation functionality. 4. Examine the dropdown menu with options available provided for the Show Entries capability to display many entries on a single page. 5. Check to see if the search feature displays the right results if the user enters any text in the field. 6. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 7. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 8. Make sure the user navigates to the Customer Information page after clicking the Add New button so they may fill out the customer's information. 9. Examine the functionality of the Next button without filling out any of the mandatory fields on the customer information page. 10. Examine the functionality of the Next button by filling out some mandatory fields on the customer information page. 11. By filling out all mandatory fields on the customer information page, check the Next button's functionality. 12. Make sure that the Customer Information page's mandatory fields are denoted by an asterisk (*). 13. When a user fills out all mandatory fields and clicks the Next button on the Customer Information page, check that they get to the Project Details page so they may fill out the Project Details. 14. When a user arrives at the project information page, make sure they can fill out all the fields under its tab. 15. Ensure that all required fields on the Project Details page are indicated with an asterisk (*) and that all fields are properly aligned. 16. Make sure the project's end date is always greater than its start date. 17. Check the user may add the milestone for that specific project if it is required under the MILESTONES section. 18. Make sure that the milestone's date always falls between the project's Start and End dates. 19. Check the outcome if you click the Add To List button after selecting only the milestone and not a date. 20. Check the outcome if you click the Add To List button after selecting only the date of milestone and not a Milestone. 21. If the user tries to add duplicate milestones, look at the response. 22. Confirm that the user can delete the milestone if those milestones are not required once the data has been added to the list. 23. Ensure that the Previous button feature is available to get back to the previous page of Customer Information and view or update the information. 24. Examine the functionality of the Finish button without filling out any of the mandatory fields on the Project Details page. 25. Examine the functionality of the Finish button by filling out some mandatory fields on the Project Details page. 26. Make sure that once all mandatory fields have been filled the Finish button works. 27. Check the pop-up message is displayed as Submitted Successfully after clicking on the finish button. 28. Confirm by clicking on the Ok button of the pop-up message window that data is submitted successfully to the List of Customers page. 29. Ensure that the user can edit the Customer details and project details using the edit functionality which is available under the data table. 30. Make sure the View functionality shows the Project's detailed information which is not editable. 31. Examine that after clicking the Finish button, the user is directed to the List of customer page. 32. To edit the project's details, check that the Edit button is functional under the action column on the project details page. 33. Overview the Delete button is present after data is saved and if required, delete the entry in the milestone section under the project details sub-module. 34. Examine that after clicking the Finish button the data is updated and the user is directed to the List of customer page. 35. Check that the Add Project functionality on the project details page allows the user to add multiple projects for the same customer. 36. Make sure that the list of all added projects is displayed for that customer on the project information page, which includes both active and inactive projects. 37. Ensure that all UI, buttons, text, and alignment are showing properly on the customer information page. 38. Ensure that all UI, buttons, text, and alignment are showing properly on the Project Details page. 39. Ensure that users can add additional contact person details using their functionality, which is mandatory on the Customer Information page. 40. Ensure that users can edit previously or newly added addresses using the 'edit' functionality on the customer information page. 41. Ensure that users can delete previously or newly added addresses using the 'edit' functionality on the customer information page. 42. Examine that using the Next button user can move from the customer information page to the project details page. 43. Examine that the MSA Attachment is visible when the user selects 'Yes' from the radio button, and also confirm that the user can successfully upload an attachment in .xls, .xlsx, .doc, and .pdf formats for the MSA. 44. Confirm that there is a delete option accessible after the attachment has been posted, which can be used to remove the attachment from the list that has been uploaded. 45. Make sure that the documents are permanently deleted once the user removes them, and that they do not appear on the edit or view page. 46. Determine whether the user can download the uploaded MSA and NDA documents from the Customer Information Page when needed. 47. Examine that the NDA Attachment is visible when the user selects 'Yes' from the radio button, and also confirm that the user can successfully upload an attachment in .xls, .xlsx, .doc, and .pdf formats for the NDA. 48. Ensure that if the user uploads documents for the MSA and NDA, and subsequently selects the 'No' radio button for the same fields, the uploaded documents will be erased and the attachment functionality will become invisible. 49. Make sure that the project manager will only see the list of assigned projects with their respective customers in the customer management module. 50. Examine that the project manager can edit customer and project details only for the projects assigned to them. 51. Ensure that the project manager can view the project details only for the projects assigned to them. 52. The project manager can add multiple projects to the same customer by utilizing the Add New Project functionality while updating the customer information. 53. Ensure that the project manager can add new customers and projects, but they will not be visible until the admin assigns those projects to him. 54. Examine that the SOW Attachment is visible when the user selects 'Yes' from the radio button, and also confirm that the user can successfully upload an attachment in .xls, .xlsx, .doc, and .pdf formats for the SOW. 55. Determine whether the user can download the uploaded SOW documents from the Project Details Page when needed. 56. Confirm that there is a delete option accessible after the attachment has been posted, which can be used to remove the attachment from the list that has been uploaded. 57. Ensure that if the user uploads documents for the SOW, and subsequently selects the 'No' radio button for the same fields, the uploaded documents will be erased and the attachment functionality will become invisible. 58. Examine that the SOW Attachment is visible when the user selects 'Yes' from the radio button, and also confirm that the user can successfully upload an attachment in .xls, .xlsx, .doc, and .pdf formats for the SOW. 59. Determine whether the user can download the uploaded SOW documents from the Project Details Page when needed. 60. Confirm that there is a delete option accessible after the attachment has been posted, which can be used to remove the attachment from the list that has been uploaded. 61. Ensure that if the user uploads documents for the SOW, and subsequently selects the 'No' radio button for the same fields, the uploaded documents will be erased and the attachment functionality will become invisible. 62. Ensure that users can delete previously or newly added MSA or NDA attachments using the cross icon, which is visible on the uploaded document after hovering the mouse over it. additionally they can download the uploaded document as well. 63. Ensure that users can upload MSA and NDA documents using the respective Attachment functionality, which is visible after selecting the 'Yes' radio button for the corresponding fields "59" The Project Management Module will enable the admin to add software, hardware, enlist tasks, milestones, project phases and specify the people skills needed in the project. This module will also display active and inactive projects.","1. Ensure that The list of active and inactive projects is displayed based on their End dates in their respective tabs once the project is added to the Customer management module. 2. Confirm that the user can click on the Project name and make changes or add new details for that particular project. 3. Validate that the data is fetching correctly from the customer management module in the respective field on the Project Management screen. 4. Examine the functionality of the Submit button without filling out any of the mandatory fields under the SOFTWARE section. 5. Make sure that the SOFTWARE section's mandatory fields are denoted by an asterisk (*). 6. Examine the functionality of the Submit button by filling out some mandatory fields. 7. By filling out all mandatory fields under the SOFTWARE section, check the Submit button's functionality. 8. Examine that if the user added duplicate data then the error pop-up message should appear. 9. To edit the software details, check that the Edit button is functional under the action column in the SOFTWARE section. 10. Check that After the data is added, a Delete option is available, which may be used to remove an entry from a list that has been added. 11. Examine the functionality of the Submit button without filling out any of the mandatory fields under the HARDWARE section. 12. Make sure that the HARDWARE section's mandatory fields are denoted by an asterisk (*). 13. Examine the functionality of the Submit button by filling out some mandatory fields. 14. By filling out all mandatory fields under the HARDWARE section, check the Submit button's functionality. 15. Examine that if the user added duplicate data then the error pop-up message should appear. 16. To edit the software details, check that the Edit button is functional under the action column in the HARDWARE section. 17. Check that After the data is added, a Delete option is available, which may be used to remove an entry from a list that has been added. 18. Examine the functionality of the Submit button without filling out any of the mandatory fields under the TASK section. 19. Make sure that the TASK section's mandatory fields are denoted by an asterisk (*). 20. By filling out the mandatory field under the TASK section, check the Submit button's functionality. 21. Ensure that if the user added duplicate data then the error pop-up message should appear. 22. Check that After the data is added, a Delete option is available, which may be used to remove an entry from a list that has been added. 23. Examine the functionality of the Submit button without filling out any of the mandatory fields under the PEOPLE SKILL section. 24. Make sure that the PEOPLE SKILL section's mandatory fields are denoted by an asterisk (*). 25. Ensure the functionality of the Submit button by filling out some mandatory fields. 26. By filling out all mandatory fields under the PEOPLE SKILL section, check the Submit button's functionality. 27. Examine that if the user added duplicate data then the error pop-up message should appear. 28. To edit the software details, check that the Edit button is functional under the action column in the PEOPLE SKILL section. 29. Check that After the data is added, a Delete option is available, which may be used to remove an entry from a list that has been added. 30. Examine the functionality of the Submit button without selecting the milestone mate on date and Met or not radio button under the MILESTONE section. 31. Check the Milestone Met On date is not accepting the less than milestone date and is fall between Start date and End date of the project's. 32. Make sure the Met Or Not field only allows the user to select one radio button at a time. 33. Confirm that the data is saved in that table once click submit button after all required fields full fill under the MILESTONE section. 34. Examine the functionality of the Submit button without filling out any of the mandatory fields under the PROJECT PHASEsection. 35. Make sure that the PROJECT PHASE section's mandatory fields are denoted by an asterisk (*). 36. Examine the functionality of the Submit button by filling out some mandatory fields. 37. By filling out all mandatory fields under the PROJECT PHASE section, check the Submit button's functionality. 38. Make sure that the Start date and End date both fall between the Project Start and End dates and that the End date is always greater than the Start date. 39. Examine that if the user added duplicate data then the error pop-up message should appear. 40. To edit the software details, check that the Edit button is functional under the action column in the PROJECT PHASE section. 41. Make sure that during editing and updating the details, the Start date and End date both fall between the Project Start and End dates and that the End date is always greater than the Start date. 42. Check that After the data is added, a Delete option is available, which may be used to remove an entry from a list that has been added. 43. Confirm that the dropdown menu with options available is provided for the Show Entries capability to display many entries on a single page. 44. Check to see if the search feature displays the right results if the user enters any text in the field. 45. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 46. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 47. Examine that the Project Management page's corresponding section, fields, and buttons are displayed with the correct alignments, spellings, font sizes, and font families. 48. Ensure that the project manager will see the list of projects with their respective customers, only for the projects assigned to him. 49. Examine that the project manager can add software, hardware, tasks, people skills, milestones, and project phases to the assigned project. 50. Examine that the project manager can edit software, hardware, people skills, milestones, and project phases to the assigned project. 51. Examine that the project manager can delete the software, hardware, tasks, people skills, and project phases to the assigned project. "60The Team Management Module would let the admin add additional team members to a desired project. The admin will be able to view the active/ inactive projects and the team members associated with the project. Admin would be able to view and edit the asso...,"1. Check Once the team has been assigned to the particular project, the list of active and inactive Team members is displayed in accordance with their release dates on the corresponding tabs. 2. Examine the New Project dropdown list, for which no team members have yet been allocated; only those projects are displayed. 3. Check the functionality of Add Members to get to the team management page where team members can be assigned to projects. 4. Validate that the data is fetching correctly in the respective field on the Team Management screen. 5. Ensure that the ASSOCIATE TEAM section includes a data table that lists the roles, skills, count, and allocated count for the user view. 6. Check the outcome if the user presses the Go button without filling in any of the required fields. 7. Examine how the Go button works once clicked to view further fields. After the user fills out the mandatory field, 8. Make sure that the allocation date always falls between the Project Start and End dates. 9. Confirm that the Release date shows by default the project end date, but if the user wants to change that, then the Release date always falls between the Project Start and End dates. 10. Ensure the functionality of the Add to List button by filling out some mandatory fieldsunder theAssociate Team section. 11. Make sure that the Associate team section's mandatory fields are denoted by an asterisk (*). 12. Once the mandatory fields are filled out, confirm that the details for the assigned team members may be added to the list using the Add to List button. 13. Examine that once the release date is less than the current date then the team allocation details will move into the Inactive tab. 14. Ensure that the user must save the team allocation data once they have been added to the list. 15. To edit the team allocation details, check that the Edit button is functional under the action column on the Team Management page. 16. Check that After the data is saved, a Delete option is available, which may be used to remove an entry from a list that has been added. 17. Examine the dropdown menu with options available provided for the Show Entries functionality to display many entries on a single page. 18. Check to see if the search feature displays the right results if the user enters any text in the field. 19. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 20. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 21. Confirm that the user can click on the Team Member name and make changes or add a new team member for the same project. 22. Ensure that the fields, data table, and buttons in the ASSOCIATE TEAM section are properly aligned within the correct format. 23. Ensure that the project manager can assign the team to the project for their assigned project. "61 The Change Request module will help the admin to accommodate any new changes to the projects. Admin will be able to edit or view a change request. All the change-related details are encapsulated within this module.,"1. Examine that the list of all customers is correctly shown once the user has reached the Add Change Request page and clicked the Customer Name dropdown. 2. Ensure that the project list won't appear unless the user chooses the customer from the customer name dropdown first. 3. Check that when a user selects a customer, the project name dropdown list only shows the projects that have been added to this customer. 4. Confirm that the Go Live Date must always be greater than the Raise Date and that the user cannot select a Go Live Date that is less than the Raise Date. 5. Assure that the user cannot select an Approved Date (Business Team) less than the Raised Date it should always be greater. 6. Ensure that the user cannot select an Approved Date (Project Team) less than the Raised Date it should always be greater. 7. Make sure the CR details section contains more fields that are required to add the new change request. 8. Check the effort section contains fields that are required to add the new change request to calculate the ETA. 9. Make sure the Unit field only allows the user to select one radio button at a time from the Hours and Days. 10. Examine that to add the new phases, the Add Phases functionality only allows the user a maximum of 3 more phases if necessary to add. 11. Check once the efforts have been added to the list, the user will no longer be able to add new phases, and the Add Phases functionality will become hidden from the effort section. 12. Examine that If the user adds additional phases to add the data, they can only delete those phases to which they have added new phases utilizing the Add Phase functionality. 13. Once a user clicks the Add to List button, ensure that the data has been added appropriately to the respective column. 14. Check that After the data is added, a delete option is available, which may be used to remove an entry from a list that has been added. 15. Examine that when a user adds or removes an entry from the list, the serial number is updated correctly. 16. If the user clicks the include deployment time check box without entering any value in the fields check the data is added to the table with Zero value. 17. Once the user enters the efforts and selects the include deployment time check box functionality, confirm that the data has been added to the effort data table 18. Check that the user can successfully upload an attachment in the .xls, .xlsx, .doc, and .pdf formats only for the Change request. 19. Confirm that there is a delete option accessible after the attachment has been posted, which can be used to remove the attachment from the list that has been uploaded. 20. Examine that for every field the alignment, font size, and font family are displayed on the Add Change request page page of the Change Request in the proper format. 21. Make sure that the entered data is not saved for that customer in the data table once the user clicks the cancel button. 22. Examine the functionality of the Submit button without filling out any of the mandatory fields on the Add Change Request page. 23. To edit the Change Request details, check that the Edit button is functional under the action column on the Change Request details page. 24. Check that the Add Phases functionality on the Edit page of the Change request only enables the user to add a maximum of 3 further phases if they haven't already been added. 25. Make sure the user can add new phases after adding efforts to the list and that the Add Phase button won't be hidden if the user adds efforts to the list. 26. Examine that If the user adds additional phases to add the data on the edit page of change request, they can only delete those phases to which they have added new phases utilizing the Add Phase functionality. 27. To edit the Effort from the efforts table, check that the edit icon is functional under the action column under the effort section. 28. Check that After the Efforts are added to the efforts table, a delete option is available, which may be used to remove an entry from a list that has been added. 29. Examine that when a user adds or removes an entry from the efforts table, the serial number is updated correctly on the Edit page of Change Request. 30. Make sure the View functionality shows the Change request detailed information once click the View icon in the action column. 31. Examine that once the user reaches the view page all fields are non-editable on the View Change Request page. 32. Confirm that the Units are displaying correctly in the data table for the Efforts section. 33. Determine whether the user can download the uploaded document from the View CR Page if necessary. 34. Examine that for every field the alignment, font size, and font family are displayed on the View CR page of the Change Request in the proper format. 35. Ensure that the user navigates to the Change Request home screen once they click the Back button on the View CR page. 36. Make sure that to preview the CR details the user navigates to the Preview page once they click the Preview button on the View CR page. 37. Confirm that once the user reaches the Preview page all fields are non-editable on the Preview CR page. 38. Make sure that the user navigates to the Change Request home screen once they click the Back button on the Preview CR page. 39. Examine that the document of CR details downloads in the .doc format only, once the user clicks the Download button on the Preview CR page. 40. Confirm that the dropdown menu with options available is provided for the Show Entries capability to display many entries on a single page 41. Check to see if the search feature displays the right results if the user enters any text in the field. 42. Examine the Customer name, which is clickable in the data table to reveal the list of projects for the Change requests added for that customer. 43. Look at the Project name in the data table, which may be clicked to display the list of change requests that have been raised for that project. 44. Make sure that the documents are permanently deleted once the user removes them, and that they do not appear on the edit or view page. 45. Make sure that the Add Change Request page's mandatory fields are denoted by an asterisk (*). 46. Examine the functionality of the Submit button by filling out some mandatory fields on the Add Change Request page. 47. By filling out all mandatory fields on the Add Change Request page, check the Submit button's functionality. 48. Make sure that the edited data is not updated for that customer in the data table once the user clicks the cancel button on the edit page. 49. Make sure that the Edit Change Request page's mandatory fields are denoted by an asterisk (*). 50. Examine the functionality of the Update button by getting blank some mandatory fields on the Edit Change Request page. 51. By updating all mandatory fields on the Edit Change Request page, check the Update button's functionality. 52. Determine whether the user can download the uploaded CR documents from the Change Request Page when needed. 53. Determine whether the user can download the uploaded document from the Edit Change Request Page if necessary. 54. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 55. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 56. Make sure the change request module has a change request page where the customer receives the details of the change request for their associated project. 57. Ensure that using the Change Request navigation functionality the user can navigate to the Change Request page where the list of change request data is listed. 58. Ensure that the OVERVIEW section displays a donut chart to view the number of change requests (CRs) with in percentage for their respective customers. 59. Examine whether the Hide Overview button is available to conceal the displayed overview, and if the admin wishes to view it again, check for the presence of the Show Overview functionality. 60. To easily determine the overall count of change requests (CRs), Ensure that the total CR count is accurately displayed on the Total CR button. 61. Ensure that the Active CR button shows an accurate count of active change requests (CRs) and, upon being clicked, displays a list of those active CRs. 62. Examine that the Inactive CR button shows an accurate count of inactive change requests (CRs) and, once clicked, displays a list of those inactive CRs. 63. Ensure that the administrator has the option to download the total, Active, and Inactive change requests on the Change Request screen into an Excel file. 64. Ensure that all UI, buttons, text, and alignment are showing properly on the Change Request page. 65. Examine that for every field the alignment, font size, and font family are displayed on the Edit Change Request Page of the Change Request in the proper format. 66. Make sure that the Project Manager can review change requests (CRs) for the respective customer. They have the ability to view the total number of CRs as well as the count of active and inactive ones. Additionally, they can download the CRs in Excel for... 67. Examine the Project Manager can raise the change request to the assigned project. 68. Ensure that the Project Manager is able to edit and view the added CR using the respective 'Edit' and 'View' functionalities. 69. Make sure that the Business Analyst/Business Analyst-intern can review change requests (CRs) for the respective customer. They have the ability to view the total number of CRs as well as the count of active and inactive ones. Additionally, they can down... 70. Examine the Business Analyst/Business Analyst-intern can raise the change request to the assigned project. 71. Ensure that the Business Analyst/Business Analyst-intern can edit and view the added CR using the respective 'Edit' and 'View' functionalities. 72. Make sure that the CR Admin can review change requests (CRs) for the respective customer. They can view the total number of CRs as well as the count of active and inactive ones. Additionally, they can download the CRs in Excel format. 73. Examine that the CR Admin can raise the change request to all projects. 74. Ensure that the CR Admin can edit and view the total added CR using the respective 'Edit' and 'View' functionalities. "62"Admin can add new software-related information to the system that can be utilized by the projects in the organization. If the software version changes, the user can modify the details of the software and can also delete added software if it is no longer...","1. Ensure the presence of the Admin module within the Project Information System modules. 2. Examine that the Admins sub-module contains the Software sub-module. 3. Make sure the user navigates to the Software Details page after clicking the Add New button so they may fill out the software detailed information. 4. Make sure that the Software Details page's mandatory fields are denoted by an asterisk (*). 5. Make sure that the entered data is not saved for that software in the data table once the user clicks the Cancel button. 6. Examine the functionality of the Submit button without filling out any of the mandatory fields on the Software Details page. 7. Examine the functionality of the Submit button by filling out some mandatory fields on the Software Details page. 8. By filling out all mandatory fields on the Software Details page, check the Submit button's functionality. 9. Check that all fields accept a space at the beginning and more than one after a letter or word. 10. Examine the dropdown menu with options available provided for the Show Entries capability to display many entries on a single page. 11. Check to see if the search feature displays the right results if the user enters any text in the field 12. Validate the data table on the List of Software page of the Software sub-module. 13. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 14. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 15. To update the Software details, check that the Edit icon is functional under the action column on the List of Software page 16. Make sure that the edited data is not updated for that software in the data table once the user clicks the Cancel button. 17. Check that the edited data is updated in the data table for that particular software once user click the Update button. 18. Examine that the delete icon is functional under the Action column, and the entries are removed from the list once the user clicks the delete icon. 19. Examine that if the user added duplicate data then the error pop-up message should appear. 20. Ensure that if the user selects the software type as commercial, more options will become visible to fill out the software details. "63" Admin can add new hardware-related information to the system that can be utilized by the projects in the organization. Admin can add a new role, can view the list of added hardware, modify changes, and can delete added hardware.","1. Check the Admin sub-module contains the Hardware sub-module. 2. Make sure the user navigates to the Hardware Details page after clicking the Add New button so they may fill out the hardware detailed information. 3. Make sure that the Hardware Details page's mandatory fields are denoted by an asterisk (*). 4. Make sure that the entered data is not saved for that hardware in the data table once the user clicks the Cancel button. 5. Examine the functionality of the Submit button without filling out any of the mandatory fields on the Hardware Details page. 6. Examine the functionality of the Submit button by filling out some mandatory fields on the Hardware Details page. 7. By filling out all mandatory fields on the Hardware Details page, check the Submit button's functionality. 8. Check that all fields accept a space at the beginning and more than one after a letter or word. 9. Examine that if the user added duplicate data then the error pop-up message should appear. 10. Examine the dropdown menu with options available provided for the Show Entries capability to display many entries on a single page. 11. Check to see if the search feature displays the right results if the user enters any text in the field. 12. Validate the data table on the List of Hardware page of the Hardware sub-module. 13. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 14. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 15. To update the Hardware details, check that the Edit icon is functional under the Action column on the List of Hardware page. 16. Make sure that the edited data is not updated for that hardware in the data table once the user clicks the Cancel button. 17. Check that the is edited data is updated in the data table for that particular hardware once user click the Update button. 18. Examine that the delete icon is functional under the Action column, and the entries are removed from the list once the user clicks the delete icon. "64" Role rate card provides information on the role of an employee and its associated budget as per the location of the employee in the current organization. Admin can add a new role, view the list of added roles, modify changes, and can delete added roles.","1. Make sure that the Admin sub-module contains the Role Rate Card sub-module. 2. Make sure the admin may add various location-specific rate cards that are developed based on the Onsite and Offsite hours and days for the employee. 3. Make sure that theRole Rate-Card Managementpage's mandatory fields are denoted by an asterisk (*). 4. Examine the functionality of the Add button without filling out any of the mandatory fields on the Role Rate-Card Managementpage. 5. Examine the functionality of theAddbutton by filling out some mandatory fields on theRole Rate-Card Managementpage. 6. By filling out all mandatory fields on the Role Rate-Card Managementpage, check the Addbutton's functionality. 7. Check that all text fields accept a space at the beginning and more than one after a letter or word. 8. Examine that if the user added duplicate data then the error pop-up message should appear. 9. Examine the dropdown menu with options available provided for the Show Entries capability to display many entries on a single page. 10. Check to see if the search feature displays the right results if the user enters any text in the field. 11. Validate the data table on the Role Rate-Card Management page under the LOCATION WISE RATE CARD section. 12. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 13. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 14. To update the Role Rate Card details, check that the Edit icon is functional under the Action column on theRole Rate-Card Managementpage. 15. Check that the edited data is updated in the data table for that particular Rate card once user click the Update button. 16. Examine that the delete icon is functional under the Action column, and the entries are removed from the list once the user clicks the delete icon. "65" Project phases are phases included in a project life cycle. Admin has the authority to add a new phase, view the list of added phases, modify changes to any phase, and can delete phases.","1. Check that the Admins sub-module contains the Project Phases sub-module. 2. Make sure that theProject-Phase Managementpage's mandatory field is denoted by an asterisk (*). 3. Examine the functionality of the Add button without filling out the mandatory field on theProject-PhaseManagementpage. 4. By filling out a mandatory field on theProject-PhaseManagementpage, check the Addbutton's functionality 5. Examine that if the user added duplicate data then the error pop-up message should appear. 6. Examine the dropdown menu with options available provided for the Show Entries capability to display many entries on a single page. 7. Check to see if the search feature displays the right results if the user enters any text in the field. 8. Validate the data table on theProject-PhaseManagement page under theList of Project-Phasessection. 9. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 10. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 11. To update the Project Phase details, check that the Edit icon is functional under the Action column of the List of Project-Phases Managementsection. 12. Check that the is edited data is updated in the data table for that particular Project phase once user click the Update button. 13. Examine that the delete icon is functional under the Action column, and the entries are removed from the list once the user clicks the delete icon. 14. Check that the List of Project-Phases section is present on the Project-Phases Management screen. "66Milestones mark the important project phases. Admin can modify or delete any milestones or add a new milestone with the help of the Milestones module.,"1. Check that the Admin sub-module contains the Milestones sub-module. 2. Check that the Milestone Management page is present in the Milestones sub-module. 3. Check the Home button functionality on the Milestone Management screen. 4. Verify the PINS button functionality on the Milestone Management screen. 5. For mandatory fields, validate the Asterisk(*) symbol. 6. To enter data in the Milestone Name text field, verify it. 7. Check the Add button functionality to add the data to the list. 8. Validate the List of Milestones section is present on the Milestone Management screen. 9. To view the entries, use the Show entries dropdown menu. 10. Check the Search text area to search the data in the list. 11. Validate the data table on the Milestone Management page. 12. Check the functionality of the next button on the Milestone Management page. 13. Check the functionality of the Previous button on the Milestone Management page. 14. Check the Edit button functionality. 15. Check that the Update button functionality updates the data in the list once the data is Edited. 16. Check the Delete functionality. 17. Check the Delete functionality. "67Service types are any services that the organization provides to its customers. Admin can add a new service type that the organization offers with the help of the Service types module. Admin can also modify or delete the added Service types.,"1. Check that the Admins sub-module contains the Service Types sub-module. 2. Check that the Service-Types Master page is available in the Service Types sub-module. 3. Check the Home button functionality on the Service-Types Master page. 4. On the Service-Types Master page, check the PINS button functionality. 5. To enter data into the Service Type text field, verify it. 6. Check the Mandatory fields for the Asterisk(*) symbol. 7. Check the Add button functionality to add the data to the list. 8. Check that the List of Service-Types section is present on the Service-Types Master page. 9. To view the entries, check the Show entries dropdown functionality. 10. To search the data in the list, enter Search in the text area. 11. Validate the data table on the Service-Types Master page. 12. On the Service-Types Master page, check the Next button functionality. 13. On the Service-Types Master page, check the functionality of the Previous button. 14. Check the Edit function. 15. Check that the Update button functionality updates the data in the list once the data is Edited. 16. Check the Delete functionality. 17. Check the Delete functionality. "68" Various roles of an employee can be added by using the Roles module. Admin can add a new role, view the list of added roles, modify changes to any role, and can delete roles that are no longer needed.","1. Check that the Admin sub-module contains the Role module. 2. Check that the Role master page is available in the Roles module. 3. Check the Home button functionality on the Roles page. 4. On the Roles Master page, check the PINS button functionality. 5. To input data in the Role Name text area, verify the field. 6. For mandatory fields, validate the Asterisk(*) symbol. 7. To add the data to the list, test the Add button functionality. 8. Validate the List of Roles section is present on the Roles Master page. 9. To view the entries, use the Show entries dropdown menu. 10. To search the data in the list, use the Search text field. 11. Validate the data table on the Roles Master page. 12. On the Roles Master page, check the functionality of the Next button. 13. Check the functionality of the Previous button on the Roles Master page. 14. Check the Edit feature using the icon. 15. Check that the Update button functionality updates the data in the list once the data is Edited. 16. Check the Delete functionality. 17. Verify the Delete functionality. "69" Skills are organizational assets; They can be tools and technologies per organization. Admin can add any new skills, update the existing skills as well as delete the skills that are no longer needed.","1. Check that the Admins sub-module contains the Skills sub-module. 2. Check to see if the Skills page is available in the Skills sub-module. 3. Check the Home button functionality on the Skills Master page. 4. Check the PINS button functionality on the Skills Master page. 5. For mandatory fields, validate the Asterisk(*) symbol. 6. To add the data to the list, test the Add button functionality. 7. To enter data in the Skill Name text area, verify it. 8. Validate the List of Skill section is present on the Skills page. 9. To view the entries, use the Show entries dropdown menu. 10. To search the data in the list, use the Search text field. 11. Validate the data table on the Skills page. 12. On the Roles Master page, check the functionality of the Next button. 13. Check the functionality of the Previous button on the Roles Master page. 14. Check the Edit feature using the icon. 15. Check that the Update button functionality updates the data in the list once the data is Edited. 16. Check the Delete functionality. 17. Check the Delete functionality. "70" The locations module consists of the locations that the organization is situated in. If the organization plans to expand its offices, the admin can add them using the Locations module. Admins can modify or delete the locations from the added list.","1. Check that the Admins sub-module contains the Location sub-module. 2. Check that the Location Master page is available in the Locations sub-module. 3. Check the Home button functionality on the Location Master screen. 4. Check the PINS button functionality on the Location Master screen. 5. For mandatory fields, validate the Asterisk(*) symbol. 6. To enter data in the Skill Name text area, verify it. 7. To add the data to the list, test the Add button functionality. 8. To add the data to the list, test the Add button functionality. 9. Validate the List of Locations section is present on the Location Master screen. 10. To view the entries, use the Show entries dropdown menu. 11. To search the data in the list, use the Search text field. 12. Validate the data table on the Location page. 13. On the Location page, check the functionality of the Next button. 14. Check the functionality of the Previous button on the Location page. 15. Check the Edit feature using the icon. 16. Check that the Update button functionality updates the data in the list once the data is Edited. 17. Check the Delete functionality. 18. Check the Delete functionality. "71Track of Achievement accomplished by the individual employee regarding ongoing and completed courses must be displayed in the achievement module for Admin.,"1. Check the functionality of search field if user enters data to search. 2. Check if user click on breadcrumb then user must be navigate on respective page. 3. Make sure that on clicking full details button user must be navigate to employee profile page. 4. In order to keep track on employee achievements, check the count appear in overview card. 5. Validate the details like employee ID and role appear on details page is same as on achievement main page. 6. Make sure that user is able to see all the details related to batch appear on mouse hover on batch card with progress status appear on progress bar of batch card. 7. Check the functionality that without mouse hover admin is able to see the actual start date and end date of training by employee. 8. Analyze that on mouse hover on batch card, admin is able to see start date and end date entered by admin while creating batch. 9. Examine that on mouse hover user is able to see assignment and certificate uploaded by employee while submitting progress. 10. Check that while submitting feedback, comments added by employee are appear on mouse hover on batch card. 11. Make sure that year dropdown is functional to see the data year wise. 12. Examine the functionality of search field on entering data in it. "72List of feedbacks and average rating provided by participants of respective course and batches must be accessible for admin.,"1. Check the name of the training appear properly with star rating for that particular training 2. Examine the functionality of breadcrumb, on clicking that user must be navigate to that particular page/module. 3. Analyze the functionality of colors appear for different star ratings. 4. Analyze the functionality of batches feedback module by clicking on view batch option. 5. Make sure that on clicking back button user must be navigate to previous page. 6. Check that all the details related to batch appear with the star rating for that particular batch. 7. Check the functionality of breadcrumb appear on batches feedback page. 8. Make sure that on clicking participant's feedback option user navigate to participants feedback page. 9. Check whether the details of selected batch appear on that page with an average star rating. 10. Check that admin is able to see rating given by employee on feedback form with date. 11. Check the functionality of search field. 12. Make sure that on clicking breadcrumb user is navigate to respective page. 13. To navigate back to previous page check the functionality of back button. "73 The report module will generate a report called the Project Completion Report. Admin should be able to view all the completed project details and the employees allocated to the project.,1. Ensure the presence of the Reports module within the Project Information System modules. 2. Examine that the Reports sub-module contains the Project Completion Report sub-module. 3. Check that the Team Available page is visible in the Project Completion Report sub-module. 4. Examine the dropdown menu with options available provided for the Show Entries capability to display many entries on a single page. 5. Check to see if the search feature displays the right results if the user enters any text in the field. 6. Validate the data table on the Team Available page. 7. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 8. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 74The report module will generate a report called Employee Allocation Report. Admin should be able to view the list of employees allocated and working on projects.,1. Examine that the Reports sub-module contains the Employee Allocation Report sub-module. 2. Check that the Project Available page is visible in the Project Completion Report sub-module. 3. Examine the dropdown menu with options available provided for the Show Entries capability to display many entries on a single page. 4. Check to see if the search feature displays the right results if the user enters any text in the field. 5. Validate the data table on the Project Available page. 6. Check that the Project Name can be clicked to take you to the Team Management page. 7. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 8. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 75"In this section user which has CO,HOD, FREE, and FDM can set the policy means set the appointment cost and also the cancellation fee. and as well as in this user can set the cancellation fee distributions using the last minutes thrashhold.","1. APPOINTMENT & ADVANCED PAYMENT- In the Set Policy module, in the Appointment Cost tab, user selects the desired clinic from the Select Clinic dropdown, User selects their desired clinic, the employees in the clinic would be displayed along with th... 2. In the Set Policy module, in the Appointment Cost tab, user selects the desired clinic from the Select Clinic dropdown, , the employees in the clinic would be displayed along with the Appointment Cost and Advance Payment fields,that the user d... 3. In the Set Policy module, in the Appointment Cost tab, User does NOT select their desired clinic from the Select Clinic dropdown, the employees in the clinic would be displayed along with the Appointment Cost and Advance Payment fields,that th... 4. In the Set Policy module, in the Appointment Cost tab, the user enters a value in the Appointment Cost field, and enters 0 in Advance Payment field, user then clicks on Save button which triggers a pop up asking the user to Please enter Advanc... 5. In the Set Policy module, in the Appointment Cost tab, the user enters a value in the Appointment Cost field, and does NOT enter any value in Advance Payment field, user then clicks on Save button which triggers a pop up asking the user to Ple... 6. In the Set Policy module, in the Appointment Cost tab, the user enters a value in the Advance Payment field, and enters 0 in Appointment Cost field, user then clicks on Save button which triggers a pop up asking the user to Please enter Appoin... 7. In the Set Policy module, in the Appointment Cost tab, the user enters a value in the Advance Payment field, and does NOT enter any value in Appointment Cost field, user then clicks on Save button which triggers a pop up asking the user to Plea... 8. In the Set Policy module, in the Appointment Cost tab, the user does NOT enter a value in either the Advance Payment field or the Appointment Cost field, user then clicks on Save button which triggers a pop up asking the user to Please enter Ap... 9. CANCELLATION POLICY: The user has to update Last Minute Threshold (x)dropdown and the Cancellation Fee % (y) dropdown from a list of choices from each dropdown e.g. If the user clicks on 5 in the Last Minute Threshold (x) and 60 in the Cancellati... 10. The user clicks the Last Minute Threshold (x)dropdown and makes a selection but skips the Cancellation Fee % (y)dropdown and clicks the save button. 11. The user clicks the Cancellation Fee % (y)dropdown and makes a selection but skips the Last Minute Threshold (x)dropdown and clicks the save button. 12. User add one more employee and does not set Appointment cost for the employee and directly hit Save button 13. In addition to having proper user interface (UI), the user should be able to access the cart including the cancellation and refund policy and its desired paragraph or text. "76Package Builder:- This module is used for to create the packages which then physio or any employee can sold to the Patient.,"1. On clicking the Package Builder module, the user does not click the checkbox stating Don't show me the on-boarding flow again., the on-boarding screens with the details keep showing everytime the user clicks on Next button unless the checkbox i... 2. On clicking the Package Builder module, the user clicks the checkbox stating Don't show me the on-boarding flow again., the onboarding screens would never show up and the page redirects the user to the Create Appointment Packages screen. 3. On the Package Builder, on selecting View Physiotherapist's Package dropdown, if the packages are present for the selected physio, a package details preview card would be displayed. 4. On the Package Builder, on selecting View Physiotherapist's Package dropdown, if the packages are not present for the selected physio, a message would be displayed Oops! There is no package for this doctor 5. Case 1: WITH SET POLICY: On clicking +CREATE A PACKAGE, Assuming in the Set Policy module, the payment policy of the physiotherapist is already set. On selecting the desired physiotherapist from the Select Physiotherapist dropdown, the appointment... 6. Case 2: WITHOUT SET POLICY: On clicking +CREATE A PACKAGE, Assuming in the Set Policy module, the payment policy of the physiotherapist is not set. While selecting the Physiotherapist in the Package Builder Module page, it will show a pop-up Ple... 7. While creating the package builder, the desired physio is to be selected from the Select Physiotherapist dropdown, keeping in mind Case 1 and 2. 8. User enters the package name in Package Name field. 9. User enters the invalid package name in Package Name field. 10. User clicks on Package Name field and leaves the field blank 11. User clicks on Package Name field and leaves the field blank 12. In the Number of Session, maximum number of sessions that can be entered will be 99.The user tries to enters no. of sessions greater than 99. 13. The user doesn't enter any value in the Number of Session field.User hits Generate preview, pop-up is displayed Number of Session is required. 14. Cost Per Session field would only accommodate an amount less than 10000 i.e. 9999 to be exact.The user enters a value between 1-9999. 15. Cost Per Session field would only accommodate an amount less than 10000 i.e. 9999 to be exact.The user tries to enters a value greater than 9999. 16. The user doesn't enter any value in the Cost Per Session field. User hits Generate preview, pop-up is displayed Cost Per Session is required 17. Package Cancellation Fee field cannot exceed the amount 9999.The user enters a value between 1-9999. 18. Package Cancellation Fee field cannot exceed the amount 9999.The user attempts to enter a value between greater than 9999. 19. The user doesn't enter any value in the Package Cancellation Fee field. User hits Generate preview, pop-up is displayed Cancellation Fee is required 20. The user attempts to enter the Package cancellation fees lesser than Total package cost. 21. The user attempts to enter the Package cancellation fees greater than Total package cost. User hits Generate preview, pop-up is displayed The cancellation fee exceeds the total package cost. Please set a lower cancellation fee 22. User enters the cost per session amount greater than the appointment cost. User hits Generate preview, pop-up is displayed Cost per session should be less than appointment cost 23. Appointment cost for physio is set but leave Cost per session field empty and hot GENERATE PREVIEW button 24. Appointment cost for physio is set but leave Number of sessions field empty and hot GENERATE PREVIEW button 25. The user should be able to access the cart including the package policy , desired pop-up messages and UI should be appropriate "77 LRA confirms that the claim is ready for reimbursement. The LRA confirms that the claim threshold equals the policy-set retention level.,"1. Make sure the UI of the 'Audit' module same as its XD design. 2. Validate the status of the displayed claims in the 'Pending Confirmation' tab. 3. Check user can edit the threshold level when Pro Rata exposure is present. 4. Check user can edit the threshold level when Pro Rata exposure is absent. 5. Make sure the claims have a total amount paid by Hanover that is less than the retention level and the threshold level, then the claim should remain on the watch list. 6. Check claim when its threshold amount is changed, and the total amount paid by Hanover is greater than the retention level and less than the threshold level. 7. Check when claims threshold amount is changed and the total amount paid by Hanover is greater than the retention level as well as greater than the threshold level. "78A Reimbursement needs to be submitted in a format which is designed by the MCCA Team. The biller should be able to see the bill and line level details of the submission.,"1. Check the platform combines HCS bill data (in CLMAAPR) and Medata + PPO data and make sure the platform updates the RFR form with all these bill details (at the bill and line level). 2. Make sure the total amount requested for reimbursement does not exceed the total bill amount. 3. Check whether the platform flags potential errors through the business rules configured. 4. Ensure the platform flags any areas where the field types do not match the expected output. 5. Check If the total repriced amount + total bill review fee + total PPO fee > total bill amount, Then the total amount requested for reimbursement should be set to the total bill amount. 6. Check the accessibility of the 'All RFR' button. 7. Check the accessibility of the 'Update' button. 8. Verify the Claim number on the RFR view screen. 9. Make sure all bills have a unique EOB ID. 10. Make sure all bills have unique pau log ID. 11. Make sure all bills have unique check number. 12. Check the RFR start date and end date for multiple RFRs. 13. Make sure the RFR start date cannot be a future date. 14. Check the working functionality of the open list module. 15. Check the working functionality of the RFR submission for the current month screen. 16. Check the working functionality of the RFR submission for the next month's screen. "79The HMIRAR will load the new BCNs from MCCA_LOSS_TXN to database. The BCN is a key data point in the process of Medata bill load. When an EDW check does not have an BCN the system skips its corresponding bill from Medata. Populating these new BCNs will ...,1. Validate user can access the admin module. 80RFR’s submitted with incorrect Bill Type (MISC bill type submitted while it should have been UB04/1500) which pass initial RFR submission and uploaded to MMS (MCCA Membership System) will be denied at bill level by the MCCA examiner and appear on the ...,"1. The denial reason, loss adjustment amount, and expense adjust amount must be loaded from the MCCA Webservice. "81"The billers update the carrier claimant numbers of claimants from claimant details. Currently, the system allows the billers to update the carrier claimant number of a single claimant at a time. On many claims, billers have to update the carrier claiman...","1. Check the UI of the reconciliation and its sub-modules. 2. Check user can access the Reconciliation module and its sub modules. 3. Make sure the denials and partial denials from MCCA will be populated for the biller review under the All Variance, 30 days variance, 30 to 60 days variance and more than 60 days variance. 4. Verify the presence of 'Accept Variance, Resubmit, Add Bill and Save' buttons and its accessibility in the All-variance module. "82Facilitate the Reconciliation capabilities on the HMIRAR using which the denials can be accepted or resubmitted.,"1. Validate the billers can edit the Pay Codes, Service start date and Service End dates for the bills need to be resubmitted to MCCA. 2. Make sure the service start date of a bill should always be date prior to the service end date. 3. Validate the billers can accept the +ve 4. variance from MCCA on the denied recovery requests. 5. Check accept variance functionality when the user accepts the variance of any denied bill by without entering an internal comment. 6. Validate users can resubmit a denied bill without entering the MCCA comment. 7. Check user can perform both Resubmission and Accept Variance actions at a time. "83The admin login and access control functionality allows authorized administrators to log in successfully using valid credentials and gain access to the facilities and services provided by the RNT organization.,1. Verifies whether a user can successfully access the Main Dashboard by using valid credentials and clicking the Login button. 2. Check that the system displays an appropriate error message and prevents access to the Main Dashboard when invalid data is provided. 3. Examine the behavior of the login functionality when a user enters a valid username but an invalid password 4. Validating the behavior of the login functionality when the user provides invalid data in both the username and password fields. 5. Ensure the behavior of the system when a mandatory field is left empty during the login process 84"The Access Management System Container module within the corporate apps allows the admin to add modules to existing applications in RNT, create user roles, assign roles to users, and set validity periods for user roles.","1. Examine by clicking on Access Management System text link from RNT Lounge screen, admin can see the dashboard of AMS 2. Perform necessary checks or validations to ensure that the user does not have access to the Access Management System module. "85The Dashboard module provides the admin with an overall overview of the entire application within the corporate apps. It presents key metrics and information to help the admin monitor and understand the application's performance and status.,"1. Test the proper display of cards, tabs, and lists on the dashboard screen and ensure that these UI elements are presented correctly with the appropriate styling, layout, and content 2. Examine the highlighting functionality of user roles whose validity is expiring within one month and ensures that when a user's role validity is approaching expiration, the corresponding date is highlighted in orange color on the dashboard screen. 3. Verify which user role validity will expire in 7 days i.e. less than or equal to 7 then that user role's validity to date will highlighted in Red color 4. Make sure the visibility and accuracy of the Active list of allocated user roles when the user selects the Dashboard option 5. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 6. Check the functionality of the download button to ensure that user can download the Excel file. 7. Ensure the user navigates to the respective page by hitting on the pagination buttons 8. Examine the highlighting functionality of user roles whose validity is expiring within one month and ensures that when a user's role validity is approaching expiration, the corresponding date is highlighted in orange color on the dashboard screen. 9. Verify which user role validity will expire in 7 days i.e. less than or equal to 7 then that user role's validity to date will highlighted in Red color 10. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 11. Evaluating the functionality of the Search textbox by entering invalid data 12. Check the functionality of the download button to ensure that the user can download the Excel file. 13. Verify that only active user roles are visible in the downloaded Excel file. "86"The system should provide the Admin with the ability to view a list of roles, usernames, and their validity in the Active tab. This functionality enables the Admin to monitor and manage the user accounts and their associated roles effectively.","1. Test the functionality of Active tab, by pressing on it admin user can see the list of active user roles only 2. Examine which user roles validity will expire in one month that date will get highlighted in orange color 3. Verify the highlighting functionality of user roles whose validity is expiring within 7 days or less that corresponding validity date is highlighted in red color 4. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 5. By inputting invalid data into the Search textbox, check the operating purpose of Error message 6. Check the functionality of the download button by ensuring that the list data can be downloaded in Excel format. 7. Examine which user roles validity will expire in one month that date will get highlighted in orange color 8. Verify the highlighting functionality of user roles whose validity is expiring within 7 days or less, then the corresponding validity date is highlighted in red color 9. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 10. Evaluating the functionality of the Search textbox by entering invalid data 11. Check the functionality of the download button by ensuring that the list data can be downloaded in Excel format. 12. Verify that only active user roles are visible in the downloaded Excel file. "87The system should provide the Admin with the ability to view a list of accesses that have expired in the Inactive Tab. This functionality allows the Admin to keep track of expired accesses and manage them accordingly.,"1. Test the functionality of Inactive tab, by pressing on it admin user can see the list of inactive user roles only 2. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 3. By inputting invalid data into the Search textbox, check the operating purpose of Error message 4. Check the functionality of the download button by ensuring that the list data can be downloaded in Excel format. 5. By clicking on the Edit icon make sure that admin can edit and set the validity of a particular user role 6. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 7. By inputting invalid data into the Search textbox, check the operating purpose of the Error message. 8. Check the functionality of the download button by ensuring that the list data can be downloaded in Excel format. 9. Verify that only inactive user roles are visible in the downloaded Excel file. "88" The system should provide the Admin with the ability to view a list of assigned user roles along with their validity, and offer the functionality to update user roles as needed. This feature enables the Admin to manage user roles effectively and ensure ...",1. Verifying the functionality of editing and setting the validity of a particular user role by clicking on the Edit icon 2. Validating the functionality of the Update button from edit pop up when selected Validity to date is less than the Validity from date 89" The system should display an overall count of roles available within the system to the Admin. This count gives a quick overview of the number of roles defined. Additionally, when the Admin clicks on the count, a detailed list of all the roles should be ...","1. Examine that the system correctly counts and displays the total number of roles within the specified container, providing an accurate representation of the roles available. 2. Check the functionality of opening the list of roles with Role-Based Access Control (RBAC) by clicking on the Total Roles card 3. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 4. Click and check the functionality of breadcrumbs present on the page 5. Evaluating the functionality of updating the Role-Based Access Control (RBAC) for a particular role and module by clicking on the Edit icon 6. Test the functionality of creating a new role and assigning Role-Based Access Control (RBAC) to an existing role for a specific module 7. Make sure the functionality of creating a new role and assigning Role-Based Access Control (RBAC) to an existing role for a specific module. 8. Check the functionality of the Add button when an existing role name is entered 9. Examine the functionality of the Back button and ensuring that the admin can navigate to the previous page by clicking on it. 10. Verify the functionality of the Save button when the Role Name and Application fields are not selected or left empty. 11. Examine by clicking on Up and Down button the admin user can navigate to the next or previous application 12. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 13. By inputting invalid data into the Search textbox, check the operating purpose of Error message 14. Evaluating the functionality of updating the Role-Based Access Control (RBAC) for a particular role and module by clicking on the Edit icon 15. Test the functionality of creating a new role and assigning Role-Based Access Control (RBAC) to that role for the required modules of an application 16. Verify that by choosing the existing role name, admin can apply the Role-Based Access Control (RBAC) for the required modules of an application "90"The system should display an overall count of applications available within the system to the Admin. This count gives a quick overview of the total number of applications. Additionally, when the Admin clicks on the count, a detailed list of all the appl...","1. Examine the count of total Applications on the container 2. Verify the functionality of opening the list of applications with their existing modules by clicking on the Total Applications card. 3. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 4. Click and check the functionality of breadcrumbs present on the page 5. Check the functionality of adding or deleting modules in a particular application by clicking on the Edit icon. 6. Without entering the module name, check the functionality of Add button 7. By pressing on Back button ensure that admin user can be navigated to the previous page 8. Validate the functionality of adding modules to an existing corporate application by clicking on the Add Modules button. 9. Test the functionality of the Submit button when all fields are kept blank. 10. Ensure the functionality of the Add button when no data is entered in the Module Name field. 11. By pressing on Back button ensure that admin user can be navigated to the previous page 12. Examine the functionality of the pagination buttons by verifying that the admin user can navigate to the respective page upon clicking on the pagination buttons 13. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 14. By inputting invalid data into the Search textbox, check the operating purpose of Error message 15. Check the functionality of adding or deleting modules in a particular application by clicking on the Edit icon. 16. Validate the functionality of adding modules to an existing corporate application by clicking on the Add Modules button. 17. Test the functionality of the Submit button when all fields are kept blank. 18. Ensure the functionality of the Add button when no data is entered in the Module Name field. 19. By pressing on Back button ensure that the admin user can be navigated to the previous page "91"The system should display an overall count of roles assigned to users within the system to the Admin. This count gives a quick overview of the total number of assigned roles. Additionally, when the Admin clicks on the count, a detailed list of all the a...","1. Examine the count of total Assigned roles on the container 2. Confirm that the list of assigned user roles with the application, RBAC, and validity will open when you hit on the Assigned Roles card. 3. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 4. Click and check the functionality of breadcrumbs present on the page 5. Test the functionality of updating or setting the validity of a particular assigned user role by clicking on the Edit icon 6. By expiring the validity, check whether a user role reflects in the inactive user role list 7. Verify the functionality of assigning a user role with validity to a particular user by clicking on the Assign User Role button 8. Without selecting mandatory fields verify the functioning of Save button 9. Pressing on the Back button ensure that the admin user can be navigated to the previous page 10. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 11. By inputting invalid data into the Search textbox, check the operating purpose of Error message 12. Test the functionality of updating or setting the validity of a particular assigned user role by clicking on the Edit icon "92The Application Module Management functionality allows the admin to add details about new applications and their modules. The admin can also edit existing modules as needed.,"1. Verify by clicking on the Application module, the admin is navigating to the Application page and whether the list of applications with added modules is visible or not 2. Click and check the functionality of breadcrumbs present on the page 3. Validate the functionality of the Show Entries dropdown by ensuring that the selected number of entries from the dropdown is correctly displayed 4. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 5. Validate that by clicking on pagination buttons admin user is navigating to respective page or not 6. Check the placement of the plus icon on every application module. 7. Test the functionality of the Plus Icon by clicking on it opens the existing modules list and displays the available modules. "93The system should allow the Admin to add relevant details and information about a new application modules. This functionality enables the Admin to effectively manage and track the newly added applications modules within the system.,1. Ensure the functionality of adding modules to an existing corporate application by clicking on the Add Modules button 2. Test the functioning of the Submit button without adding the necessary data 94"The system should have the capability to fetch application names from the PINS Application. This functionality allows the system to retrieve and utilize the application names without requiring manual entry, ensuring consistency and accuracy of applicati...","1. Validate the functionality of the application names dropdown list, ensuring that only applications which having the client RNT are visible "95 The system should provide the Admin with the ability to add modules to the selected application. This functionality enables the Admin to enhance and extend the functionality of the application by incorporating additional modules,"1. Validate by selecting the application name from the dropdown list the already exist modules are visible or not 2. Check by selecting the application name, admin can add the modules under that application 3. Evaluate the functioning of Add button by adding duplicate data "96The system should provide the Admin with the ability to edit the details of an application. This functionality enables the Admin to update and modify the information associated with an application as needed.,1. Evaluate the functionality of adding or deleting modules in a particular application by clicking on the Edit icon. 97 The Role Management functionality enables the admin to add and edit roles and grant access to those roles based on the requirements of the system. This functionality allows for the fine-grained control of user permissions and access within the system.,"1. Verify the functionality of navigating to the Role page and displaying the list of roles with application and module-wise Role-Based Access Control (RBAC) by clicking on the Role module 2. Click and check the functionality of breadcrumbs present on the page 3. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries appear only 4. Validate that by clicking on pagination buttons admin user is navigating to respective page or not 5. Check the plus icon is placed properly on every application module or not 6. Validate the functioning of Plus Icon, by clicking on it the existing modules list should get open and displayed "98The system should provide the Admin with the ability to create new roles to accommodate specific access requirements or organizational needs. This functionality enables the Admin to define customized roles that align with the access control policies and...,"1. By clicking on Create New Role button, verify that the admin can create new role and provide RBAC to existing role for particular module 2. Verify the functionality of the Add button when attempting to make a duplicate entry of a role 3. Ensure that the admin can create a new roles "99The system should offer the Admin a list of available role names from which they can select when assigning roles to users or performing other role-related actions. This functionality simplifies the role selection process and ensures that the Admin choos...,1. Examine whether the added role is correctly reflecting in the role list. 100 The system should provide the Admin with the ability to associate applications with selected roles. This functionality enables the Admin to control and manage the access rights of users assigned to those roles within specific applications.,"1. Check that by selecting the applications, the application will reflect beside the Application field and that application with modules list will appear on the screen. 2. Test the functionality of Save button without selecting any field 3. Examine whether the selected applications, along with their associated modules and Role-Based Access Controls (RBACs), appear only on the page 4. Evaluate that by selecting the module checkbox all the checkboxes of RBACs get checked 5. Ensure that the Module checkbox gets cleared when unchecking any module of an access 6. Validate the functionality of the checkboxes of all modules and Role-Based Access Controls (RBACs) by checking the checkbox of an application name 7. Verify the functionality of clearing the Application Name checkbox by unchecking any RBAC checkbox. 8. Ensure the functionality of the Module checkbox by verifying that when the user clicks on it, all the checkboxes of the accesses associated with that particular module get checked 9. Verify the functionality of clearing the Module checkbox when unchecking any of the accesses associated with that module "101The system should provide the Admin with the ability to modify the details of roles and add additional modules as needed. This functionality enables the Admin to customize and update the role configurations to align with evolving organizational requirem...,1. Evaluate the functionality of updating Role-Based Access Control (RBAC) for a particular role and module by clicking on the Edit icon 102"The User Role Management functionality allows the admin to view the access of applications and roles assigned to users, along with their validity periods. This functionality provides the admin with visibility and control over user roles within the syste...","1. Verify the functionality of navigating to the User Role page and displaying the list of user names along with their assigned role, application, and validity date by clicking on the User Role module 2. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with single click 3. Evaluating the functionality of the Search textbox by entering valid data and ensuring that only the relevant entries appear. 4. Validate that by clicking on pagination buttons admin user is navigating to respective page or not 5. Check the placement of the plus icon on every user role name 6. Validate the functionality of the Plus Icon by clicking on it correctly displays the list of existing applications and modules. "103The system should provide the Admin with the ability to assign roles to a specific user. This functionality enables the Admin to manage user access and permissions by associating them with the appropriate roles.,1. Validating the functionality of assigning a role to multiple users with validity by clicking on the Assign User Role button 104The system should provide the Admin with the ability to modify the validity of user roles by updating the relevant fields. This functionality enables the Admin to manage the access rights and permissions of users within specific time periods.,1. Test the functionality of updating or setting the validity of a particular assigned user role by clicking on the Edit icon. 105 The admin will be eligible to access the application after successful login and will be redirected to the admin dashboard page. Admin will have access to all different modules.,1. To check that the system allows users to log in successfully with valid credentials. 2. Examine the system handles login attempts with an invalid username and valid password appropriately. 3. Ensure that the system handles login attempts with a valid username and an invalid password appropriately. 4. When the system properly handles attempts to log in with both the username and password fields left blank. 106"The user can login with their credentials and views the dashboard. The admin, upon accessing the application and navigating to the admin dashboard, will have the ability to view graphical representations of data in the form of charts. These charts provi...","1. To confirm that the Interviews, Institutes, and Feedback details are correctly shown on the graphical representation in the application. "107" The dashboard presents an interface that includes various skill cards (Java, Python, BA) displayed on the screen. These skill cards serve as visual representations of different skills or areas of expertise within the system. By clicking on any of the sk...",1. Examine that the Dashboard's functionality related to quiz assignment works correctly. 2. To confirm that the Test Configuration functions correctly and allows the user to configure tests as intended. 3. Check whether the 'Add' button for adding a batch Code functions. 4. To ensure that the test assignment functionality for a candidate works. 5. Examine the Question Management functionality works correctly. 6. When the 'List of Skills' functionality works correctly with valid data. 7. Validate that the Test Summary functionality accurately displays details for all subjects. 8. Check the 'Test Score' functionality accurately displays scores for employee/candidate records. 9. To ensure that the 'Employee Test Score' functionality accurately displays scores for employee records. 10. Check whether the 'Test Feedback' functionality accurately displays feedback for all questions. 11. Examine that the Productivity Evaluation Tool tab functions correctly. 12. Check whether the candidate information functionality show in tabular manner. 108"Once employees successfully log into the system, they will be directed to their respective dashboard. The employee dashboard provides a personalized interface where employees can access relevant information and perform various tasks. They can view the i...","1. When the list of Test names, Skills, Difficulty Levels, and Actions is accurately and appropriately presented in a tabular format. 2. Check whether the Add button is clickable. 3. Ensure that the Search box correctly filters and displays relevant results when provided with valid details. 4. Examine the admin can successfully view and delete already added valid data. 5. Check the Previous and Next buttons are clickable and navigate through the pages correctly. 6. Validate the Show Entries drop-down field displays the expected number of entries per page. 7. To ensure that the Test Name functionality works correctly when entering valid data. 8. When the Role Type drop-down field allows the selection of valid data. 9. Check whether the Skill drop-down field on the Test Configuration page functions as intended. 10. To evaluate the functionality and options of the Difficulty Level drop-down field on the Test Configuration page. 11. In the Add button functions correctly when clicking the Get Questions button on the Test Configuration page. 12. To confirm the presence and functionality of the Close button or icon on the Test Configuration pop-up. "109" Once SME successfully logs into the system, they will be directed to their respective dashboard. The SME dashboard provides a personalized interface where they can access relevant information and perform various tasks. SMEs could check the answers and a...",1. Ensure that the Question tab functions correctly based on the selected type (Batches or Candidates). 2. Validate the Edit functionality in Question Management correctly assigns questions to candidates. 110"In the test configuration, tests are displayed in a data table format with columns for Test Name, Skill, Difficulty Level, and Action. The data table includes pagination and search features for easy navigation and management. The Action column provides ...",1. Check the list of tests with skills present in the Dashboard. 2. Ensure the Search box field functionality with valid details. 3. Check the Admin can Preview the already added valid data. 4. Check the Admin can edit and update the already added valid data 5. Check the Admin can Delete the already added valid data. 6. To test the working of the Previous and Next buttons are clickable. 111"The system shall provide functionality to validate and reflect the applicant's name, including special characters, in the (CAAMS) for an existing account. This validation process shall compare the applicant's name in CAAMS with the validated data from ...",1. Verify whether an applicant's name with a special character is reflected in CAAMS as validated in the FAI UI for an existing account. 112The system shall provide functionality to validate and ensure that the contact name reflected in the CAAMS matches the contact name validated in the FAI User Interface (UI). This validation process is critical to maintaining data consistency and accurac...,1. Verify to ensure that the contact name reflected in CAAMS matches the one validated in the FAI UI. 113Contact number in CAAMS matches the one that validated in the FAI UI.,1. Verify to ensure that the contact number in CAAMS matches the one that validated in the FAI UI. 114 The system shall address and resolve issues related to the failure of the BOT in creating tasks for certain instances. This functionality is crucial to ensure the reliability and effectiveness of the task creation process.,"1. Verify that Bot has created the Caams task for every LOB, for successful non declination cases submission. 2. Verify that Bot has not created the Caams task for the LOB submission for the declined policy. "115The system shall address and resolve issues related to the failure of the BOT in sending exception emails to the Scan Queue. This functionality is crucial to ensure that exceptions and error notifications are promptly delivered and processed.,1. Check the BOT forwards Exception mail Exception Scan Queue with the error description and the attachment for the process with the error request 116The system shall provide functionality to handle situations where a Doing Business As (DBA) name exceeds the 30-character limit. This functionality is essential to ensure that DBA names are accurately recorded and managed even when they exceed the speci...,1. Verify the behavior of submission of the balance characters into Name Continuation field if the DBA name contains more than 30 characters and 30th characters is space. 2. Verify the behavior of submission of the balance characters into Name Continuation field if the DBA name contains more than 30 characters and 30th character is NOT space. 3. Verify the behavior of the DBA name field can include less than 30 characters. 117" The system shall provide functionality to handle and process special characters within the Applicant Name parameter. This functionality is essential to ensure the accurate and secure processing of applicant names, even when they contain special characte...","1. Verify that the submission of the policy when Applicant Name contains special characters(comma, full stop, backward slash, forward slash). 2. Verify that the submission of the policy when applicant name contain special character (plus sign should be considerd as And character). 3. Verify that the submission of the policy when Applicant Name contains special characters(aphostrophe, &). 4. Verify that the submission of the policy when Applicant Name does not contains special characters "118 Functional Requirement Description: The system shall provide functionality to handle and process special characters within the Doing Business As (DBA) Name parameter. This functionality is essential to ensure the accurate and secure processing of DBA na...,"1. Verify that the submission of the policy when DBA Name contains special characters(comma, full stop, backward slash, forward slash, plus sign). 2. Verify that the submission of the policy when DBA name contain special character (plus sign should be considerd as & And character). 3. Verify that the submission of the policy when DBA Name contains special characters(aphostrophe, &). 4. Verify that the submission of the policy when DBA Name does not contains special characters "119The system shall provide functionality to verify whether the Contact Name contains a third name. This functionality is essential for ensuring that Contact Names are accurately processed and analyzed to identify the presence of additional names.,1. Verify the submission of the Contact Name if it contains more than 2 words. 2. Verify the submission of the Contact Name if it contains 2 or less words. 120" With the successful login, users will gain full access to the application, enabling them to utilize its features, functionalities, and resources according to their assigned roles and permissions. This ensures that authenticated users can effectively int...","1. After entering the URL into the browser, ensure that the user navigates to the valid login screen. 2. Check that proper placeholders are present in the Username and Password fields. 3. Ensure that the Username field successfully accepts user-inserted text as input. 4. Check that the Password field successfully accepts user-inserted text as input, allowing users to enter their desired password or login credentials into the field. 5. Users can log in by providing a valid username and password in the corresponding text boxes for those fields. 6. The user can log in if they input an invalid username and a valid password in the corresponding Username and Password fields. 7. Ensure that the user can log in functionality, after entering a valid username and an invalid password in the appropriate fields. 8. Check if a user can log in functionality, after providing an invalid username and invalid password in the corresponding fields for those two. 9. Confirm that the text displayed in the Password field is in encrypted format. 10. Confirm that, upon clicking the Eye icon, the text within the Password field is shown. 11. Ensure that the functionality of the Reset button by ensuring that all entered data is cleared from the respective fields upon clicking the Reset button. 12. Ensure that the Login button and the Reset button are appropriately labeled. 13. Confirm whether the user can successfully copy the text from the Password field. 14. Check that the logo, name of the application, username and password fields, and the login button are visible and properly aligned on the login page to validate the user interface (UI) of the application. 15. Check whether the login page of the application is compatible with various browsers like Chrome, Microsoft Edge etc., and their version. "121" Upon successful login, users will be redirected to the home screen, which prominently features the projects section. The home screen provides a centralized view of all available projects, allowing users to easily navigate and access project-related info...","1. Check the Counting panel at the top of the home page, which contains the total projects, today's reported bugs, active projects, and inactive projects fields. 2. Ensure that the Count of the Total project from the counting panel same as the number of actual total projects and check if it is clickable. 3. Check that the 'Todays Reported Bugs' number in the Counting Panel contains the correct count of 'Todays Reported Bugs' and is not editable. 4. Confirm that the 'Active projects' number in the Counting Panel contains the correct amount of Project numbers and is not editable. 5. Check that the 'Inactive projects' number displayed in the Counting Panel contains the correct count of 'Inactive Project' numbers and is not editable. 6. Check that the Project cards display the Project Name on the top of each card, ensuring that the Project Name is visible and easily identifiable for users viewing the cards. 7. Check that all fields, including BR, RTM, Test Plan, Test Scenario, Test Case, Test Script, and Test Result are displayed on the project card with the proper alignment and the relevant status color in front of each field. 8. Ensure that the Project Card accurately displays the counts of Total Bugs, Open Bugs, Closed Bugs, and Reopen Bugs at the bottom of the card. 9. Check to see if all project information appears after clicking on the Project name and More buttons. 10. Confirm whether Active projects are displayed when clicking on the Active project filter and the theme of the filter is 'green' in color. 11. Confirm the presence of the search box on the home page, ensuring that it includes the appropriate placeholder. 12. Confirm that the user can successfully input the data into the 'Search box'. 13. Check the functionality of the Search bar of the 'Home Page', where the entered text and relevant data are displayed. 14. Examine the user interface (UI) of the application, ensuring that the Company name, Logo, User Profile, and Sidebar are appropriately aligned and prominently displayed on the homepage. 15. Ensure the filter operations for the Active project and display of project cards based on specific criteria. 16. Evaluate that the Sidebar labels and icons are clear and understandable. 17. Ensure that testers successfully receive the developer notification if they edit a bug and make changes in the status by developer dropdown field. 18. Check to see if testers assign a bug then developers successfully receive the tester notification. 19. Make sure that on clicking on the notification bell icon the list of all notifications is displayed. 20. Examine that if the developer/tester clicks on notification he navigates to the edit bug pop-up for that particular bug and can edit it. "122"If the user clicks on each project tab It will show all the information related to that project such as: - Project owner, Project status, Total bugs count, Start date, End date And there will be modules that show information related to each project: -RT...","1. Validate the Show Entries Dropdown Functionality for Customizing Data Display. 2. Check that the user can search the project name, customer name, start date, end date, and the project phase column data and get the respective result. 3. Ensure that in the project phase, all project data is displayed in a tabular format. 4. Check the user can successfully select 'project phase' from the dropdown, and ensure that the selected value is displayed in the corresponding field. 5. Ensure that users can view project information, including details about their team members when selecting the 'View' option. 6. Examine the status field of the business requirement, RTM, test scenario, test case, test script, and test result module within the 'View' popup window 'Project' module. 7. Confirm that the list of project names and their specific information is displayed according to the selected value from the show entries dropdown list. 8. Check that the placeholder is present for the 'Search' field of the 'Project' module. 9. Confirm that the dropdown displays a list of numerical options representing the number of entries to be shown on the table per page. 10. On the 'View' popup window of the 'Project' module, examine that the status field of the business requirement, RTM, test scenario, test case, test script, and test result module reflects the status that is selected by the user in the... "123"If the user clicks on the RTM module the data with the project name selected in the ‘select project’ field will reflect, The user can select a different project from the dropdown RTM module will have the following fields: - BR Id, Req. Id, Requireme...","1. Examine the functionality of the RTM module present in the sidebar. 2. Ensure that the selected project name from the 'Select Project' field remains stable even when navigating to another module. 3. Examine and confirm the accuracy and functionality of the client name field. 4. Examine the functionality of the tester name field, ensuring that it accepts and displays the tester's name correctly. 5. Ensure functionality of the 'Bug' count is present on the RTM page. 6. Check the bug field to ensure its accuracy, functionality, and adherence to the required specifications. 7. Ensure the functionality of the Add New RTM, after the user clicks on the Add New RTM button. 8. Examine the start date field's functionality on the Test Cases module page. 9. On clicking the RTM module page ensure the 'End Date' field Functionality. 10. Evaluate the functionality of the RTM status field, examining its behavior, and accuracy. 11. Examine the functionality of the dropdown feature in the Show entries field. 12. Ensure that the search field operates as intended, allowing users to enter search queries. 13. Check the functionality of the Add New RTM button to ensure that it performs as expected. 14. Ensure the functionality of the BR ID field by examining its behavior and ensuring it meets the requirements. 15. Evaluate and validate the functionality of the Req-ID field. 16. To ensure the correctness of the 'Requirement field', it is necessary to perform verification checks on various aspects of the provided value. 17. Check the functionality of the Add button, examining its behavior, and responsiveness. 18. Check the functionality and behavior of the data table. 19. Confirm the functionality of the reset button, ensuring that it successfully resets the form or clears the selected data as expected. 20. Check the Save button's functionality to see if it saves any changes made by the user. 21. Make sure the functionality of the RTM page's data table present in the 'RTM' module. 22. Examine the functionality of the edit icon in the action column. 23. Ensure that the user can add a test scenario from 'RTM' by selecting the Hand Pencil icon, from the RTM module. 24. Examine that if a user adds a test scenario and clicks on the save button he directly navigates to RTM without any issues or interruptions. 25. Examine the functionality of the edit icon located in the action column of the Edit RTM popup window. 26. Check the functionality of the delete icon located in the action column of the RTM popup window. 27. Confirm the functionality of the expand icon located in the action column of the data table on the RTM page. 28. Assess the functionality of the BR ID field to ensure its proper operation. 29. Ensure after entering the data into the Test scenario and Test case column with the edit function, and clicking on the save button, the user should be automatically redirected to the RTM (Requirements Traceability Matrix) module. 30. Ensure the alignment for the 'Select Project' field. 31. Check the 'RTM' module alignment, module label size in the sidebar. 32. Evaluate the 'RTM status' field, for the dropdown alignment. 33. Ensure that the selected filter value is displayed in the filter. 34. Make sure that the placeholder is present for the 'Search' file on the 'RTM' module. 35. Check the 'Download' button functionality of the RTM module. 36. Check data present in the downloaded file is the same as the user added in RTM. "124" If a user clicks on the Test Scenario module the data with the project name selected in ‘select project’ field will reflect, The user can select different project from the dropdown Test Scenario will have below fields: -Module, Requirement Id, Test ...","1. Ensure that the Test Scenario module page is successfully opened and accessible for further actions and operations. 2. Ensure that the Select Project dropdown field functions as expected, allowing users to choose a project from the dropdown menu and have the selection accurately reflected in the field. 3. Check that there are no blank values present in the dropdown list of the Select Project field. 4. Check that the project dropdown list contains all the required values with correct spelling. 5. Ensure that the alignment of the Select Project dropdown list is by the specified design or layout. 6. Check the functionality of the Client field on the Test Scenario module page 7. Ensure that the 'Status'field allows users to select and update the status of the test scenario module, reflecting the current state or progress of the scenario accurately. 8. Check the functionality of the Bugs field on the Test Scenario module page and ensure that the user can not edit the field. 9. Confirm the start date field and ensure that the user can not edit the field. 10. Examine the end date field in the Test Scenario module. 11. Check the functionality of the project name field in the Test Scenario module. 12. Evaluate the tester name field in the Test Scenario module. 13. Check the project ID field in the Test Scenario module. 14. Examine the search functionality in the search field in the Test Scenario module. 15. Ensure the dropdown feature in the Show entries field. 16. Evaluate the pagination and next icon's functionality on the 'Test scenario'. 17. Ensure the pagination 'Previous icon'functionalityon the 'Test scenario' module. 18. Examine the sorting arrow functionality in the Req ID, Test Scenario ID, and Test Scenario description fields. 19. Make sure that the alignment, size, and color of the 'Test scenario' module icon is in the sidebar. 20. Check that the 'Search' text box of the 'Test scenario module has the proper placeholder. 21. Check the alignment for the 'Show entries' field in the 'Test Scenario' module. 22. Ensure that the 'Sorting Arrows' are visible in the Req Id, Test Scenario ID, and Test Scenario description fields. "125 Test Scenario module with 'Add New Test Scenario' functionality.,"1. Ensure that, clicking on the Add Test Scenario option, a pop-up window opens successfully. 2. Ensure the correctness and proper functioning of the Req Id dropdown field. 3. Confirm the accuracy and functionality of the Test Scenario ID field. 4. Examine that the Test Scenario description field is functioning correctly 5. Check the operational performance of the save button functionalities on the 'Add test scenario' popup window. "126 Test Scenario module will be available for Tester and Business Analyst in edit mode There will be an edit option in the action column in the Test Scenario module.,"1. Evaluate the performance of the edit button functionality within the action column. 2. Ensure that the design, alignment, and size of the edit button are in the action column. "127 Access to delete in the Test Scenario module will be for the Business Analyst and Tester. There will be a Delete option in the action column in the Test Scenario module.,"1. Examine the 'Delete' functionality from action column. 2. Ensure that the size, alignment, and design of the delete icon is proper. "128The data will reflect the project name entered in the choose project form if the user clicks on the Test Case Module button. The user may choose another project from the dropdown menu. Test Case Module will include the following fields: 1. The Test ...,"1. Confirm that the Test Cases page is currently open with a click on 'Test-case' module. 2. On clicking, the Test Case module, Examine the dropdown functionality in the select project field. 3. Make sure that on the Test Case module, when the dropdown menu is first shown, it displays the correct option selected by default. 4. Confirm that the Show Entries options are displayed in a sorted order according to a specified criterion (e.g., numeric order). 5. Ensure the alignment of the select project dropdown list as per the provided specifications. 6. On clicking, the Test case module ensure that in client name field shows the customer name for the specific project. 7. Confirm that in Test case Status, the user can select the status of the project. 8. Examine the bugs field's functionalityon the Test Cases module page. 9. Examine the start date field's functionality on the Test Cases module page. 10. On clicking the Test Cases module page ensure the 'End Date' field Functionality. 11. Analyze the project name fieldon the Test Cases module page. 12. Evaluate the functionality of the tester name field in the Test Cases module page. 13. Check the project ID field that is present on the Test Cases module page. 14. Evaluate the search functionality of the search box. 15. Examine the functionality of the dropdown feature in the Show entries field. 16. Evaluate the functionality of the next page icon in the pagination. 17. Test the functionality of the previous page icon in the pagination. 18. Ensure the sorting arrow functionality in the Req Id, Test Scenario ID, Test Cases ID, and Test Cases fields. 19. Review the complete table view of the Test Cases page. 20. Confirm the alignment of the entire data table in the 'Test Case' module. 21. Ensure that the search results are relevant to the search query. 22. Examine that by using an invalid search term, no matching records are displayed. 23. Ensure that the selected filter value is displayed in the filter. 24. Check that the sortingoption works in both 'Ascending' and 'Descending' order. 25. Check the show entries dropdown field to ensure that it correctly incorporates the highlight functionality. 26. On the Test Case module, Ensure that all fields as per requirements are present on the 'Test case' Page. "129Users can add data by clicking on the ‘+’ sign in the action column and save as well Access to create and save Test Case will be with Tester and Business Analyst.,1. Confirm that a pop-up window opens after clicking on the Add Test Cases option. 2. Ensure functionality of the 'Req Id 'dropdown field is present on the test case page. 3. Check the 'Test Scenario ID' and then check whether the provided value meets those criteria. 4. Examine the Test Case ID field's functionality on the Test Cases module page. 5. Ensure that the Test Cases field meets the required criteria for correctness and adherence to specified standards. 6. Check the functionality of the save button in the Add Test Cases pop-up. 130The test Case module will be available for the Tester and Business Analyst in edit mode There will be an edit option in the action column in the Test Case module.,1. Check the functionality of the edit button in the action field to ensure that it works as intended. 2. Ensure the confirmation message when the user updates the record successfully. 131Access to delete in the Test Case module will be for the Business Analyst and Tester. There will be a Delete option in the action column in the Test Case module.,1. Check the functionality of the delete button in the action field. 2. Examine a confirmation message on a popup or alert shown as the user clicks on the delete button. 3. Make sure the record should not be deleted as the user clicks on the No on the confirmation popup. 4. Make sure that the delete functionality works as the user clicks on the Yes button on the confirmation popup. 132" For the Developer, Administrator, and Project Manager, the Test Case Module will be in view mode.",1. Ensure that the expand view functionality of the action field to ensure it is working as expected. 2. Check the alignment of an expanded table for the selected row by examining its positioning. 133" If a user clicks on the Test Script module the data with the project name selected in ‘select project’ field will reflect, The user can select different projects from the dropdown Test Script module will be having fields: -Test Case Id, Module, Subm...","1. Check that by clicking on the Test Script module the test script page should get open. 2. Examine the start date and end date present on the header. 3. Ensure the functionality of the Select Project field. 4. Check the functionality of the Tester Name dropdown, by selecting the name that should be displayed beside the tester name field. 5. Check the functioning of the test script status dropdown, the selected status display beside the Test script status field. 6. Check the functioning of the Show Entries dropdown by selecting the number from the list. 7. Ensure the functionality of the Search textbox, by entering valid data in the Search box field. 8. Examine the functionality of the Download button, by clicking on it the data should downloaded in Excel format. 9. Test the functionality of the Add Test Script button, by clicking on it user can add the test scripts for particular test cases. 10. Ensure that the user can select the specific project from the Select Project dropdown field and as per the selection of the project the data is accurately reflected in the field. 11. Check that there are no blank values present in the dropdown list of the Select Project field. 12. Check that the project dropdown list contains all the required values with correct spelling. 13. Make sure the dropdown menu for select project is precisely aligned. 14. Ensure the user can only see the client name which is presented in the header on the test script module page. 15. Ensure the functionality of the Status field on the Test script module page and the Project Status is displayed in the three categories. If it is in the Active list, it is displayed in green. 16. Check the project ID is appropriately shown on the test script module page. 17. Make sure the tester name dropdown is clickable and all assigned tester list is displayed in the tester name field on the test script module page. 18. Make sure the count of bugs for the selected project is accurately displayed as per the assigned bugs in the bug module and the user can only view it on the header. 19. Ensure that the end date of the project is displayed in the format of DD-MM-YYYY on the test script module page. 20. Ensure that the start date of the project is displayed in the format of DD-MM-YYYY on the test script module page. 21. Check the search functionality by entering the valid keyword in the search box. 22. Check that the search box handles invalid search queries gracefully. 23. Assess the operational functionality of the dropdown feature in the Show entries field. 24. Ensure that the selected filter value is displayed in the filter. 25. Check the show entries dropdown field to ensure that it correctly incorporates the highlight functionality. 26. Evaluate the functionality of the next icon's from the pagination. 27. Ensure the operational performance of the previous icon from the pagination in terms of its functionality. 28. Ensure the sorting arrow functionality in the ID, steps description, input data, and expected result fields. 29. Check that the sorting option works in both 'Ascending' and 'Descending' order. 30. Check the data table of the test script module. 31. Confirm the alignment of the entire data table in the 'test script' module. "134"If a user clicks on the Test Result module the data with the project name selected in the ‘select project’ field will reflect, The user can select a different project from the dropdown Test Result module will have fields: -Test Case Id, Module, Subm...","1. Ensure the functionality of the test result module is correctly assessed. 2. Confirm that the selected project field is correct and satisfies the specified criteria. 3. Make sure the dropdown menu for select project is precisely aligned. 4. Check the select project field to ensure it has a dropdown menu and supports the select and highlight functionality. 5. Ensure the user can only see the client name which is presented in the header. 6. Check to see if the select project dropdown is clickable and assigned project list is displayed in the dropdown. 7. Make sure the count of bugs for the selected project is accurately displayed as per the assigned bugs in the bug module and the user can only view it on the header. 8. Ensure that the start date of the project is displayed in the format of DD-MM-YYYY on the Test Plan module page. 9. Ensure that the end date of the project is displayed in the format of DD-MM-YYYY on the Test Plan module page. 10. Assess the operational effectiveness of the project name field in the Test result module page. 11. Make sure the tester name dropdown is clickable and all assigned tester list is displayed. 12. Check the project ID is appropriately shown on the Test Result module page. 13. Examine the functionality of the test result table to ensure its proper operation. 14. Check the functionality of the show entries field with the dropdown feature. 15. Test the show entries field dropdown functionality with the required values. 16. Check the show entries dropdown field to ensure that it correctly incorporates the highlight functionality. 17. Ensure that search field functionality works correctly by verifying that the displayed search results are relevant to the entered search keyword. 18. Ensure that the show entries dropdown field to ensure that it correctly incorporates the highlight functionality. 19. Check the show entries dropdown field to ensure that the highlight functionality is working correctly. 20. Evaluate the search functionality of the search box. 21. Ensure that the search results are relevant to the search query. 22. Examine that by using an invalid search term, no matching records are displayed. 23. Confirm the alignment of the entire data table in the 'Test Result' module. "135Users can add data by clicking on the ‘+’ sign in the action column and save as well Access to create and save Test Result will be with Tester only.,"1. Check the functionality of the Add Test Result button to ensure that it performs as expected. 2. Ensure the functionality of the Req Id field by examining its behavior and ensuring it meets the requirements. 3. Check if the alignment of the dropdown values in the Req Id field is correct. 4. Test the functionality of the Req Id field dropdown by checking it with a blank field. 5. Examine the functionality of the dropdown selects in the Req ID field. 6. Ensure that the dropdown functionality of the Req Id field is checked to determine if it correctly highlights the selected option when a requirement ID is chosen. 7. Check the spelling of the values in the dropdown list for the Req Id field to ensure accuracy and correctness. 8. Ensure that the alignment of dropdown values in the Test Case ID field is correct. 9. During the examination of the dropdown field for the Test Case ID, particular attention is given to verifying whether it permits the selection of blank or empty values. 10. To ensure the proper functionality of the 'Test Case ID' field dropdown select, it is necessary to verify its behavior. 11. Ensure that the 'Test case Id' field dropdown highlight functionality is functioning as expected, confirming that the dropdown menu for selecting the test case ID is visually highlighted. 12. To ensure the correctness of the 'Test-case name' field, it is necessary to perform verification checks on various aspects of the provided value. 13. The functionality of the Test Case Name field needs to be verified to ensure its proper operation. 14. Ensure the accuracy and correctness of the 'steps field' thoroughly. 15. Examine the steps column field with alphanumeric characters and special characters. 16. Ensure the accuracy and correctness of the steps field. 17. Ensure that the Expected Result column field is checked for correctness and accuracy. 18. Check the expected result column field with alphanumeric characters and special characters. 19. Review the field in the expected result column, specifically checking for any occurrences of blank spaces. 20. Ensure the correctness of the actual result column field by examining and confirming that the provided value meets the required criteria. 21. Examine the actual result column field with alphanumeric characters and special characters. 22. Ensure that the actual expected result column field contains a blank space. 23. Check the dropdown options available in the status column field. 24. Ensure that the alignment of the dropdown list in the status column field is properly verified. 25. Confirm that the functionality of selecting options from the dropdown list in the status column field is properly verified. 26. Ensure the functionality of the upload button located in the screenshot column by thoroughly examining its behavior and performance. 27. Examine the screenshot for the Image upload feature, ensuring that it includes image files of various extensions such as PNG, JPEG, and other supported formats. 28. Inspect the functionality of the upload button to verify the capability of uploading multiple images simultaneously. 29. Ensure the reset button functionality. 30. Assess the functionality of the save button by examining its behavior and ensuring that it performs the intended actions. 31. Ensure that the user navigates to the Add Test Result' pop-up. 32. Examine that when the user clicks on the reset button by entering the data in the field. 33. Ensure that all saved data is displayed in table format. "136The test Result module will be available for the Tester in edit mode There will be an edit option in the action column in the Test Result module.,"1. Check the functionality of the edit button in the action field to ensure that it works as intended. 2. Check the functionality of the 'Req Id' field to ensure that it operates as intended. 3. Test the 'Req Id' field dropdown to ensure it accurately displays a list of valid requisition identifiers and allows for seamless selection of the desired option. 4. Ensure the alignment of the dropdown values in the 'Req Id' field. 5. Check the 'Req Id' field dropdown, and check if it allows the selection of a blank field, indicating the absence of a specific requirement identification. 6. Make sure that the functionality of the dropdown is selected in the 'Req Id' field. 7. Check the 'Req Id' field dropdown highlight functionality by ensuring that when the dropdown is selected, the corresponding field is visually highlighted, allowing users to easily distinguish and focus on the selected option. 8. Examine the functionality of the 'Test case Id' field to ensure its accuracy and effectiveness. 9. Examine the alignment of the dropdown values in the 'Test case Id' field. 10. Ensure that the 'Test case field' dropdown is thoroughly checked, paying close attention to the possibility of any blank fields. 11. Examine the operational functionality of the dropdown selection in the 'Test case Id' field. 12. Examine the dropdown highlight functionality of the 'Test-case Id' field. 13. Check the 'Test case name' field to ensure its accuracy. 14. Confirm the details provided in the steps description column field. 15. Confirm the integrity of the inputted data in the steps description column by ensuring it consists of a combination of alphanumeric characters as well as special characters. 16. Check the accuracy and correctness of the steps description column field by, ensuring there are no empty spaces. 17. Ensure the accuracy of the expected result column field. 18. Ensure that the expected result column field consists of a combination of alphanumeric characters and special characters. 19. Check the expected result column field for compatibility by comparing it to a space. 20. Check the accuracy of the data entered in the field of the actual result column. 21. Ensure that the actual result column field contains a combination of alphanumeric characters and special characters. 22. Compare the contents of the actual expected result column field to a space to ensure accuracy. 23. Examine the dropdown options in the status column field. 24. Check the alignment of the dropdown list in the status column field to ensure proper positioning. 25. Confirm that the status column field dropdown list is functioning properly. 26. Examine the upload button depicted in the screenshot column to confirm its functionality. 27. Examine the image upload screenshot by comparing it with image files of varying extensions such as PNG, JPEG, and more. 28. Test the functionality of the upload button by attempting to upload multiple images. 29. Test the functionality of the reset button to ensure it operates correctly. 30. Examine the functionality of the save button to ensure its proper operation. 31. Confirm the functionality of the cancel button. 32. Ensure the confirmation message when the user updates the record successfully. 33. Check the contents of the steps column field to ensure accuracy and correctness. 34. Examine the steps column field thoroughly, ensuring that it contains a combination of alphanumeric characters and special characters. 35. Ensure the accuracy of the steps column field by thoroughly examining it for any empty spaces.ps column field with blank space. 36. Ensure that the Test Case Name' field is not editable for the user. 37. Ensure that all the entered data is clear when the user clicks on the reset button. 38. Examine that when the user clicks on the reset button by entering the data in the field. "137Access to delete in the Test Result module will be for the Tester only. There will be a Delete option in the action column in the Test Result module.,1. Check the delete functionality for the 'test script' module. 2. Ensure the confirmation pop-up is displayed while deleting the 'Test Script'. 138"The bugs module will consist of all the Bugs with the below fields: Bug ID, Project Name, Status by Tester, Status by Developer, Priority, Date of Creation, Assigned Date, Resolved Date, Reopen Date, and Round.","1. Confirm that the Bugs page is currently open with the click on 'Bugs' module. 2. Examine the functionality of the dropdown feature in the Show entries field. 3. Check the show entries field dropdown functionality with the required values. 4. Examine the show entries dropdown field thoroughly while incorporating the highlight feature. 5. Evaluate the search functionality of the search box. 6. On the Bugs module, Ensure that all fields as per requirements are present on 'Bugs' Page. 7. Ensure that the search results are relevant to the search query. 8. Examine that by using an invalid search term, no matching records are displayed. "139 If the user clicks on the Create Bugs button the pop-up with the below fields will open: Bug Id • Project Name • Status by Tester • Status by Developer • Priority • Date of Creation • Assigned Date • Resolved Date • Reopen ...,1. Test the functionality of the Create New Bug field to ensure its accuracy and effectiveness. 2. Confirm the accuracy of the project name field. 3. Examine the operational capabilities of the project name field dropdown to ensure its proper functioning. 4. Examine the project name field by utilizing a dropdown menu that has the ability to select options. 5. Examine the bug ID field to ascertain its operational effectiveness. 6. Examine the functionality of the requirement ID field. 7. Assess the functionality of the requirement ID field dropdown 8. Ensure the requirement Id field is properly linked to a dropdown menu that allows for selection and highlighting. 9. Examine the functionality of the test case ID field. 10. Assess the functionality of the test case ID field dropdown. 11. Check the test case Id field dropdown list with select and highlight functionality. 12. Ensure the accuracy of the assigned date field. 13. Examine the assigned date field to confirm its highlighted functionality. 14. Check the closed date field to ensure the user can select the 'Closed' date from the date picker. 15. Check the closed date field highlight functionality. 16. Ensure the closed date field in the 'Add new Bug' popup window from the 'Bug' module. 17. Check the accuracy of the closed date field highlight feature. 18. Ensure the assigned to field functionality. 19. Evaluate the functionality of the assigned field dropdown. 20. Ensure the assigned field dropdown has functional select and highlight features. 21. Evaluate the defect form field functionality from the 'Add New Bug' popup window of the 'Bug' module. 22. Check the assigned field dropdown for functionality that allows you to select options and highlight them. 23. Ensure the defect form field with dropdown with select and highlight functionality. 24. Test the status by tester field dropdown functionality in the 'Add New Bug' popup window of the 'Bug' module. 25. The tester field includes a dropdown menu with selectable options and the ability to highlight the chosen status. 26. Check the 'Reopen' date field functionality. 27. Test the functionality of highlighting the reopen date field. 28. Ensure the status by developer field functionality. 29. Check the status by developer field dropdown functionality. 30. Ensure the status by developer field dropdown with select and highlight functionality. 31. Examine the resolved date field functionality. 32. Check the resolved date field highlight functionality. 33. Check the tester comment field functionality. 34. Evaluate the functionality of the developer comment field. 35. Check the priority field functionality present in the 'Create new bug' field. 36. Make sure the priority field dropdown functionality. 37. Check the priority field dropdown menu that enables selection and highlights the chosen option. 38. Check the reporter/assigner field functionality. 39. Check the reporter/assigner field dropdown functionality. 40. Ensure the accuracy of the reporter/assigner field dropdown menu that allows users to select options and includes a highlighting feature. 41. Confirm the reset button functionality present in creating a new bug page. 42. Examine that when the user clicks on the save button without entering any data. 43. Confirm that all saved data is displayed on the 'Bug' page. 44. Examine that all required fields are present on the Bugs page. 45. Ensure that by default the bug ID is created. 46. Examine that user will not be able to edit Bug_Id. 47. Ensure that while creating the bug user can only able to select the 'open' option from the dropdown. 48. Confirm when the user selects the reopen status from the dropdown he can able to select the reopen date. 49. Confirm that when a user selects the bug status as 'Closed' then he can select the 'closed' date. 50. Confirm the mandatory condition for the tester comment field. 51. Ensure that when the developer gives the status as 'Resolved' then the user can close the bug. 52. Examine if the developer has not given the status of the bug and if the user tries to close that bug. 53. Ensure that all selections are cleared and reset to their default state. 54. Examine that when the user does some modification and clicks on the reset button. 55. Ensure that when the user edits the page and clicks on the reset button without doing any modification. 56. Ensure that when the user clicks on the save button by entering the data in the mandatory field. 57. Confirm that a success message is displayed to indicate the successful save. 58. Confirm that the saved data matches the entered data without any data corruption or loss. 59. Ensure that data added while creating the bug is displayed on the bug page. 140The tester and Business Analyst can edit Bugs once it’s saved in the Bugs module. There will be an edit option in the action column in the Bugs module.,"1. Examine the 'Edit A Bug' field functionality present in the action column. 2. Ensure the accuracy of the project name field. 3. Check the project name field is equipped with a dropdown menu that allows you to choose options, and it also has a highlighting feature to draw attention to the selected item. 4. Test the bug ID field functionality for validation. 5. Check the functionality and behavior of the 'Requirement Id' field. 6. Examine the dropdown functionality of the 'Requirement Id' field. 7. Examine the dropdown menu for the 'Requirement Id' field, which includes the option to choose and highlight specific items. 8. Test the functionality of the test case ID field. 9. Check the functionality of the dropdown field for the test case ID. 10. Ensure the test case ID field dropdown with select and highlight functionality. 11. Check the assigned date field functionality is present while creating the bug. 12. Examine the assigned date field highlight functionality to ensure its accuracy and effectiveness. 13. Check closed date field is present while creating the bug. 14. Ensure the closed date field highlights functionality. 15. Examine the description field functionality to ensure a user can add bug descriptions in the 'Description' field. 16. Examine the 'assigned to' functionality to ensure a user can assign bugs to the developer. 17. Examine the 'Assigned To' field dropdown functionality to ensure a user can select the developer name from the dropdown. 18. Check the 'Assigned to' dropdown with select and highlight functionality. 19. Examine the 'Defect Type' dropdown functionality that is present while creating a bug. 20. Examine the 'Defect Type' field dropdown functionality. 21. Confirm the 'Defect Type' field with a dropdown with select and highlight functionality. 22. Examine the 'Status By Tester' functionality that is present while creating the bug. 23. Examine the 'Status By Tester' field dropdown functionality. 24. Ensure the 'Status By Tester 'dropdown field with select and highlight functionality. 25. Check 'Reopen Date' functionality is present when the user wants to reopen the bug. 26. Ensure the 'Reopen Date' field highlights functionality. 27. Check 'Status By Developer' functionality is present for a developer to give the status for the bug. 28. Check the 'Status By Developer ' field dropdown functionality. 29. Check the status by developer field with dropdown with select and highlight functionality. 30. Make sure that the 'Resolved Date' field functionality is present while creating the bug. 31. Check 'Resolved Date' field highlight functionality is present while selecting the date from the date picker. 32. Check the 'Tester Comment' field present while creating the bug. 33. Ensure the functionality of the developer comment field is operating as intended. 34. Ensure that the priority field is present and the user can see all types of priority in the dropdown. 35. the Check priority field dropdown functionality is working properly and user can select priority form dropdown. 36. Confirm the priority field with a dropdown with select and highlight functionality. 37. Check the functionality of the reporter/assigner field. 38. Examine the reporter/assigner field dropdown functionality. 39. The reporter/assigner field can be checked by using a dropdown menu that allows the selection of options and provides a highlighting feature. 40. Ensure the reset button functionality 41. Check the save button functionality. 42. Ensure that the user can only edit some specific fields without any interruptions. 43. Examine that while editing the bug user can add the screenshot and links. 44. Confirm that if the user edits the data and saves it the updated data is displayed perfectly. 45. Ensure that the sorting present for Bug id is working properly. 46. Confirm that 'Bug id' is not duplicate. 47. Examine whether the bug id will decrease by one if the user deletes the bug in between. 48. Examine the sorting functionality for the Assigned date field. 49. Examine the sorting functionality for the Closed date field. 50. Make sure the previous closed date is replaced with the new one if the bug is reopened and the user closes it. 51. Ensure that the Description field accepts the alphanumeric data. 52. Check whether the user can save the data without providing a description of the bug. 53. Make sure the user may choose the reopen option from a dropdown after closing the bug. 54. Ensure that the Tester Comment field accepts the alphanumeric data. 55. Ensure that the Developer Comment field accepts the alphanumeric data. 56. Ensure that all selections are cleared and reset to their default state. 57. Examine that when the user does some modification and clicks on the reset button. 58. Confirm that when the user edits the page and clicks on the reset button without doing any modification. 59. Ensure that when the user clicks on save button by entering the data in the mandatory field. 60. Examine that when the user clicks on the save button without entering any data. 61. Confirm that a success message is displayed to indicate the successful save. 62. Confirm that the saved data matches the entered data without any data corruption or loss. "141 The tester and Business Analyst can delete Bugs once it’s saved in the Bugs module. There will be a delete option in the action column in the Bugs module.,1. Check the delete button functionality of the 'Bug' module. 2. Ensure that the confirmation message on the popup or alert is shown as the user clicks on the delete button. 3. Make sure the record will not be deleted as the user clicks on the NO on the confirmation popup. 4. Ensure that the delete functionality works as the user clicks on the YES button on the confirmation popup. 5. Ensure that if a user deletes the bug in between then the Bug id should be decremented by one. 142"All Bugs that are present in the Bugs module will be available for the Project Manager, Developer, and Administrator in view mode.",1. Test the functionality of the Bug Module's view icon to ensure its proper operation and validate that it displays the desired information accurately and effectively. 2. Ensure that on clicking the View option all the added data for that particular bug is displayed. 3. Examine the user not able to edit the data in the View fields. 143"The application will track the reconciliation process progress.Record the time taken to complete the reconciliation. 1. Time taken to accept the denial, the time from the record received on the platform till the denial is accepted.2. Time taken or resub...",1. Check user can access the Reconciliation module. 2. Check user can access and update resubmitted RFr id in the 'enter MCCA RFR id' fild. 144"Calculate the reimbursements received from MCCA. The calculations must be claim wise, RFR wise and Bill wise.",1. Validate the Total Repriced Paid Billed amount on the Claim details screen under the Reimbursed module. 2. Validate the Total Repriced Paid Reimbursed amount on the Claim details screen under the Reimbursed module. 3. Validate the Pending Reimbursement amount at the Claim level on the Claim details screen under the Reimbursed module. 4. Validate the Total Reimbursement Received amount from the Historic RFR details screen. 5. Validate the Pending Reimbursement is equals to the (Total Amount Billed - Total Reimbursement Received). 6. Validate that the Pending Reimbursement is equal to the (Total Amount Billed - Total Reimbursement Received). 145" The login page will lead the user to the portal's dashboard, where the user can perform various operations for which this program is intended to be used dependent on the user's access. Before accessing the portal, the user must have valid logi...","1. Examine the result when a valid User ID and password are entered and check if the Login button is active. 2. If the user wants to delete all of the data they have filled, they can do so by clicking on the Reset button. 3. Examine the outcomes and click the Login button when the User ID field is left empty and the Password field is filled in. 4. Check the login functioning when the user inputs the User ID but leaves the password box blank. 5. Check the response when an invalid User ID and Password are entered and the Login button is clicked. 6. Check the response when the wrong User ID and password are entered and the Login button is clicked. 7. Check the response when a correct User ID and incorrect Password are entered and the Login button is clicked. "146"The user can view the Recruitment Status, Resource requisition, and Pending Positions in the form of a Pie chart. Positions in a particular company are represented in graphic form.","1. Check the pie charts of pending positions, resource requisitions, and recruiting status, which are each displayed in the appropriate color according to the outcome. 2. Check the functionality of the customer name dropdown, which allows users to choose a client name from a list. 3. Check out the SUBMIT button functionality, where users can view the company details in the form of a graph. "147"Based on the user role, the user will be able to access the customer list, channel list, user role, and career's password.","1. Ensure that when the user clicks on ADMIN, the list is displayed with their respective fields like Customer, Channel, User Role, and career. "148The User (the hiring manager or recruiter lead) will be able to examine all of the data related with the customer and change the customer details in the appropriate fields.,"1. Examine the Customer tab to check that customer information is in tabular format when the user clicks on it. 2. To search for a customer's details, the user can enter a value in the search bar, and all related details are displayed in the table. 3. Check all entries that have shown customer details in the tabular format by choosing the show entries dropdown. 4. The customer's entire profile can be updated by using the Pencil icon. 5. Check the Text display at the bottom left corner of the customer table to view a selected number of entries out of the total entries. 6. At the bottom right, check the Page Navigation button functionality to show the Previous and Next page information of customers. "149" The User (hiring manager, recruiter lead, or recruiter) will be able to add channels and change their state to active or inactive. The user will also be able to change and remove channel names.","1. The user can create a channel by clicking the Add Channel button from the Channel home screen. 2. Check that all of the information entered into the Add Channel can be removed using the Reset button on the pop-up. 3. If user wants to check the particular records, then using the Search Bar user can check the records. 4. Using the show entries dropdown, user can expand the records in the table. 5. Ensure that user can change the details of any particular channel using the Edit icon in the action column. 6. Check the functionality of the text display at the bottom left corner of the channel table to view the number of entries out of the total entries. 7. Make sure that the bottom right-side page navigation buttons show the Previous and Next page information of the channel in the tabular format. 8. Examine that the Delete button is available in the action column to delete the records of the channel. "150" The User will be able to assign a user role to each employee. Any of the following user roles can be assigned: Hiring Manager, Recruiter Lead, or Recruiter. (Inactive)","1. Using the ADD USER ROLE button, the user may create a user role for any user that provides specific details about the user's username and Role. (Inactive) 2. Examine that all the entered information from the ADD USER ROLE can be deleted; for that, check the Reset button by clicking on it.(Inactive) 3. To search the user details with respect to the User Name and Role, the search bar is present on the user role screen.(Inactive) 4. To expand the list of users that has been shown on the screen, using the show entries dropdown, the user can check the list.(Inactive) 5. To Update the User Role for any user, make sure that the pencil icon is present in the Action column.(Inactive) 6. Check the delete using the Dustbin icon present in the Action column of the User Role table.(Inactive) 7. Check that the Text display is at the bottom left corner of the User Role table to view the selected number of entries out of the total entries.(Inactive) 8. At the bottom right side, check that the PAGINATION buttons are set to show the PREVIOUS and NEXT page lists of the user.(Inactive) "151"The password will be changeable by the user. To update the password, the user must fill out three fields: old password, new password, and confirm password.","1. Check if the Careers tab is available to change the user password. 2. See the response when the Old Password, New Password, and Confirm Password fields are empty and the Change Password button is clicked. 3. To view the outcomes, when we click on the Change Password button without entering the old password and entering the New Password, Confirm Password appears. 4. Check the change password button functionality when the user enters the Old Password but leaves the New Password and Confirm password text boxes unfilled. 5. Click the Change Password button if the user enters the right value in the New Password and Confirm Password boxes after entering the incorrect value in the Old Password. 6. Check the response when the correct Old Password, New Password, and Confirm Password are entered and the Change Password button is clicked. "152"The user can establish a requisition, post a requirement, add or check the new applicant list from jobseekers, and move that candidate to the next Review and Shortlist section from the Onboarding tab. The next portion is the candidate interview, as sche...",1. Make sure the Onboarding screen has the necessary modules to keep track of the candidates' details across the various phases. 153"The user will be able to view, create, update, and delete a requisition and maintain the details of the channels to post their requisitions.","1. Using the Add button, the user can add the new requisition to the application for further processing. 2. Make sure that all the entered information from the New Requisition has been cleared using the Reset button. 3. Using the Search bar, the user can easily find any details of the position in the tabular format. 4. Using the show entries dropdown, the user can verify any entries that haven't been displayed on the screen at that time. 5. The edit icon in the action column can be used to modify any Job post data in the resource requisition. 6. To see all of the information on the resource requisition, make sure the eye icon is visible in the action column of the resource requisition screen. 7. To delete the added requisition, select the Delete Icon in the Action column of the Resource Requisition table. 8. Check the count of which entries are displayed on the screen in tabular format and also the out-of-total count in the bottom left corner. 9. Check the PAGINATION button at the bottom right of the Resource Requisition table to display the previous and next page information of the requisition in the table. "154"In the customer sub-module, the user can add a new demand for any of the customers. To successfully add the requirement, the user must fill out the required fields.","1. The Add Requirement user can post the information of a new job vacancy post on numerous channels. 2. The user can quickly delete all inputted data from the form by clicking the Reset option on the form. 3. The user can view the full job description for the selected job role by clicking the See JD icon. 4. Check that the SEARCH bar was used to locate the information provided in tabular form below. 5. Users can use the Show Entries dropdown to extend the details provided on the screen in tabular format. 6. Use the Edit icon in the action column to change any data about the added requirements. 7. The Delete icon allows the user to simply delete any record from the table. 8. Examine the list count, which is displayed on the screen in tabular format along with the overall count. 9. The PAGINATION button allows the user to view the requirement's PREVIOUS and NEXT page information in the Post Requirement table. "155 The tracker section displays a list of candidates who have applied for a specific position. The user will have access to the candidate's basic information.(Inactive),"1. Users can add applicants to the application for the next interview round by clicking the Add To Tracker button. (Inactive) 2. If the user wants to erase all of the entered data, they have the option to do so by pressing the Reset button.(Inactive) 3. The user can utilize the dropdown to sort the details by status, which are displayed in tabular format. (Inactive) 4. The user can download all tracker data by clicking the Excel icon on the screen.(Inactive) 5. Check the search bar to find the details from the table that are related to the entered values.(Inactive) 6. The show entries dropdown can be used to extend the candidate list in the table. (Inactive) 7. The user can move the candidate from tracker to seeker by clicking the seeker's icon in the action column. (Inactive) 8. The dropped icon allows the user to move any candidate into the dropped area. (Inactive) 9. The user can update any details of the inserted entry from the table by clicking the edit icon in the action column. (Inactive) 10. To see how many entries are displayed in the table, check the total entry count in the bottom left corner of the screen.(Inactive) 11. Check the PAGINATION button capability at the bottom right side of the Tracker table to display the candidate's PREVIOUS and NEXT page information. (Inactive) 12. To check the particular job role data, the user needs to select the job role from the dropdown. (Inactive) 13. Using the dropdown menu Select Recruiter, the user can quickly check the data of any recruiter.(Inactive) "156The Review and Shortlist sub-module will allow the user to shortlist a candidate for the interview process. Shortlisted candidates will be invited for an interview.,"1. The user can search the data related with the candidate by using the Search Bar. 2. Check that the number of entries in the show entries option reflects the selected values. 3. Make sure the Eye icon in the action column displays the data for the specific candidate. 4. To update the candidate details, the user can use the edit icon in the action column. 5. Check that the desired number of entries appears in the total number of entries on the bottom left side of the review and shortlist page. 6. Make sure the user access the previous or next page at the bottom right of the review and shortlist page. 7. On the bottom right of the review and shortlist page, make sure the user access the previous or the next page. "157 The user will be able to schedule an interview for the applicants that have been shortlisted. The user will also be able to leave comments and criticism on the applicant's interview. The User will also be able to send an email with the subject 'Intervie...,"1. Ensure that the value entered in the Search bar accurately reflects the data associated with that specific value in tabular format. 2. Check that the show entries dropdown displays the number of records related with the selected value. 3. The user can give feedback to the candidate using the feedback icon in the action column. 4. When you click on the Email ID symbol in the action column, be sure that the planned interview is previewed. 5. Check that the data similar to candidate information are reflected when you click on the Eye icon. 6. The user can Schedule the interview for the candidate using the calendar icon in the Schedule Interview column. 7. Check that the count of entries visible out of the total entries is shown on the bottom left side of the page. 8. Ensure that the user can access the next and previous pages by clicking on the next page and previous page icons. 9. The Edit icon allows the user to change the details related with the candidate interview. 10. The feedback icon allows the user to view the interview feedback provided by the interviewer. "158"The user will be able to update the candidate's shortlisting status based on the interview. The user will be able to make comments and Terms & Conditions, and the Selected candidates will be reflected in the Joined Sub-Module.","1. The user can filter candidate details based on the candidate's status by selecting the status from the Select Status dropdown. 2. The user can download the candidate details in the form of an Excel sheet by clicking on the Excel icon button. 3. Ensure that the values entered in the Search bar reflect the candidate data analogous to the values entered. 4. Examine whether the Show entries dropdown reflects the exact count of entries as the selected value. 5. Examine that, by clicking on the Eye icon, the candidate's details are reflected. 6. Ensure that the user can edit the candidate details by clicking on the Edit icon in the action column. 7. Check that the user can read the recipient's details and send the email by clicking on the Email ID symbol. 8. Make sure that the user is able to generate the offer letter for the payroll candidate by clicking on the generate offer letter icon. 9. Ensure that the displayed count of entries on the bottom left side of the page is reflected in the total count. 10. Check that the user can access the previous and next pages by clicking on the pagination button on the bottom right side of the page. 11. The user can filter out the specifics of similar candidate data by selecting the recruiter name from the Select Recruiter option. 12. Check that the user can submit a request for the intern candidate's offer letter. "159"For the Developer, Administrator, and Project Manager, the Test Scenario Module will be in the expand icon.","1. To ensure accuracy, we will examine the expanded view functionality of the action field. 2. Check the alignment of the expanded table of the selected row. 3. Examine the entire table view of the Test Scenario page. 4. Examine the alignment of the entire data table. 5. Ensure that all added data in the 'Add Test Scenario' popup window, gets reflected in the data table. "160" The user will be able to browse the list of candidates who have joined the organization and will be able to update the comments, terms, and conditions associated with a specific candidate.","1. Check that the value supplied in the search bar filters out data similar to the candidate details. 2. Check that the show entries dropdown reflects the exact count of data selected in the show entries dropdown. 3. Make sure that the Eye icon in the action column reflects the data associated with the candidate. 4. Ensure that on the bottom left side of the Joined page, the displayed count of entries out of the total count of entries is reflected. 5. Check for a pagination button in the bottom right corner of the linked table to display the entries from the previous and subsequent pages. "161" Same login page for Admin, Manager and Employee. Allows to log in successfully with valid credentials.",1. Examine that user able to navigate to the respective dashboard by hitting login button by entering valid credentials. 2. Ensure that the user is unable to log in on providing incorrect data in any one of the fields. 3. Determine the functionality of the login button on entering a valid username and invalid password. 4. Make sure that user unable to log in by providing invalid data in both fields. 5. Ensure that if the user enters incorrect data in any one of the fields and click on login then the validation message must appear as Invalid username or password. 6. Check that user must be able to see the alert message if the user misses out to enter data in the username field. 7. Examine that the null field cannot be accepted as both fields are mandatory and the user must notify regarding the empty field by showing a validation message. 8. Determine that all the entered data must be cleared by hitting the reset button. 9. Ensure that all the text on buttons and fields is correct and visible. 162 The login screen validates the provided credentials and grant access to the authorized user only into Timesheet Management module to access the features provided.,"1. Once the admin has entered the application URL into the browser, check the results. 2. Check whether the user is able to login with valid Username and Password. 3. Check the response of login functionality if the valid username and invalid password are entered. 4. To verify the behavior of login functionality when the valid username and invalid password are entered. 5. Ensure the login functionality will not allow the user to access the application if both username and password are entered incorrectly. 6. Validate the functionality of the login button if the username is entered, the password field is left empty and the login button is clicked. 7. Check the response of the login button when the username is left blank and the password field is entered. "163The login module should enable the Admin and Accountant to log in and execute certain functions.,1. Check that all of the tabs on the login screen are positioned correctly. 2. Make sure the user is unable to login if he enters the wrong User ID and password after clicking the Log in button. 164"When the policy is received in the Automation Inventory table, BOT should proceed to determine whether the policy is a refereed renewal or a bypass renewal. And based on the policy type, BOT should decide the criteria for policy updates",1. Ensure that the final status of the selected Policy number is Submitted in the UPDM Automation Inventory table. 165"The BOT should conduct a policy search in PCS or TAP sales, download the expiring policy, and then update the renewal policy. And should save in the UPDM Forms Coverage Staging table for further use","1. Make sure that Bot searches the policy on 'Policy inquiry' tab. 2. Make sure that Bot selects the 'variable form' for selected policy. 3. Make sure that Bot download the policy file(PDF) from PCS 4. Ensure that Bot rename the file with selected policy id. 5. Ensure that Bot moves the downloaded file to 'Not Process' folder 6. Make sure that if policy is not found in PCS does the Bot search the policy in Tap. 7. Ensure that the Bot is able to login into the Tap. 8. Make sure that Bot search the policy on the 'Service customers' tab 9. Make sure that Bot download the policy file(PDF) from Tap 10. Ensure that Bot rename the file with selected policy id. 11. Ensure that Bot moves the downloaded file to 'Not Process' folder 12. Make sure that the Bot update the C1 status in Automation Inventory table if policy is not found in PCS and Tap. 13. Make sure that the AI builder starts the extraction process once a new file is received in the Not process folder. 14. Make sure that the AI builder model will extract the data from the PDF 15. Once extraction is complete, ensure that the Bot moves the file from the Not process folder to the Extraction folder. 16. Ensure that the Bot is able to enter the URL into the search bar of the browser and Bot redirected to the home page of Underwriter Workstation 17. Make sure that Bot searches the Account Number in UWWS. 18. Ensure that the Bot stored the data in Automation Inventory table if Agency Contact Information is found for selected Account number in UWWS. 19. Make sure that the Bot update the test data if Agency Contact Information is Blank for the selected Account number in UWWS. "166"The BOT should perform an account search in the Account Section. If the account is found in APEX, the chosen Policy must be updated.",1. Make sure that Bot checks the final status in Automation Inventory table. 2. Examine that Bot is able to enter the APEX URL into the search bar and Login into APEX. 3. Ensure that the Bot searches the policy by policy number using mod Plus 1. 4. Make sure that Bot moves to the account screen when the policy is not found on the My work section in APEX. 167"If the account can't be found in APEX, the BOT should click Add Account, and then add the account by entering the required information.","1. Make sure that the Bot searches the account number on the account search bar. 2. If the account number is not present, verify if Bot creates an account by clicking on the New account number button. 3. When the Bot creates a new account, the Bot will check if an account is present in CAAMS. If account is not present, then Bot will update the C2 status in the Inventory table. "168Create a new account if the account cannot be found. The bot should then click on Get started button and bot should select Inland Marine conversion and fill out policy-related data.,1. Ensure that Bot updates all the policy related information. 169The BOT should select Coverages from the Coverage section for the expiring Policy Term based on the Coverages selected.,"1. Verify that the BOT has filled out all the necessary fields on the general information page. 2. Make sure that BOT is able to fill the General information section details. 3. Examine the Named insured field on the General Informationscreen, which includes the Email, Phone, and DBA fields filled out by BOT. 4. Check the insuredAddress can be filled out by the BOT if those fields are required. 5. Check BOT can enter the effective and expiring date under the policy information section. 6. Make sure BOT enters all the information within the agency information area after obtaining the details from the inventory table. 7. Make sure BOT fills up the Conversion Renewal Information according to the Policy ID. 8. Ensure that the BOT is able to choose the applicable coverages as mentioned in the Inventory table for the particular policy. 9. Ensure that the BOT navigates to the policy's applicable selected coverages. (For WS selected coverage) 10. Examine that Bot selects the Scheduled Equipment Limit checkbox 11. Make sure that Bot enters the details for Blanket Equipment. 12. Ensure that the Bot enters the details for Additional Coverages 13. Ensure that the Bot enters the details for Theft Prevention Devices. 14. Ensure that the Bot enters the details for Underground Property . 15. Ensure that the Bot enters the value of Coinsurance 16. Examine that the Bot enters the value of 'Valuation'. 17. Examine that the Bot enters the details for Flat Deductible. 18. Make sure that Bot checks the Flood Exclusion checkbox on the APEX screen if Flood Exclusion checkbox is checked on form number IM441-1426. 19. Make sure that Bot checks the Flood Coverage Specific Location Limitation Endorsement checkbox on the APEX screen if Flood Coverage Specific Location Limitation Endorsement checkbox is checked on form number IM441-1444. 20. Make sure that Bot checks the Location Subject to Limitations checkbox on the APEX screen if Location Subject to Limitations checkbox is checked on form number IM441-1444. 21. Ensure that the Bot enters the details for Flood Blanket Coverage Limitation Endorsement. 22. Ensure the Bot selects the 'Flood Zone B or Shaded X Limitations' checkbox 23. Ensure that the Bot enters the details for Earthquake Limitation Endorsement. 24. Make sure that Bot checks the Earth Movement Exclusion checkbox on the APEX screen, if form number IM441-1427 is present in Automation Inventory table. 25. Make sure that Bot checks the Earth Movement Limitation Endorsement checkbox on the APEX screen if form number IM441-1443 is present in Automation Inventory table. 26. Make sure that Bot checks the Earth Movement Territories Subject To Limitations checkbox on the APEX screen, if form number IM441-1443 is present in Automation Inventory table. 27. Make sure that Bot checks the Locations Excluded checkbox on the APEX screen, if form number IM441-1443 is present in Automation Inventory table. 28. Verify if the Bot checks the Continuing Rental or Lease Expense checkbox on the APEX screen, if form number IM441-1492 is present in Automation Inventory table. 29. Verify if the Bot checks the Equipment Leased or Rented to Others checkbox on the APEX screen, if form number IM441-1442 is present in Automation Inventory table. 30. Make sure that Bot checks the Named Driver Exclusion checkbox on the APEX screen, if form number IM441-1429 is present in Automation Inventory table. 31. Make sure that Bot checks the Stacked Equipment Endorsement checkbox on the APEX screen, if form number IM441-1430 is present in Automation Inventory table. 32. Make sure that Bot checks the Well Servicing checkbox on the APEX screen, if form number IM441-1430 is present in Automation Inventory table. 33. Make sure that Bot checks the Multiple Deductible checkbox on the APEX screen, if form number IM441-1055 is present in Automation Inventory table. 34. Make sure that Bot checks the Protective Safeguards checkbox on the APEX screen, if form number IM441 1457 09 15 is present in Automation Inventory table. 35. Examine that the Bot selects the save option from the dropdown list. 36. Make sure that Bot clicks on Continue button on well service page. 37. Make sure that Bot clicks on Continue button on 'Subjectivities' page. 38. Ensure that Bot can enters the details in 'Rate section' on premium summary page. 39. Examine that Bot performs the premium field calculation correctly. 40. Ensure that information is auto populated on the 'policy coverage section' 41. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 42. Examine whether the Bot enters the details on the Additional Interest page. 43. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 44. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 45. Ensure that the Bot selects the values from the dropdown fields. 46. Ensure that the Bot selects the 'Billing Details' from the dropdown. 47. Ensure that the Bot saves the entered data in Billing Information section. "170" According to the policy ID and the coverage applicable to the policy, Bot selected the Riggers coverage. Ex-IHH-6791076-12","1. Ensure that the Bot moves to the applicable coverage (RG-selected coverage) 2. Examine whether the Bot enters the details for the 'Riggers Liability Information' section, including the mandatory fields. 3. When a mandatory field is left blank or the Bot fails to update, check the response. 4. When both the required fields are left empty or the Bot fails to update, check the response. 5. Examine whether the Bot enters the information for the Coverage Extensions section. 6. Verify that the Bot is able to enter the Supplemental coverages details. 7. Ensure that the Bot enters a value for Deductible Amount field. 8. Ensure that the Bot enters a value of for 'Valuation' field. 9. Ensure that the Bot enters a value for 'Reporting and Adjustment Period' from dropdown. 10. Make sure that Bot checks the Multiple Deductible checkbox on the APEX screen if form number IM441 1055 0608 is present in the Automation Inventory table. 11. Make sure that Bot checks the Replacement Cost checkbox on the APEX screen if if form number IM7855 or IM7851 is present in the Automation Inventory table. (IM7851 is out of scope) 12. Make sure that Bot checks the EM, flood, sewer backup exclusion checkbox on the APEX screen if form number IM7860 is present in the Automation Inventory table. 13. Make sure that Bot checks the Property Excluded checkbox on the APEX screen if form number IM7856 is present in the Automation Inventory table. 14. Make sure that Bot checks the Limited Theft Coverage checkbox on the APEX screen if if form number IM7858 is present in the Automation Inventory table. 15. Make sure that Bot checks the Named Storm Exclusion checkbox on the APEX screen if form number IM7858 is present in the Automation Inventory table. 16. Make sure that Bot check the Windstorm or Hail Exclusion check box on the APEX screen if form number 7865 is present in the Automation Inventory table. 17. Make sure that Bot will check the Named Storm Deductible check box on the APEX screen if form number 7869 is present in the Automation Inventory table. 18. Make sure that Bot will check the Tier 1 Counties check box on the APEX screen if form number IM441-1028 is present in the Automation Inventory table. 19. Make sure that Bot checks the Protective Safeguards checkbox on the APEX screen, if form number IM441-1036 is present in the Automation Inventory table. 20. Ensure that the Bot enters the details of 'Terms and Conditions.' 21. Check Bot selects the save option from the dropdown list. 22. Ensure that Bot clicks on Continue button on riggers page. 23. Ensure that Bot enters the details in 'rate' section on premium summary page. 24. Ensure that the Bot performs the premium field calculation correctly. 25. Ensure that information is auto populated on the 'policy coverage section.' 26. Examine whether the Bot enters the details for the 'Rating' section on the Premium Summary page. 27. To Examine the BOT will add the necessary details applicable as per Variable and static form numbers, If the form number is not applicable then BOT will move to the next page. 28. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 29. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 30. Ensure that the Bot selects the values from the dropdown fields. 31. Ensure that the Bot will save the entered data in Billing Information section. 32. Ensure that the Bot selects the 'Billing Details' from the dropdown. "171"Depending on their role, all application users will receive notifications. The notification will be divided into five categories: appointment, business, employee, patient, and finance. There will be two different sorts of notifications: push notificatio...","1. The user has done with their registration process, then the application is sent to the admin and the admin has approved that profile. That notification is received in the text message as well as on what's app. 2. If the user has gone with the registration but some mistakes are done, that mistake is checked by the admin and the admin rejects that profile. That notification is received in the text message as well as on what's app. 3. The user has received the text notification for successfully applying to the application. 4. The user has added the patient to the business and assigned the physiotherapist for that patient. 5. Check the notification in the phone scroll bar, if the money left in the wallet is less than 100rs only. 6. The notification is received in the application form in the wallet there is only some money left. 7. If the user has a zero balance in their wallet then that user can receive the notification in the application as well as a push notification. 8. If a patient has not paid their pay later money, when due date is exceeded by one day then the notification get received. 9. When the user has reached the ten thousand rupees amount of credit owed then the notification get received. 10. To the user, the previous month's clinic report gets received by the notification in the application. 11. The previous month's clinic report gets notified via push notification on the current month's starts. 12. The user received the notification of the daily report on their phone by push notification. 13. To check the daily report when the last appointment get completed then the notification is received in the application notification. 14. User get received the notification via push-up notification for their next appointment. 15. Through the push-up notification, a user gets a notification to mark the attendance of the patient before the appointment will be started. 16. The user gets the holiday notification via a push-up notification on the previous day of the leave day. 17. On the previous day of the holiday, the user received the notification in the application for as a reminder the tomorrow is a holiday. 18. In the device, push-up notifications are received before the ten minutes of the exercise to the patient. 19. On the patient's what's app number the remainder will be received when the physio has blocked the appointment. 20. If in case physiotherapist has blocked the slots for the patient appointment then that notification will be received to the patient via push-up notification. 21. The patient gets notified if their physio has sent the package of the appointment. 22. The notification gets received before the 30 minutes of the appointment for upcoming appointment of the patient. 23. The pay-later due date is exceeded and if the patient didn't pay the amount then the patient gets a notification. 24. The employee can receive a notification when their schedule gets changed. 25. On scanning the QR code of one patient, a notification will be received to the next appointment patient for reaching out at the location. 26. A patient has received the notification when the physiotherapist's previous patient appointment is done then the next patient received the notification. 27. When users booked an appointment for their treatment, then by WhatsApp and text message patient can receive the confirmation notification. 28. When the physiotherapist has sent the package to their patient but the patient doesn't pay then that notification will be gone like information about the patient's name, package, etc. by notification in the application. 29. If in case patient received their package and pay for that package then with all details that notification can be sent to the business. 30. At the end of the day, the notification should be received for the payment received by the patients but in the application is not marked as received. 31. In physio's over-time schedule, patient booked the appointment then by the notification physio has received the details of the booked appointment. 32. The exercise adherence rate will be calculated, and if the exercise is not complete by the patient then the adherence rate will be gone less, and the patient's physio gets a notification about the dropped-off adherence rate. "172" According to the policy ID and the coverage applicable to the policy, Bot selected the Equipment Dealers coverage.",1. Ensure that the Bot moves to the applicable coverage (ED-selected coverage) 2. Make sure that the Bot enter the details for 'Coverage Information section (Mandatory fields). 3. Make sure that the Bot enters the required details for of the Additional Coverage Section. 4. Ensure that the Bot enters the value for Deductible Amount. 5. Make sure that the Bot enters the information for Multiple Deductible. 6. Examine that the Bot selects the correct or applicable 'Valuation.' 7. Is this form number IM441-0318 01 21 presents in the Inventory table then BOT checks the Contingent Transit Coverage Endorsement check box. 8. Make sure that Bot checks the Earth Movement Coverage checkbox on the APEX screen if form number IM441-0321 01 21 is present in Automation Inventory table. 9. Make sure that Bot checks the Flood Coverage checkbox on the APEX screen if form number IM441-0323 01 21 is present in Automation Inventory table. 10. Make sure that Bot checks the Equipment Sent Off-Premises Coverage checkbox on the APEX screen if form number IM 7020 04 04 is present in Automation Inventory table. 11. Make sure that Bot checks the Equipment Sent Off-Premises Coverage checkbox on the APEX screen if form number IM441-0317 01 21 is present in Automation Inventory table. 12. Make sure that Bot check the 'Trial Period Coverage' checkbox on APEX screen. 13. Make sure that Bot enters the details of 'Terms and Conditions' 14. Examine that Bot selects the save option from the dropdown list. 15. Validate the functionality of the Continue button. 16. Ensure Bot enters the details in 'Rate' on premium summary page. 17. Examine that Bot performs the premium field calculation correctly. 18. Ensure that information is auto populated on the 'policy coverage section.' 19. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 20. Ensure that Bot enters the details on the 'Additional Interest' page. 21. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 22. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page 23. Ensure that the Bot selects the values from the dropdown fields. 24. Ensure that the Bot saves the entered data on Billing Information section. 173" The doctor will send the invitation link to patient by entering their Full name, email-id and mobile number. Gender, D.O.B. The prescription will go to patient through SMS and WhatsApp messaging. There will be a functionality where the doctor can send p...",1. From my patient user can include the patient in the business using the Add New Patient. 2. The user can easily search for patients using the name or patient phone by entering the search bar of all patients from the business. 3. If a user wants to check all patients of the particular Physio then by selecting the physio clinic and name from the dropdown they can do. 4. The doctor can add a new patient for further treatment and the maintaining details of that patient. 5. The user can check the patient card which has assign to themselves only. 6. In the patient profile by clicking on the Call Patient bar user can easily connect with the patient on the call. 7. The user can add the profile photo for the patient in the patient profile. 8. Check the basic details of the particular patient in the patient profile. 9. Change the assigned doctor of the patient by using the Reassign option in the doctors profile. 10. Check the details of the patient appointment which has upcoming . 11. By using the upcoming card user can scan the QR to mark there attendance of that appointment. 12. Check the prescription card which the patient is following currently. 13. If user wants to check the previous all prescription then by using the View History they can check. 14. The user can check the due amount of the patient in the view patient details screen in the Pay later card. 15. The user can check all previous details of the pay later using the History of in the pay later. 16. The user accepts the payments in cash of the patients by using the Accept In Clinic Payments option. 17. If the user needs to download the invoice for a particular date for patient from history they can easily do that. 18. The user needs to send the new prescription which patient details checked write now then by using the Send New Prescription button they can do. 19. The doctor needs to send the package which has already been created. 20. The doctor needs to check the package history which packages are earned by that patient. 21. If the doctor has not created the package and goes on the send package screen. 22. If patient has the ongoing package and physio wants to send the new package. 174"According to the policy ID and the coverage applicable to the policy, Bot selected the Contractors Equipment coverage.",1. Ensure that the Bot moves to the applicable coverage (CE-selected coverage) 2. Ensure that the Bot enters details for 'Contractor's Equipment Information' section(Mandatory fields). 3. Examine that BOT enters the Coverage Extensions on the APEX screen. 4. Make sure that BOT enters the details in the Supplemental Coverages. 5. Ensure that the BOT is enters the value in the Deductible field. 6. Examine that the BOT entered the values in the Percentage Deductible fields. 7. Make sure that Bot checks the Multiple Deductible checkbox on the APEX screen if form number IM441 1055 0608 is present in Automation Inventory table. 8. Make sure that Bot checks the Income Coverage checkbox on the APEX screen if form number IM 7032 04 04 is present in Automation Inventory table. 9. Make sure that Bot checks the Agreed Amount checkbox on the APEX screen if form number IM 7026 01 07 is present in Automation Inventory table. 10. Make sure that Bot checks the Boom Restriction checkbox on the APEX screen if form number IM IM 7016 04 04 is present in Automation Inventory table. 11. Make sure that Bot checks the Waterborne Endorsement checkbox on the APEX screen if form number IM 7019 04 04 is present in Automation Inventory table. 12. Make sure that Bot checks the Replacement Cost Endorsement checkbox on the APEX screen if form number IM 7020 04 04 is present in Automation Inventory table. 13. Make sure that Bot checks the Split Deductible Endorsement checkbox on the APEX screen if form number IM 7021 04 04 is present in Automation Inventory table. 14. Make sure that Bot checks the Additional Coverages Endorsement checkbox on the APEX screen if form number IM 7025 04 04 is present in Automation Inventory table. 15. Make sure that Bot checks the Continuing Rental or Lease Payments checkbox on the APEX screen if form number IM 7038 09 06 is present in Automation Inventory table. 16. Make sure that Bot checks the Below The Surface Of The Ground Exclusion checkbox on the APEX screen if form number IM 7039 07 11 is present in Automation Inventory table. 17. Make sure that Bot checks the Fire Department Service Charge Endorsement checkbox on the APEX screen if form number IM 7852 04 04 is present in Automation Inventory table. 18. Make sure that Bot checks the Limited Fungus Coverage Endorsement checkbox on the APEX screen if form number IM 7861 08 11 is present in Automation Inventory table 19. Make sure that Bot checks the Named Storm Deductible checkbox on the APEX screen if form number IM 7851 04 04 is present in Automation Inventory table 20. Make sure that Bot checks the Named Storm Exclusion checkbox on the APEX screen if form number IM 7021 04 04 IM 7864 07 08 is present in Automation Inventory table. 21. Make sure that Bot checks the Property Excluded checkbox on the APEX screen if form number IM 7856 04 04 is present in Automation Inventory table. 22. Make sure that Bot checks the Tier 1 Counties checkbox on the APEX screen if form number IM441-1028 01 08 is present in Automation Inventory table. 23. Verify that auto-populated data is displayed on the apex screen. 24. Make sure that Bot enters the information for Leased or Rented to Others on APEX screen. 25. Make sure that Bot enters the information for Installation or Rigging Property Limit in Any One Occurrence on APEX screen. 26. Make sure that Bot enter the value for Valuation on APEX screen. 27. Make sure that Bot enter the value for Agreed Amount for Specific Equipment. 28. Make sure that Bot selects the applicable Coinsurance on APEX screen (select the radio button for coinsurance) 29. Ensure that the Bot enters the details of 'Terms and Conditions' 30. Examine whether the Bot selects the Save option from the dropdown list. 31. Make sure that Bot clicks on Continue button on Contractor's Equipment page. 32. Ensure that the Bot enters the details in 'Rate' section on premium summary page. 33. Examine that the Bot performs the premium field calculation correctly. 34. Ensure that information is auto populated on the 'policy coverage section' 35. Ensure that the Bot enters the details for 'Rating' section on Premium Summary page. 36. Examine whether the Bot enters the details on the Additional Interest page. 37. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 38. The BOT will click the continue button and move to the Premium Summary page because subjectivities are out of the scope. 39. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page 40. Ensure that the Bot selects the values from the dropdown fields. 41. Ensure that the Bot will save the entered data in Billing Information section. 42. Ensure that the Bot selects the 'Billing Details' from the dropdown. 43. BOT clicks on the continue button and move to the Premium Summary page because subjectivities are out of the scope. 175"The diagnosis and the patient's name are displayed on a card. There are two cards on the screen with their physio (Dr.) photo, name, and clinic name. From the two cards above, choose 1) Appointments and 2) Upcoming Appointments. The dashboard screen's d...","1. The person is logged in using a Valid mobile number. 2. If the logging user inputs the incorrect number and clicks on the Get OTP button. 3. Check to see if the user entered the correct mobile number and the incorrect OTP number. 4. The person appears to be trying to log in to the application using a mobile number. 5. Check the user's age and the name of their diagnosis on their name card. 6. Check the user's physiotherapist card, which was displayed on the screen that included the physio's name, age, clinic name, and clinic address. 7. Check the user's upcoming appointments for Physiotherapy and the details of that. 8. Check if the user has not any upcoming appointments with their physiotherapist. 9. Make sure that user is able to see all the past appointments with all the details and marked completed in the card. 10. check if the user has not any past appointments with any physiotherapist. 11. The user has the option to look at the appointment tickets for upcoming appointments. 12. Check that if user has not any upcoming appointments with physiotherapist and the patient then user is able to see that by clicking on view tickets QR on dashboard. 13. The user can book an appointment for their physiotherapy treatment at the clinic. 14. The patient has to book the appointment for themself there needs to select the slots. 15. The patient can review the details of the selected date and time for book an appointment. 16. The patient needs the check the payment details and pay the amount for treatment to the clinic. 17. The person wants to come to the physiotherapist at their place and for this, he/she needs to book an appointment through home visits. 18. The patient needs to book the appointment for themself and select the slots at their home location and review the details. 19. After booking an appointment for home visit then user must be able to pay the amount for physiotherapy treatment. 20. The patient can view the card's details with the remaining time for paymenton the patient dashboard. 21. The patient can check the appointments that their physiotherapist has scheduled for them and enter their home address and any other locations they need to ride to the patient's home. 22. The patient has reached on the review appointments screen and directly click on the Confirm button. 23. If the physiotherapist has blocked the appointment for the patient at clinic only then patient doesn't need to add home location. 24. Check the bill details of the blocked appointments by the physiotherapist. 25. Check the terms and conditions of the payment policy's on bill details screen. 26. The patient must make the payments for the physiotherapist's blocked appointment. 27. Check the Pay Later details on the card which has displayed on the patient dashboard screen. 28. The patient can pay the amount which has remains to paid to the business on clicking the Pay Now button. 29. From the History option on the Pay Later card, the user can check there all payment history till date. 30. If a patient needs an invoice, they can download it from their pay later history. 31. There is a screen named as Clear dues to clear previous dues. After clearing previous dues, user can book an appointment with the physiotherapist 32. Check if user accepted the prescription sent by the physiotherapist. 33. If the patient has rejected the prescription alert has sent by the physiotherapist. 34. Check the all details of the prescription on today's exercises card on dashboard. 35. Start to do the exercises from the today's exercises card which has displayed on dashboard. 36. Without completing the all exercises if the patient is back on the previous screen. 37. If the user wants to book an appointments for the both Clinic and Home visit then user can also book for this and pay with Pay Later option. 38. If patient wants to book an appointment then patient is able add slots and pay the amount using the razor pay. 39. After book an appointments the patients wants to share the all booked appointments tickets. 40. If patient wants to share the particular appointment ticket from the all booked appointments tickets 41. Check the card which has shows the details of the upcoming appointments. 42. The patient can track the physiotherapist or check the clinic location on the map using the option on the card. 43. If the patient needs to download the Invoice of the upcoming appointment to store in the personal device. 44. If user wants to view the booked appointment tickets which has upcoming appointment then they can view using the View Ticket button. 45. If in case patient wants to cancel the booked appointment then user can easily cancel there appointments using the Cancel Appointment button. 46. In the appointments of the Past, the user can check the cards of the past appointments with some details. 47. If the patient wants to download the invoice of the appointment which is past then from the card in the past appintments easily can download. 48. The patient have an option to give their valuable experience rating to the particular physiotherapist. 49. If in case patient have any complaint about the treatment from the any appointments of the physio then they can do using the Report option. "176" According to the policy ID and the coverage applicable to the policy, Bot selected the CE Leased or Rented Equipment coverage.","1. Ensure that the Bot moves to the applicable coverage (CR-selected coverage) 2. Ensure that the Bot enters the details for 'CE Leased or Rented Equipment' section (Mandatory fields). 3. When one required field are left empty or the fails to update then check the response 4. When both required fields are left empty or the fails to update then check the response of the Bot 5. Make sure that Bot checks the Multiple Deductible checkbox on the APEX screen if form number IM441 1055 0608 is present in Automation Inventory table. 6. Make sure that Bot checks the Income Coverage checkbox on the APEX screen if form number IM441 1055 0608 is present in Automation Inventory table. 7. Make sure that Bot checks the Agreed Amount checkbox on the APEX screen if form number 7026 01 07 is present in Automation Inventory table. 8. Make sure that Bot checks the Boom Restriction checkbox on the APEX screen if form number IM 7016 04 04 is present in Automation Inventory table. 9. Make sure that Bot checks the Waterborne Endorsement checkbox on the APEX screen if form number IM 7019 04 04 is present in Automation Inventory table. 10. Make sure that Bot checks the Replacement Cost Endorsement checkbox on the APEX screen if form number IM 7020 04 04 is present in Automation Inventory table. 11. Make sure that Bot checks the Split Deductible Endorsement checkbox on the APEX screen if form number IM 7021 04 04 is present in Automation Inventory table. 12. Make sure that Bot checks the Additional Coverages Endorsement checkbox on the APEX screen if form number IM 7025 04 04 is present in Automation Inventory table. 13. Make sure that Bot checks the Continuing Rental or Lease Payments checkbox on the APEX screen if form number IM 7038 09 06 is present in Automation Inventory table. 14. Make sure that Bot checks the Below the Surface of The Ground Exclusion checkbox on the APEX screen if form number IM 7039 09 06 is present in Automation Inventory table. 15. Make sure that Bot checks the Fire Department Service Charge Endorsement checkbox on the APEX screen if form number IM 7852 04 04 is present in Automation Inventory table. 16. Make sure that Bot checks the Limited Fungus Coverage Endorsement checkbox on the APEX screen if form number IM 7861 08 11 is present in Automation Inventory table. 17. Make sure that Bot checks the Named Storm Deductible checkbox on the APEX screen if form number IM 7861 08 11 is present in Automation Inventory table 18. Make sure that Bot checks the Named Storm Exclusion checkbox on the APEX screen if form number IM 7864 07 08 is present in Automation Inventory table. 19. Make sure that Bot checks the Property Excluded checkbox on the APEX screen if form number IM 7864 07 08 is present in Automation Inventory table. 20. Make sure that Bot checks the Tier 1 Counties checkbox on the APEX screen if form number IM441-1028 01 08 is present in Automation Inventory table. 21. Make sure that Bot checks the 'Windstorm or Hail Exclusion' checkbox on the APEX screen if form number IM 7020 04 04 is present in Automation Inventory table. 22. Make sure that Bot enters the details of 'Terms and Conditions.' 23. Examine whether the Bot selects the Save option from the dropdown list. 24. Ensure that Bot clicks on the continue button on CE Leased or Rented page. 25. Examine whether the Bot enters the details in the 'Rate' field on the Premium Summary page. 26. Examine that Bot performs the premium field calculation correctly. 27. Ensure that information is auto populated on the 'policy coverage section.' 28. Examine that the Bot enters the details for 'Rating' section on Premium Summary page. 29. To Examine the BOT will add the necessary details applicable as per Variable and static form numbers, If the form number is not applicable then BOT will move to the next page. 30. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 31. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 32. Ensure that the Bot selects the values from the dropdown fields. 33. Ensure that the Bot saves the entered data in Billing Information section. 34. Ensure that the Bot selects the 'Billing Details' from the dropdown. 35. Make sure that Bot clicks on the 'Continue' button of Subjectivities page. 36. Ensure that Bot click on the continue button of 'Manuscript Page' "177"According to the policy ID and the coverage applicable to the policy, Bot selected the Contingent Cargo coverage.","1. Ensure that the Bot moves to the applicable coverage (CC-selected coverage) 2. Ensure that the Bot enters details for 'Covered Property' section (Mandatory fields). 3. When a mandatory field is left blank or the Bot fails to update, check the response of the bot. 4. Make sure that Bot can enters the details on Additional Coverages section. 5. Ensure Bot can enter a value for Deductible Amount. 6. If the form number IM441 1055 0608 is present on policy form, then ensure that bot check the multiple deductible checkbox on the APEX screen. 7. Make sure that Bot can selects the Reporting Conditions Apply checkbox on APEX screen. 8. Ensure that the Bot enters the information for Reports. 9. Make sure that Bot checks the Additional Property Not Covered Endorsement checkbox on the APEX screen if form number IM441-0292 04 20 is present in Automation Inventory table. 10. Make sure that Bot checks the Adulterated Food Additional Coverage checkbox on the APEX screen if form number IM441-0293 04 20 is present in Automation Inventory table. 11. Make sure that Bot checks the Covered Property Endorsement checkbox on the APEX screen if form number IM441-0294 04 20 is present in Automation Inventory table. 12. Make sure that Bot checks the Covered Property checkbox on the APEX screen if form number IM441-0294 04 20 is present in Automation Inventory table. 13. Make sure that Bot checks the Designated Shipper Endorsement checkbox on the APEX screen if form number IM441-0295 04 20 is present in Automation Inventory table. 14. Make sure that Bot checks the Freight Brokers Errors and Omission's Coverage checkbox on the APEX screen if form number IM441-0296 04 20 is present in Automation Inventory table. 15. Make sure that Bot checks the Parked Trailer Coverage checkbox on the APEX screen if form number IM441-0297 04 20 is present in Automation Inventory table. 16. Make sure that Bot checks the Theft By Carrier Employee Coverage checkbox on the APEX screen if form number IM441-0297 04 20 is present in Automation Inventory table. 17. Is this form number IM441-0299 04 20 present in pdf as well as in the Inventory table then BOT checks the Theft By Refrigeration Breakdown Coverage check box. 18. Ensure that the Bot enters the details of 'Terms and Conditions.' 19. Examine whether the Bot selects the Save option from the dropdown list. 20. Ensure that the Bot clicks on the Continue button on the Contingent Cargo page. 21. Ensure that the Bot enters the details for 'rate' on premium summary page. 22. Ensure that the Bot performs the premium field calculation correctly. 23. Check that information is auto populated on the 'policy coverage section.' 24. Examine whether the Bot enters the details for the 'Rating' section on the Premium Summary page. 25. Examine whether the Bot enters the details on the Additional Interest page. 26. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 27. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page 28. Ensure that the Bot selects the values from the dropdown fields. 29. Ensure that the Bot will save the entered data in Billing Information section. 30. Ensure that the Bot selects the 'Billing Details' from the dropdown. "178 The doctor will be able to check the list of the patients who has already booked the appointment. There will be two tabs as follows 1) Today 2) Past Today: Clinic Owner will be able see all the booked appointments for present day. They can filter the li...,1. The user has an access to open the appointment summary module in the calendar and appointments. 2. Ensure that the user has an access to check the details of the appointment of their own as well as their employees. 3. This user can access the appointment summary for checking their own appointments for today and the past. 4. In this user has no access to check another employee's appointment in the appointment summary. 5. In the appointment summary user can see the cards of the patients which has shown clinic appointments of the physiotherapist. 6. Check the details of the patients to go to the location of the patient for home visit appointments 7. The doctor wants to call the patient to reach their location using the call patient option easily contact the patient. 8. The doctor wants to reach the location of the patient using the Navigate to patient location option. 9. If the patient wants to cancel their appointments with the physio and for this visited the clinic and requested before some hours to cancel their appointments. 10. If the doctor has a personal reason and canceling the patient's appointment then the patient doesn't need to pay the cancellation fee. 11. If the patient had a personal reason and canceling their appointment on time then that patient has no money will be refund. 12. The doctor wants to start the treatment for this need to scan the QR code and marked their attendance. 13. The doctor has completed the treatment of the patient and proceeded to the next appointment for this they need to mark appointment as completed. 14. The user wants to check their own and another employees those appointments which has past. 15. Check the list of their own appointments which has past. 179"According to the policy ID and the coverage applicable to the policy, Bot selected the Fine Arts Dealers coverage.","1. Ensure that the Bot moves to the applicable coverage (FD-selected coverage) 2. Make sure that the Bot is able to enter the details for the 'Coverage Extensions.' 3. Make sure that Bot enters the details for 'Supplemental Coverages' section on APEX. 4. Ensure that Bot enters the information for Deductible on APEX screen. 5. Make sure that Bot enters the details for Multiple Deductible on APEX screen. 6. Examine that Bot selects the correct or applicable 'coinsurance.' 7. Make sure that Bot checks the Breakage Coverage checkbox on the APEX screen if form number IM 7360 is present in Automation Inventory table. 8. Make sure that Bot checks the Off-Site Location Endorsement checkbox on the APEX screen if form number IM 7361 is present in Automation Inventory table. 9. Make sure that Bot checks the Department Service Charge Endorsement checkbox on the APEX screen if form number IM 7852 is present in Automation Inventory table. 10. Make sure that Bot checks the Property Excluded checkbox on the APEX screen if form number IM 7866 is present in Automation Inventory table. 11. Make sure that Bot checks the Sewer Backup Coverage checkbox on the APEX screen if form number IM 7866 is present in Automation Inventory table. 12. Make sure that Bot checks the Limited Fungus Coverage checkbox on the APEX screen if form number IM 7861 is present in Automation Inventory table. 13. Make sure that Bot checks the Named Storm Exclusion checkbox on the APEX screen if form number IM 7864 is present in Automation Inventory table. 14. Make sure that Bot checks the Named Storm Deductible checkbox on the APEX screen if form number IM 7869 is present in Automation Inventory table. 15. Make sure that Bot checks the Windstorm or Hail Exclusion checkbox on the APEX screen if form number IM 7865 is present in Automation Inventory table. 16. Make sure that Bot checks the Split Deductible Endorsement checkbox on the APEX screen if form number IM 7870 is present in Automation Inventory table. 17. Make sure that Bot checks the Earthquake Coverage Provided checkbox on the APEX screen if form number IM 7807 is present in Automation Inventory table. 18. Make sure that Bot checks the Flood Coverage Provided checkbox on the APEX screen if form number IM 7807 is present in Automation Inventory table. 19. Make sure that Bot checks the Tier 1 Counties checkbox on the APEX screen if form number IM441-1028 is present in Automation Inventory table. 20. Make sure that Bot checks the Protective Safeguards checkbox on the APEX screen if form number IM441-1036 is present in Automation Inventory table. 21. Ensure that Bot can enter the details for 'Terms and Conditions' on APEX screen. 22. Examine that Bot selects the save option from the dropdown list. 23. Ensure that Bot clicks on Continue button on fine arts dealers page. 24. Make sure that Bot enters the details in 'Rate' on premium summary page. 25. Ensure that Bot performs the premium field calculation correctly. 26. Ensure that the information is auto populated on the 'policy coverage section.' 27. Make sure that Bot enters the details for 'Rating' section on Premium Summary page. 28. To Examine the BOT will add the necessary details applicable as per Variable and static form numbers, If the form number is not applicable then BOT will move to the next page. 29. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 30. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 31. Ensure that the Bot selects the values from the dropdown fields. 32. Ensure that the Bot will save the entered data in Billing Information section. "180"According to the policy ID and the coverage applicable to the policy, Bot selected the CE Small Tools Floater coverage.","1. Ensure that the Bot moves to the applicable coverage (CS-selected coverage) 2. Make sure that the Bot enters the details for 'Small Tools Floater' section (Mandatory fields). 3. When a mandatory field is left blank or the Bot fails to update, check the response of Bot. 4. When Both required fields are left empty or the Bot fails to update, check the response of the Bot. 5. Make sure that Bot checks the Percentage Deductible Endorsement checkbox on APEX screen if form number IM 7018 06 04 is present in Automation Inventory table. 6. Make sure that Bot checks the Waterborne Endorsement checkbox on the APEX screen if form number IM 7019 04 04 is present in Automation Inventory table. 7. Make sure that Bot checks the 'Replacement Cost Endorsement' checkbox on the APEX screen if form number IM441 1055 0608 is present in Automation Inventory table. 8. Make sure that Bot checks the 'Split Deductible Endorsement' checkbox on the APEX screen if form number IM441 1055 0608 is present in Automation Inventory table. 9. Make sure that Bot checks the 'Additional Coverages Endorsement' checkbox on the APEX screen if form number IM441 1055 0608 is present in Automation Inventory table. 10. Make sure that Bot checks the 'Below the Surface of the Ground Exclusion' checkbox on the APEX screen if form number IM441 1055 is present in Automation Inventory table. 11. Make sure that the Bot enters the details of 'Terms and Conditions.' 12. Examine whether the Bot selects the Save option from the dropdown list. 13. Examine whether the Bot clicks on Continue button on small tool floater page. 14. Ensure that the Bot enters the details in 'rate' on premium summary page. 15. Ensure that Bot performs the premium field calculation correctly. 16. Ensure that information is auto populated on the 'policy coverage section.' 17. Ensure that the Bot enters the details for 'Rating' section on Premium Summary page. 18. To Examine the BOT will add the necessary details applicable as per Variable and static form numbers, If the form number is not applicable then BOT will move to the next page. 19. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 20. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page 21. Ensure that the Bot selects the values from the dropdown fields. 22. Ensure that the Bot will save the entered data in Billing Information section. 23. Make sure that Bot clicks on 'Continue' button of 'Subjectivities' page. "181Clinic report:- This report is a monthly report which will showcase the performance of the clinics. It will show collections and net earnings per clinic and Physio. Employee Report:- This page will show analytics related to all the physiotherapist worki...,"1. The user wants to check their business report with all payment details and appointments by all clinics. 2. In the business report there are three categories Clinic report, Employee report, Business report. 3. If a user wants to examine the report of the previous month then the user must be able to see that by selecting the clinic. 4. Check that by selecting the clinic name user is able to see the count of employees working, the number of patients visited, and ratings given by patients for that particular clinic. 5. The user can check the collections, refunded amount, and net earnings of the selected clinic with earning per doctor. 6. Examine the count of newly visited patients, converted and the conversion rate in percentage of that clinic. 7. Ensure that the user must be able to see the percentage of appointment utilization and total cancellation count of the previous month by selecting the clinic. 8. If user wants to share a previous month report to anyone, then user must be able to do it by using share button. 9. To check the history till the current date, make sure that the report history option is functional. 10. Make sure that on selecting employee report user must be able to see the data of all employees working under that business. 11. In order to see the data of the employees user must have to select clinic name. 12. Ensure that by clicking on the employee details card the user must be able to visit the employee profile in which all the details such as the experience and the patient visited count appear. 13. After visiting the doctor's profile user must be able to see the details of the doctor such as designation, specialization, clinic name, etc. 14. The user can examine the selected employee attendance for the clinic as well as for the home visit appointments with the leaves taken by that employee. 15. To check the attendance history of any employee the history option is available and by choosing the year and month the user is able to check the monthly attendance till the date. 16. To check the ratings and reviews given by patients for that particular employee make sure that ratings & reviews button is functional. 17. Examine that user is able to see the exact percentage of the conversion rate of new cases and converted cases. 18. Determine the count of late appointments which shows the exact count of appointments for which doctors visited late. 19. Make sure that in the appointment type distribution card user is able to see the exact percentage of Home visits and clinic appointments. 20. The user can check the utilization of the appointment in percentage by using the total appointment count and the empty slots count. 21. Analyze the total count appear in progress bar by calculating the cancellation count by doctor as well as by the patients. 22. The user can check the daily report of their business by clicking on the business report. 23. The user can check the history for the Net earnings, Earnings per doctor and appointments count till the date by choosing year and month from dropdown in the history option on the daily screen. 24. If the user wants to examine the report of their business for the week of the day then by choosing the weekly tab user can easily check the reports for whole week. 25. Ensure that the user has the history functionality to check all report of the business till the date by selecting the year and month. 26. In the monthly tab, the user can check the whole business report like net earnings, earnings per clinic, earnings per doctor, etc for a clinic for the previous month 27. After visiting the clinic reports a user can examine the doctor's report by choosing the doctor tab on the monthly business report screen. 28. The user can check the detailed report till the date for all clinics as well as for all doctors in the history tab by choosing the year and month. "182"According to the policy ID and the coverage applicable to the policy, Bot selected the Cell Tower coverage.","1. Ensure that the Bot moves to the applicable coverage (CT-selected coverage) 2. Make sure that Bot can enter the details for 'Coverage Section' on APEX screen. 3. Make sure that Bot can enter the details for Coverage Extensions on APEX screen. 4. Examine that Bot enters the details for Supplemental Coverages section. 5. Ensure that the Bot enters the details for Deductibles section. 6. Ensure that the Bot enters the details for Named Storm Deductible on APEX screen. 7. Examine that the Bot enters the value for Coinsurance. 8. Examine that the Bot enters the value for a Valuation 9. Ensure that the Bot enters the details for Reporting on APEX screen. 10. Ensure that the Bot enters the details for INCOME COVERAGE PART. 11. Make sure that Bot checks the Named Storm Endorsement checkbox on the APEX screen, if form number IM441-0292 04 20 is present in Automation Inventory table. 12. Examine that Bot selects the save option from the dropdown list. 13. Make sure that Bot clicks on Continue button on Cell Tower page. 14. Examine that Bot enters the details in 'rate' section on premium summary page. 15. Examine Bot performs the premium field calculation correctly. 16. Ensure that information is auto populated on the 'policy coverage section.' 17. Ensure that Bot enters the details for 'Rating' section on Premium Summary page. 18. Make sure that Bot enters the details of 'Additional Interest' page. 19. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 20. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 21. Ensure that the Bot selects the values from the dropdown fields. 22. Ensure that the Bot will save the entered data in Billing Information section. 23. Make sure that Bot selects the applicable territories checkbox. 24. Make sure that Bot selects the 'coverage provided only in the territory.' 25. Make sure that, BOT is able to select the coverage NOT provided for the territory 26. Make sure that Bot selects the coverage NOT provided for the territory checkbox. After selecting the checkbox Bot enters the required fields. 27. Make sure that Bot enter the details after selecting the 'Coverage Provided only in the Special Flood Hazard Areas' checkbox. 28. Make sure that Bot clicks on 'Continue' button of 'Subjectivities' page. "183" According to the policy ID and the coverage applicable to the policy, Bot selected the Transportation coverage.",1. Ensure that the Bot moves to the applicable coverage (TP-selected coverage) 2. Make sure that Bot enter details for 'Covered Property' section (Mandatory fields). 3. Make sure that Bot enters the value for Deductible Amount on APEX screen. 4. Ensure that Bot enters the information for Multiple Deductible on APEX screen. 5. Ensure that the Bot can enters the details for Reporting Conditions Apply. 6. Make sure that Bot checks the Named Perils Endorsements checkbox on the APEX screen if form number IM7856 is present in Automation Inventory table. 7. Make sure that Bot checks the Backhaul Coverage checkbox on the APEX screen if form number IM 7265 is present in Automation Inventory table. 8. Make sure that Bot checks the Unattended Vehicle Exclusion checkbox on the APEX screen if form number IM7267 is present in Automation Inventory table. 9. Make sure that Bot checks the Theft Limitation checkbox on the APEX screen if form number IM 7268 is present in Automation Inventory table. 10. Make sure that Bot checks the Vehicle Alarm Endorsement checkbox on the APEX screen if form number IM 7271 is present in Automation Inventory table. 11. Make sure that Bot checks the Refrigeration Breakdown Endorsement checkbox on the APEX screen if form number 7275 is present in Automation Inventory table. 12. Make sure that Bot checks the Concealed Damage Exclusion checkbox on the APEX screen if form number IM 7275 is present in Automation Inventory table. 13. Make sure that Bot checks the Property Excluded checkbox on the APEX screen if form number IM7856 is present in Automation Inventory table. 14. Make sure that Bot checks the Limited Fungus Coverage Endorsement checkbox on the APEX screen if form number IM 7261 is present in Automation Inventory table. 15. Make sure that Bot checks the Named Storm Exclusion checkbox on the APEX screen if form number IM 7261 is present in Automation Inventory table 16. Make sure that Bot checks the Windstorm or Hail Exclusion checkbox on the APEX screen if form number IM 7865 is present in Automation Inventory table. 17. Make sure that Bot checks the Named Storm Deductible checkbox on the APEX screen if form number IM 7269 is present in Automation Inventory table. 18. Make sure that Bot checks the Split Deductible Endorsement checkbox on the APEX screen if form number IM 7270 is present in Automation Inventory table. 19. Ensure that the Bot enters the details of 'Terms and Conditions' 20. Examine that Bot selects the save option from the dropdown list. 21. Make sure that Bot clicks on 'Continue' button on transportation page. 22. Ensure that Bot enters the details in 'Rate' on premium summary page. 23. Ensure that the Bot performs the premium field calculation correctly. 24. Make sure that the information is auto populated on the 'policy coverage section' 25. Examine that Bot enters the details for 'Rating' section on Premium Summary page. 26. Ensure that the Bot enters the details on 'Additional Interest page 27. Examine that Bot clicks on continue button of 'Manuscripts Forms' page. 28. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 29. Examine that the Bot selects the values from the dropdown fields. 30. Ensure that the Bot will save the entered data in Billing Information section. 31. Make sure that Bot clicks on 'Continue' button of 'Subjectivities' page. 184"According to the policy ID and the coverage applicable to the policy, Bot selected the Household Goods movers coverage","1. Ensure that the Bot moves to the applicable coverage (HG-selected coverage) 2. Make sure that Bot enters the details of 'Carrier's Legal Liability' section on APEX screen. 3. If Bot failed to update the required field on the APEX screen then check the response of the Bot. 4. Examine that the Bot enters the details for 'Warehouseman's Legal Liability / Bailees Liability Endorsement' on APEX screen. 5. Make sure Bot selects the 'Moving Equipment and Miscellaneous Property' checkbox. 6. Make sure that Bot selects the 'Customer's Coverages - Transit And Storage' checkbox on APEX screen. 7. Make sure that the Bot selects the applicable 'Carrier's Income Protection' checkbox on APEX screen. 8. Ensure that the Bot checks the Moving Equipment and Miscellaneous Property Coverage checkbox on the APEX screen, if form number 441-0041 is present in Automation Inventory table. 9. Ensure that the Bot checks the Moving and Storage Broadening Endorsement checkbox on the APEX screen, if form number IM441-1629 is present in Automation Inventory table. 10. Ensure that the Bot checks the Windstorm Deductible checkbox on the APEX screen, if form number IM441-1055 is present in Automation Inventory table. 11. Ensure that the Bot checks the Motor Common Carrier Policies checkbox on the APEX screen, if form number MC 2414C is present in Automation Inventory table. 12. Ensure that the Bot checks the Motor Common Carrier Policies checkbox on the APEX screen, if form number MC 2414C is present in Automation Inventory table. 13. Ensure that the Bot enters the details of 'Terms and Conditions' 14. Make sure that Bot selects the save option from the dropdown list. 15. Make sure that Bot clicks on 'Continue' button of Household Goods Movers page. 16. Ensure that Bot enters the details in 'Rate' on premium summary page. 17. Examine that Bot performs the premium field calculation correctly. 18. Ensure that information is auto populated on the 'policy coverage section' 19. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 20. Examine whether the Bot enters the details on the 'Additional Interest' page. 21. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 22. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 23. Ensure that the Bot selects the values from the dropdown list. 24. Ensure that the Bot will save the entered data in Billing Information section. 25. Ensure that the Bot selects the 'Billing Details' from the dropdown. 26. Make sure that Bot clicks on 'Continue' button of 'Subjectivities' page. "185" According to the policy ID and the coverage applicable to the policy, Bot selected the Warehouse Legal liability coverage",1. Ensure that the Bot moves to the applicable coverage (WL-selected coverage) 2. Examine that the Bot enters the value for 'Catastrophe Limit' on warehouse legal liability page. 3. Ensure that BOT can enter the information for Additional Debris Removal Expenses. 4. Examine that the Bot enters the value for Defence Costs on APEX screen. 5. Examine that the Bot enters the value for Emergency Removal on APEX screen. 6. Examine that the Bot enters the value for Fraud and Deceit on APEX screen. 7. Ensure that the Bot enters the value for Earned Warehouse Charges on APEX screen. 8. Ensure that the Bot enters the value for Newly Acquired Warehouse on APEX screen. 9. Ensure that the Bot enters the value for Pollutant Cleanup And Removal on APEX screen. 10. Ensure that the Bot enters the value for Rewards on APEX screen. 11. Examine that the Bot enters the information for Deductible Amount section on APEX screen. 12. Ensure that the Bot can enters the details for Reporting Conditions Apply section on APEX screen. 13. Make sure that Bot checks the Cold Storage Coverage checkbox on the APEX screen if form number IM7669 04 04 is present in Automation Inventory table. 14. Make sure that Bot checks the Spoilage Coverage checkbox on the APEX screen if form number IM7669 04 04 is present in Automation Inventory table. 15. Make sure that Bot checks the Processing Work Coverage checkbox on the APEX screen if form number IM7675 09 06 is present in Automation Inventory table. 16. Make sure that Bot checks the Inventory Shortage Coverage checkbox on the APEX screen if form number IM7675 09 is present in Automation Inventory table. 17. Make sure that Bot checks the Défense Limit Endorsement checkbox on the APEX screen if form number IM7663 04 04 is present in Automation Inventory table. 18. Make sure that Bot checks the Flood And Earth Movement Exclusion checkbox on the APEX screen if form number IM7665 04 04 is present in Automation Inventory table. 19. Make sure that Bot checks the Leakage Of Refrigerant Exclusion checkbox on the APEX screen if form number IM7668 04 04 is present in Automation Inventory table. 20. Make sure that Bot checks the Property Excluded checkbox on the APEX screen if form number IM441-0292 04 20 is present in Automation Inventory table. 21. Make sure that Bot checks the Fire Department Service Charge checkbox on the APEX screen if form number IM7852 is present in Automation Inventory table. 22. Make sure that Bot checks the Multiple Deductible checkbox on the APEX screen if form number IM441 1055 06 08 is present in Automation Inventory table. 23. Make sure that Bot checks the Named Storm Deductible checkbox on the APEX screen if form number IM7851 04 04 is present in Automation Inventory table. 24. Make sure that Bot checks the Protective Safeguards checkbox on the APEX screen if form number IM441 1036 01 08 is present in Automation Inventory table. 25. Ensure that the Bot enters the details of 'Terms and Conditions' 26. Examine that Bot selects the save option from the dropdown list. 27. Make sure that Bot clicks on the Continue button on Warehouse Legal liability page. 28. Examine that Bot enters the details in 'rate' on premium summary page. 29. Examine that the Bot performs the premium field calculation correctly. 30. Ensure that information is auto populated on the 'policy coverage section' 31. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 32. Examine whether the Bot enters the details on the Additional Interest page. 33. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 34. Check the BOT is able to select the Bill to Name and Address check box on Billing information page 35. Examine the BOT is select the values from the dropdown fields. 36. Ensure that the Bot will save the entered data in Billing Information section. 37. Ensure that the Bot selects the 'Billing Details' from the dropdown. 38. BOT will clicks on the continue button and move to the Premium Summary page because subjectivities are out of the scope. 186" According to the policy ID and the coverage applicable to the policy, Bot selected the Rolling Stock coverage.","1. Ensure that the Bot moves to the applicable coverage (RS-selected coverage) 2. Make sure that the Bot enter details for 'Rolling Stock Liability' section (Mandatory fields). 3. Make sure that the Bot enter details for 'Rolling Stock Schedule' section 4. Examine that the Bot enters the value for Additional Debris Removal Expenses. 5. Examine that the Bot enters the value for Emergency Removal 6. Examine that the Bot enters the value for Any one item 7. Examine that the Bot enters the value for Any one Occurrence 8. Ensure that the Bot enters the value for Continuing Rental or Lease Payments 9. Ensure that the Bot enters the value for Fire Department Service charges 10. Make sure that the Bot enters the value for Pollutant Cleanup and Removal 11. Make sure that the Bot enters the value for Recharge of Fire Extinguishing Equipment 12. Ensure that the Bot enters the value for Rental Reimbursement 13. Examine that the Bot enters the value for Re-rail Expense 14. Examine that the Bot enters the value for Valuable Papers And Records 15. Examine that the Bot enters the value for Deductible Amount 16. Examine that Bot can enter the details for Multiple Deductible on APEX screen. 17. Ensure that the Bot enters the value of Valuation on APEX screen. 18. Ensure that Bot enters the required details on APEX screen after selecting the Stated Amount checkbox. 19. Examine that the Bot enters the value for Coinsurance 20. Make sure that Bot checks the Earthquake Flood Coverage checkbox on the APEX screen, if form number IM 5011 is present in Automation Inventory table. 21. Make sure that Bot checks the Earthquake Coverage checkbox on the APEX screen, if form number IM 5011 is present in Automation Inventory table. 22. Make sure that Bot checks the Flood Coverage checkbox on the APEX screen, if form number IM 5011 is present in Automation Inventory table. 23. Ensure that BOT can enter the information for Earthquake and Flood Limitations 24. Ensure that BOT can enter the information for Expanded Coverage Territory. 25. Make sure that Bot enters the details for Damage to Track/Roadbed and Extra Expense To Re-Route Rolling Stock Schedule 26. Ensure that BOT can enter the information for Property Loaned, Leased or Rented to Others - Home Office Referral Required (Specific to USI) . 27. Examine that the Bot enters the details for Flat Wheel Coverage 28. Examine that the Bot enters the details for Business Income and Extra Expense Coverage 29. Ensure that the Bot enters the details for Hi-Rail Vehicle Coverage Endorsement 30. Make sure that the Bot enters the details for Named Storm Exclusion 31. Make that the Bot enters the details for Windstorm or Hail Exclusion 32. Make sure that Bot checks the Named Storm Deductible checkbox on the APEX screen, if form number IM7851 04 04 or 221 0163 10 03 is present in Automation Inventory table. 33. Ensure that the Bot enters the details of 'Terms and Conditions' 34. Examine Bot selects the save option from the dropdown list. 35. Make sure that Bot click on 'Continue' button on Rolling Stock page. 36. Validate the functionality of the Continue button. 37. Ensure that the Bot enters the details in the 'Rate' section on the premium summary page. 38. Examine that the Bot performs the premium field calculation correctly. 39. Ensure that information is auto populated on the 'policy coverage section' 40. Make sure that Bot enters the details for 'Rating' section on Premium Summary page. 41. Examine whether the Bot enters the details on the Additional Interest page. 42. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 43. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 44. Ensure that the Bot selects the values from the dropdown fields. 45. Ensure that the Bot will save the entered data in Billing Information section. "187"According to the policy ID and the coverage applicable to the policy, Bot selected the Renewable Energy coverage.","1. Ensure that the Bot moves to the applicable coverage (RE-selected coverage) 2. Examine that the Bot enters the value for a Catastrophe Limit on APEX screen. 3. Examine that the Bot enters the value for Energy Generating Income Catastrophe Limit 4. Examine that the Bot enters the value for Electricity Replacement 5. Make sure that Bot enters the details for Additional Debris Removal Expenses 6. Make sure that Bot enters the details for Supplemental Coverages 7. Examine that the Bot enters the value for 'Valuation' on APEX screen. 8. Ensure that the Bot enters the details for the 'Deductible' Section on APEX screen. 9. Ensure that the Bot enters the details for the Multiple Deductible Section. 10. Examine Bot enter the value for Coinsurance on APEX screen. 11. Make sure that Bot enters the details for Equipment Breakdown Coverage on APEX screen. 12. Ensure that BOT can enter the information for Ordinance or Law Coverage 13. Ensure that BOT can enter the information for Increased Cost To Repair Limit 14. Ensure that BOT can enter the information for Fire Department Service Charge Endorsement 15. Ensure that BOT can enter the information for Fire Department Service Charge 16. Ensure that BOT can enter the information for Property Excluded 17. Ensure that BOT can enter the information for Sewer Backup Coverage 18. Ensure that BOT can enter the information for Limited Fungus Coverage Endorsement 19. Ensure that BOT can enter the information for Named Storm Exclusion 20. Ensure that BOT can enter the information for Named Storm Deductible. 21. Ensure that BOT can enter the information for Windstorm or Hail Exclusion 22. Verify that Bot checks the Split Deductible checkbox on APEX screen, if form number IM441-1485 06 17 is present in Automation Inventory table. 23. Verify that Bot checks the Earthquake Flood Coverage checkbox on APEX screen, if form number IM 5011 is present in Automation Inventory table. 24. Verify that Bot checks the Earth and Flood Limitation checkbox on APEX screen, if form number IM441-1050 05 15 is present in Automation Inventory table. 25. Ensure that BOT can enter the information for Tier 1 Counties. 26. Verify that Bot checks the Protective Safeguards checkbox on APEX screen, if form number IM441 1036 is present in Automation Inventory table. 27. Verify that the Bot will enter the details of 'Terms and Conditions' 28. Verify if the Bot selects the save option from the dropdown list. 29. Ensure that Bot clicks on the Continue button 30. Validate the functionality of the Continue button. 31. Verify if the Bot enters the details in 'Rate' section on premium summary page. 32. Make sure that Bot calculates the premium correctly on premium summary page. 33. Verify that information is auto populated on the 'policy coverage section' 34. Verify that the Bot enters the details for 'Rating' section on Premium Summary page. 35. Verify the functionality of 'Additional Interest page' 36. Verify the functionality of 'Manuscripts Forms' page. 37. Examine that the Bot is able to select the Bill to Name and Address check box on Billing information page 38. Examine that the Bot selects the values from the dropdown fields. 39. Examine that the Bot will save the entered data in Billing Information section. "188"According to the policy ID and the coverage applicable to the policy, Bot selected the Installation Floater coverage.","1. Ensure that the Bot moves to the applicable coverage (IF-selected coverage) 2. Make sure that Bot can enter the details for 'Covered Property' section on APEX screen. 3. Ensure that the Bot enters the details for Blanket Coverage 4. Ensure that BOT can enter the information for Scheduled Location Coverage. 5. Ensure that the Bot enters the details for Coverage Extensions 6. Ensure that the Bot enters the details for Supplemental Coverages 7. Ensure that the Bot enters the value for Deductible 8. Make sure that Bot can enter the value for 'Coinsurance' on APEX screen. 9. Ensure that Bot can enter the Reporting Conditions Apply 10. Make sure that Bot checks the Multiple Deductible checkbox on the APEX screen, if form number IM441-1055 is present in Automation Inventory table. 11. Make sure that Bot checks the Delay In Completion Coverage checkbox on the APEX screen, if form number IM 7126 is present in Automation Inventory table. 12. Make sure that Bot checks the Equipment Breakdown And Testing Endorsement checkbox on the APEX screen, if form number IM 7124 is present in Automation Inventory table. 13. Make sure that Bot checks the Testing and Commissioning Coverage checkbox on the APEX screen, if form number IM 7115 is present in Automation Inventory table. 14. Ensure that BOT can enter the information for Earthquake and Flood Coverage Endorsement. 15. Make sure that Bot checks the Earthquake and Flood Limitations checkbox on the APEX screen, if form number IM441-1050 is present in Automation Inventory table. 16. Make sure that Bot checks the Contract Penalty Endorsement checkbox on the APEX screen, if form number IM 7120 is present in Automation Inventory table. 17. Make sure that Bot checks the Business Personal Property Endorsement checkbox on the APEX screen, if form number IM 7111 is present in Automation Inventory table. 18. Make sure that Bot checks the Waterborne Endorsement checkbox on the APEX screen, if form number IM 7106 or IM 7111 is present in Automation Inventory table. 19. Ensure that the Bot enters the details for Fraud And Deceit Coverage. 20. Ensure that the Bot enters the details for Blueprints And Construction Documents Coverage. 21. Ensure that BOT can enter the information for Named Storm Exclusion. 22. Make sure that Bot checks the Windstorm or Hail Exclusion checkbox on the APEX screen, if form number IM 7665 is present in Automation Inventory table. 23. Make sure that Bot checks the Named Storm Deductible checkbox on the APEX screen, if form number IM 7869 02 09 is present in Automation Inventory table. 24. Ensure that the Bot enters the details of 'Terms and Conditions' on APEX screen. 25. Examine Bot selects the save option from the dropdown list. 26. Make sure that the Bot clicks on Continue button of Installation Floater page. 27. Validate the functionality of the Continue button. 28. Examine that the Bot enters the details in 'Rate' section' on premium summary page. 29. Examine that the Bot performs the premium field calculation correctly. 30. Ensure that the information is auto populated on the 'policy coverage section' 31. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 32. Examine whether the Bot enters the details on the Additional Interest page. 33. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 34. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 35. Ensure that the Bot selects the values from the dropdown fields. 36. Ensure that the Bot will save the entered data in Billing Information section. "189"According to the policy ID and the coverage applicable to the policy, Bot selected the Oil and Gas coverage.",1. Ensure that the Bot moves to the applicable coverage (OG-selected coverage) 2. Ensure that the Bot can enter the details for Covered Property on APEX screen. 3. Ensure that the Bot can enter the details for Additional Coverages on APEX screen. 4. Examine that the Bot can enters the value for Coinsurance. 5. Examine that the Bot can enters the value for Valuation 6. Examine that the Bot can enters the value for Deductibles 7. Make sure that Bot checks the Flood Exclusion checkbox on the APEX screen if form number IM441-1437 09 15 is present in Automation Inventory table. 8. Make sure that Bot checks the Flood Location Limitation Endorsement checkbox on the APEX screen if form number IM441-1447 09 15 is present in Automation Inventory table. 9. Make sure that Bot checks the location Subject To Limitations checkbox on the APEX screen if form number IM441-1447 09 15 is present in Automation Inventory table. 10. Make sure that Bot checks the Earth Movement Exclusion checkbox on the APEX screen if form number IM441-1436 09 15 is present in Automation Inventory table. 11. Make sure that Bot checks the Earth Movement Limitation Endorsement checkbox on the APEX screen if form number IM441-1448 09 15 is present in Automation Inventory table. 12. Make sure that Bot checks the Locations Subject To Limitations checkbox on the APEX screen if form number IM441-1055 is present in Automation Inventory table. 13. Make sure that Bot checks the Earthquake Limitation Endorsement checkbox on the APEX screen if form number IM441-1437 09 15 is present in Automation Inventory table. 14. Make sure that Bot checks the Locations Subject To Limitations checkbox on the APEX screen if form number IM441-1448 09 15 is present in Automation Inventory table. 15. Examine that the Bot selects the save option from the dropdown list. 16. Make sure that Bot clicks on Continue button of Oil and Gas page. 17. Ensure that Bot can enters the details in 'Rate' section on premium summary page. 18. Examine that the Bot performs the premium field calculation correctly. 19. Ensure that information is auto populated on the 'policy coverage section' 20. Make sure that Bot enters the details for 'Rating' section on Premium Summary page. 21. Examine whether the Bot enters the details on the Additional Interest page. 22. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 23. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 24. Ensure that the Bot selects the values from the dropdown fields. 25. Ensure that the Bot will save the entered data in Billing Information section. 26. Make sure that Bot checks the Protective Safeguards checkbox on the APEX screen if form number IM441 1457 09 15 is present in Automation Inventory table. 27. Ensure that the Bot will enter the details of 'Terms and Conditions' 28. BOT clicks on the continue button and move to the Premium Summary page because subjectivities are out of the scope. 190" According to the policy ID and the coverage applicable to the policy, Bot selected the Medical Diagnostics coverage.","1. Ensure that the Bot moves to the applicable coverage (MD-selected coverage) 2. Examine that Bot enters the details in Facility Type section. 3. Ensure Bot enters the details for 'Equipment Specifically Scheduled on Policy' on APEX screen. 4. Ensure Bot enters the details for 'Equipment At Schedule Locations on Policy' 5. Ensure Bot enters the details for 'Per Item Limit at Scheduled Locations on file dated' 6. Ensure Bot enters the details for 'Display Equipment/Location Schedule information on quote' 7. Make sure that Bot enter a value for 'Additional Debris Removal Expenses' on APEX screen. 8. Examine that Bot enters the value for 'Active Data Processing Media, Data and Programs' 9. Examine that Bot enters the value for 'Expediting Expenses' 10. Examine that Bot enters the value for 'Extra Expense' 11. Examine that Bot enters the value for 'Newly Acquired Equipment' 12. Examine that Bot enters the value for 'Pollutant Cleanup and Removal' 13. Examine that Bot enters the value for 'Rental Reimbursement' 14. Examine that Bot enters the value for 'Site Control Systems' 15. Examine that the Bot enters the value for Deductible Amount 16. Ensure that Bot enters the details for 'Multiple Deductible' on APEX screen. 17. Ensure that Bot enters the details for 'Valuation' on APEX screen. 18. Examine that the Bot enters the value for 'Coinsurance' on APEX screen. 19. Make sure if Bot checks the Income Coverage checkbox on the APEX screen if form number IM441-1022 01 2008 is present in Automation Inventory table. 20. Make sure if Bot checks the Equipment Breakdown checkbox on the APEX screen if form number IM441 1023 04 2008 is present in Automation Inventory table. 21. Make sure if the Bot checks the Earthquake Coverage checkbox on the APEX screen if form number IM7807 07 08 is present in Automation Inventory table. 22. Ensure that BOT can enter the information for Earthquake Coverage. 23. Make sure if the Bot checks the Earth and Flood Limitation checkbox on the APEX screen if form number IM441-1050 05 is present in Automation Inventory table. 24. Make sure if the Bot selects the 'applicable territories' checkbox 25. Make sure if the Bot selects the 'coverage provided only in the territory' checkbox. 26. Make sure if the Bot selects the 'coverage NOT provided for the territory' checkbox 27. Make sure that the Bot enters the required details after selecting the 'coverage NOT provided for the territory' checkbox 28. Make sure that the Bot enters the required details after selecting the 'Coverage Provided only in the Special Flood Hazard Areas' checkbox. 29. Make sure if the Bot checks the Sewer Backup Coverage checkbox on the APEX screen if form number IM7866 10 08 is present in Automation Inventory table. 30. Make sure if the Bot checks the Property Excluded checkbox on the APEX screen if if form number IM7856 04 04 is present in Automation Inventory table. 31. Ensure that the Bot enters the details for Limited Theft Coverage 32. Make sure if the Bot checks the Named Storm Deductible checkbox on the APEX screen if form number IM7851 or 221-0163 is present in Automation Inventory table. 33. Examine that Bot selects the save option from the dropdown list. 34. Make sure that Bot clicks on Continue button on Medical Diagnostics page. 35. Ensure that the Bot enters the details in 'rate' section on premium summary page. 36. Ensure Bot performs the premium field calculation correctly. 37. Ensure that information is auto populated on the 'policy coverage section' 38. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 39. Examine whether the Bot enters the details on the Additional Interest page. 40. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 41. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 42. Ensure that the Bot selects the values from the dropdown fields. 43. Ensure that the Bot will save the entered data in Billing Information section. 44. Make sure if the Bot checks the Fire Department Service Charge checkbox on the APEX screen if form number IM7852 04 04 is present in Automation Inventory table. 45. Make sure if the Bot checks the Protective Safeguards checkbox on the APEX screen if form number IM441-1365 is present in Automation Inventory table. 46. Examine that the Bot enters the details of 'Terms and Conditions' 47. BOT clicks on the continue button and move to the Premium Summary page because subjectivities are out of the scope. "191"According to the policy ID and the coverage applicable to the policy, Bot selected the Scheduled Property Floater coverage.","1. Ensure that the Bot moves to the applicable coverage (SP-selected coverage) 2. Make sure that Bot selects the Does this require an NTP checkbox on APEX screen. 3. Make sure that the Bot enters the details for Are Building and Structures Covered section. 4. Make sure that the Bot enters the details for Is Business Personal Property Covered section 5. Examine whether the Bot selects the 'Miscellaneous Covered Property Non-Location Based' checkbox on APEX screen. 6. Examine whether the Bot selects the 'Miscellaneous Covered Property Location Based' checkbox on APEX screen. 7. Make sure that Bot enters the details for Additional Debris Removal Expenses section on APEX screen. 8. Make sure that Bot enters the details for Supplemental Coverages section on APEX screen. 9. Examine whether the Bot enters the details for the Business Income Coverage Applies to Building and Structures and Personal Property section 10. Examine whether the Bot enters the details for Business Income Coverage Applies to Miscellaneous Covered Property 11. Make sure that the Bot enters the details for Equipment Breakdown Coverage Applies to Building and Structures and Personal Property section. 12. Make sure that the Bot enters the details for Equipment Breakdown Coverage Applies to Miscellaneous Covered Property section. 13. Examine whether the bot enters the value for Covered Property on the APEX screen. 14. Examine whether the bot enters the value for Income Coverages - 15. amount 16. Examine whether the bot enters the value for Income Coverages - % 17. Examine whether the bot enters the value for Income Coverages - days 18. Examine whether the bot enters the value for Deductible Description 19. Examine whether the bot enters the value for Deductible 20. Ensure that BOT can enter the information for Limited Crime Coverage. 21. Make sure that the Bot enters the details for Earthquake Coverage Provided on APEX screen. 22. Make sure that the Bot enters the details for Flood Coverage Provided on APEX screen. 23. Ensure that Bot checks the Earth and Flood Limitation checkbox on the APEX screen if form number IM441-1050 05 15 is present in Automation Inventory table. 24. Ensure that the Bot checks the Limited Fungus Coverage Endorsement checkbox on the APEX screen only if form number IM 7861 is present in the Automation Inventory table. 25. Ensure that the Bot checks the Multiple Deductible checkbox on the APEX screen, if form number IM441-1055 is present in Automation Inventory table. 26. VEnsure that the Bot checks the Named Storm Deductible checkbox on the APEX screen, if form number IM441-7851 is present in Automation Inventory table. 27. Ensure that the Bot checks the Fire Department Service Charge Endorsement checkbox on the APEX screen, if form number IM 7852 is present in Automation Inventory table. 28. Ensure that the Bot checks the Named Perils Endorsement checkbox on the APEX screen, if form number IM 7812 is present in Automation Inventory table. 29. Make sure that the enters the details for Named Storm Exclusion section. 30. Ensure that the Bot checks the Excluded Property checkbox on the APEX screen, if form number IM 7856 is present in Automation Inventory table. 31. Ensure that the Bot checks the Sewer Backup Coverage checkbox on the APEX screen, if form number IM7866 is present in Automation Inventory table. 32. Make sure that BOT can enter the information for Tier 1 Counties 33. Ensure that the Bot checks the Windstorm or Hail Exclusion checkbox on the APEX screen, if form number IM7865 is present in Automation Inventory table. 34. Make sure that the Bot enters the details of 'Terms and Conditions' on APEX screen. 35. Examine that Bot selects the save option from the dropdown list. 36. Make sure that Bot clicks on the Continue button of Schedule Property page. 37. Make sure that Bot enters the details in 'Rate' section on premium summary page. 38. Examine whether the bot performs the premium field calculation correctly. 39. Ensure that information is auto populated on the 'policy coverage section' 40. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 41. Examine whether the Bot enters the details on the 'Additional Interest' page. 42. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 43. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 44. Ensure that the Bot selects the values from the dropdown list. 45. Ensure that the Bot will save the entered data in Billing Information section. 46. BOT clicks on the continue button and move to the Premium Summary page because subjectivities are out of the scope. "192"According to the policy ID and the coverage applicable to the policy, Bot selected the Broadcast Equipment & Tower coverage.","1. Ensure that the Bot moves to the applicable coverage (BE-selected coverage) 2. Ensure Bot can enters the details in 'Coverage' section 3. Make sure that the Bot enters the details for Are Building and Structures Covered? Coverage Extensions 4. Validate the functionality of Coverage section on APEX screen. 5. Examine Bot enters the value for 'Any One Occurrence' 6. Examine Bot enters the value for 'Each Separate 12 Month Period' 7. Examine Bot enters the value for 'Earthquake Coverage' 8. Examine Bot enters the value for 'Flood Coverage' 9. Examine Bot enters the value for 'Deductible Amount' 10. Make sure if the Bot checks the Multiple Deductible checkbox on the APEX screen if Multiple Deductible checkbox is checked on form number IM441-1055 06 08. 11. Make sure if the Bot checks the Split Deductible Endorsement checkbox on the APEX screen if Split Deductible Endorsement checkbox is checked on form number IM 7870 08 10. 12. Examine Bot enters the value for 'Valuation' 13. Examine Bot enters the value for 'Coinsurance' 14. Make sure that Bot enters the details for 'INCOME COVERAGE PART' on APEX screen. 15. Make sure that the Bot enters the details for Income Coverage Extensions 16. Ensure that BOT can enter the details for Supplemental Income Coverages 17. Examine that the Bot enters the value for Earthquake Coverage 18. Ensure that the Bot enters the details for the Flood Coverage section on APEX screen. 19. Ensure that the Bot enters the details for the Sewer Backup Coverage section on APEX screen. 20. Ensure that the Bot checks the Income Coverage Waiting Period checkbox on the APEX screen only if the form number IM 7606 05 07 is present in the Automation Inventory table. 21. Ensure that the Bot checks the Equipment Breakdown checkbox on the APEX screen, if form number IM441 1468 03 16 is present in Automation Inventory table. 22. Ensure that the Bot checks the Fire Department Service Charge checkbox on the APEX screen if form number IM 7852 04 04 is present in Automation Inventory table. 23. Ensure that the Bot checks the Property Excluded checkbox on the APEX screen, if form number IM 7856 04 04 is present in Automation Inventory table. 24. Ensure that the Bot checks the Limited Theft Coverage - Excludes theft from an unattended car or unlocked building checkbox on the APEX screen, if form number IM 7858 05 04 is present in Automation Inventory table. 25. Ensure that the Bot checks the Limited Fungus Coverage Endorsement checkbox on the APEX screen, if form number IM 7861 08 11 is present in Automation Inventory table. 26. Ensure that the Bot checks the Named Storm Deductible checkbox on the APEX screen, if form number IM 7869 02 09 is present in Automation Inventory table. 27. Ensure that the Bot checks the Protective Safeguards checkbox on the APEX screen, if form number IM441-1036 01 08 is present in Automation Inventory table. 28. Ensure that the Bot checks the Earth and Flood Limitation checkbox on the APEX screen, if form number IM441-1050 05 15 is present in Automation Inventory table. 29. Make sure that Bot selects the applicable territories checkbox on APEX screen. 30. Examine that Bot selects the save option from the dropdown list. 31. Make sure Bot clicks on the 'Continue' button of Broadcast Equipment & Tower page. 32. Validate the functionality of the Continue button 33. Ensure if the Bot enters the details in 'Rate' section on premium summary page. 34. Ensure that information is auto populated on the 'policy coverage section' 35. Make sure that Bot enters the details for 'Rating' section on Premium Summary page. 36. Examine whether the Bot enters the details on the Additional Interest page. 37. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 38. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 39. Ensure that the Bot selects the values from the dropdown fields. 40. Ensure that the Bot will save the entered data in Billing Information section. 41. Make sure that Bot selects the 'coverage provided only in the territory' 42. Make sure that Bot selects the 'coverage NOT provided for the territory' 43. Make sure that Bot enters the required details after selecting the 'coverage NOT provided for the territory' checkbox. 44. Make sure that Bot enters the required details after selecting the 'Coverage Provided only in the Special Flood Hazard Areas' checkbox. 45. Examine that Bot enters the details of 'Terms and Conditions' 46. Examine that Bot performs the premium field calculation correctly. "193" According to the policy ID and the coverage applicable to the policy, Bot selected the Electronic Data Processing coverage.","1. Ensure that the Bot moves to the applicable coverage (EP-selected coverage) 2. Make sure that Bot enters the details of On-Site Server section on APEX screen. 3. Make sure that Bot enters the details of On-Site Server Coverage Under Hardware and Software on APEX screen. 4. Make sure that Bot enters the details of Off-Site Server on APEX screen. 5. Ensure that Bot enters the details of Equipment Coverage section. 6. Examine that Bot enters the details for Supplemental Coverages section. 7. Examine that Bot enters the details for Virus and Hacking Coverage section. 8. Examine whether the bot enters the value for Deductible correctly on the APEX screen. 9. Examine whether the bot enters the value for Coinsurance correctly on the APEX screen.. 10. Make sure that the Bot enters the details for Coverage Options 11. Make sure that Bot checks the Upgrade Value Endorsement checkbox on APEX screen, if form number IM 7214 05 01 is present in Automation Inventory table. 12. Make sure that Bot checks the Interruption of Web Site checkbox on APEX screen, if form number IM 7237 10 02 is present in Automation Inventory table. 13. Make Sure that BOT can enter the information for Hardware and Software Exclusion Endorsement. 14. Make sure that Bot checks the Electrical And Power Supply Disturbance Limitation checkbox on APEX screen, if form number IM 7223 10 02 is present in Automation Inventory table. 15. Make sure that Bot checks the Incompatible Hardware And Media checkbox on APEX screen, if form number IM 7224 05 01 is present in Automation Inventory table. 16. Ensure that BOT can enter the information for Foreign Transit And Location Coverage 17. Make sure that Bot checks the Production Equipment Exclusion checkbox on APEX screen, if form number IM 7233 05 01 is present in Automation Inventory table. 18. Make sure that Bot checks the Calendar Date or Time Failure Exclusion checkbox on APEX screen, if form number IM 7234 05 01 is present in Automation Inventory table. 19. Make Sure that BOT can enter the information for Earthquake, Flood And Sewer Backup Schedule. 20. Make sure that Bot checks the Earth and Flood Limitation checkbox on APEX screen, if form number IM441-1050 05 is present in Automation Inventory table. 21. Make sure that Bot checks the Fire Department Service charge checkbox on APEX screen if form number IM7852 04 04 is present in Automation Inventory table. 22. Make sure that Bot checks the Protective Safeguards checkbox on APEX screen if form number IM441-1036 01 08 is present in Automation Inventory table. 23. Make sure that Bot checks the Limited Theft Coverage checkbox on APEX screen if form number IM 7858 05 04 is present in Automation Inventory table. 24. Make sure that Bot checks the Limited Fungus Coverage Endorsement checkbox on APEX screen if form number IM 7861 08 11 is present in Automation Inventory table. 25. Make sure that Bot checks the Named Storm Exclusion checkbox on APEX screen if form number IM441-1036 01 08 is present in Automation Inventory table. 26. Make sure that Bot checks the Named Storm Deductible checkbox on APEX screen if form number IM MAN00113 09 20 is present in Automation Inventory table. 27. Make sure that Bot checks the Multiple Deductible checkbox on APEX screen if form number IM441-1055 06 08 is present in Automation Inventory table. 28. Make sure that Bot checks the Split Deductible Endorsement checkbox on APEX screen if form number IM441-1485 06 17 is present in Automation Inventory table. 29. Make sure that Bot checks the Property Excluded checkbox on APEX screen if form number IM 7856 04 04 is present in Automation Inventory table. 30. Ensure that the Bot enters the details of 'Terms and Conditions' on APEX screen. 31. Examine that Bot selects the save option from the dropdown list. 32. Ensure that Bot clicks on 'Continue' button of Electronics Data Process page. 33. Ensure that Bot enters the details in 'Rate' section on premium summary page. 34. Examine Bot performs the premium field calculation correctly. 35. Ensure that information is auto populated on the 'policy coverage section' 36. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 37. Examine whether the Bot enters the details on the 'Additional Interest' page. 38. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 39. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 40. Ensure that the Bot selects the values from the dropdown list. 41. Ensure that the Bot will save the entered data in Billing Information section. 42. BOT clicks on the continue button and move to the Premium Summary page because subjectivities are out of the scope. "194" According to the policy ID and the coverage applicable to the policy, Bot selected the Jewelers Block coverage.","1. Ensure that the Bot moves to the applicable coverage (JB-selected coverage) 2. Make sure that Bot checks the Does this require an NTP checkbox on APEX screen. 3. Make sure that Bot checks the Is the Business Retail or Wholesale checkbox on APEX screen. 4. Ensure that the Bot enters the details of Covered Property at the Premises of a Dealer or Processor in the Jewelry Trade section. 5. Make sure that Bot enters the details for Coverage Extensions section. 6. Make sure that Bot enters the details for Supplemental Coverages section. 7. Ensure that if form number 441-0163 is on the policy, the bot selects the 'Additional Employees' checkbox on the APEX screen. 8. Ensure that if form number 441-0139 is on the policy, the bot selects the 'Bonus Incentive Agreement' checkbox on the APEX screen. 9. Ensure that if form number 441-0141 is on the policy, the bot selects the 'Bonus Incentive Adjustment No Claims' checkbox on the APEX screen. 10. Ensure that if form number IM441-1211 is on the policy, the bot selects the 'Jeweller's Protection Broadening Endorsement' checkbox on the APEX screen. 11. Ensure that if form number IM441-1141 is on the policy, the bot selects the 'Hotel Motel Restriction' checkbox on the APEX screen. 12. Ensure that if form number 441-0191 is on the policy, the bot selects the 'Hurricane Warning Condition' checkbox on the APEX screen. 13. Ensure that if form number 441-0171 is on the policy, the bot selects the 'Joint Venture Merchandise' checkbox on the APEX screen. 14. Ensure that if form number IM441-1210 is on the policy, the bot selects the 'Private Dwelling Restriction' checkbox on the APEX screen. 15. Ensure that if form number IM441-1200 is on the policy, the bot selects the 'Valuation Options Endorsement' checkbox on the APEX screen. 16. Ensure that if form number 441-0199 is on the policy, the bot selects the 'Wind Exclusion Endorsement' checkbox on the APEX screen. 17. Ensure that if form number IM441-1214 is on the policy, the bot selects the 'Employee Dishonesty Coverage and Limit' checkbox on the APEX screen. 18. Ensure that BOT can enter the information for Common Carrier Endorsement 19. Ensure that if form number IM 7807 is on the policy, the bot selects the 'Earthquake Coverage Provided' checkbox on the APEX screen. 20. Ensure that if form number IM 7807 is on the policy, the bot selects the 'Flood Coverage Provided' checkbox on the APEX screen. 21. Ensure that if form number IM441-1199 is on the policy, the bot selects the 'Foreign Trade Show' checkbox on the APEX screen. 22. Ensure that if form number IM441-1146 is on the policy, the bot selects the 'Increased Off Premises Limit' checkbox on the APEX screen. 23. Ensure that if form number 441-0138 is on the policy, the bot selects the 'Loss Payee Endorsement' checkbox on the APEX screen. 24. Ensure that if form number IM441-1152 is on the policy, the bot selects the 'Property While Being Worn - Named Individuals Endorsement' checkbox on the APEX screen. 25. Ensure that if form number IM441-1202 is on the policy, the bot selects the 'Specific Date and Off Premise Limit for Individual' checkbox on the APEX screen. 26. Ensure that if form number IM441-1144 is on the policy, the bot selects the 'Trade Show Coverage Endorsement for Individual' checkbox on the APEX screen. 27. Ensure that if form number IM441-1143 is on the policy, the bot selects the 'Unattended Automobile for Individual' checkbox on the APEX screen. 28. Ensure that if form number IM441-1198 is on the policy, the bot selects the 'Multiple Deductible' checkbox on the APEX screen. 29. Ensure that if form number IM441 1036 is on the policy, the bot selects the 'Protective Safeguards' checkbox on the APEX screen. 30. Make sure that the Bot enters the details of 'Terms and Conditions' 31. Examine that Bot selects the save option from the dropdown list. 32. Make sure that Bot clicks on 'Continue' button of Jeweller's Block' page. 33. Ensure that Bot enters the details in 'rate section' on premium summary page. 34. Examine Bot performs the premium field calculation correctly. 35. Ensure that information is auto populated on the 'policy coverage section' 36. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 37. Examine whether the Bot enters the details on the 'Additional Interest' page. 38. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 39. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 40. Ensure that the Bot selects the values from the dropdown list. 41. Ensure that the Bot will save the entered data in Billing Information section. 42. Ensure that the Bot selects the 'Billing Details' from the dropdown. 43. Ensure that the Bot enters the details for 'Property in Transit' section. 44. BOT clicks on the continue button and move to the Premium Summary page because subjectivities are out of the scope. "195"According to the policy ID and the coverage applicable to the policy, Bot selected the Motor Truck Cargo coverage.","1. Ensure that the Bot moves to the applicable coverage (MT-selected coverage) 2. Make sure that Bot selects the Does this require an NTP checkbox on APEX screen. 3. Examine whether the bot enters the value for Limit of Insurance correctly on APEX screen. 4. Examine whether the bot enters the value for Property In Transit correctly. 5. Examine whether the bot enters the value for Unscheduled Terminal Limit. 6. Examine whether the bot enters the value for Unscheduled Terminal Time Period 7. Make sure that Bot selects the Schedule on File checkbox on APEX screen. 8. Examine whether the Bot enters the value for Schedule on File Dated: on APEX screen. 9. Make sure that Bot enters the details for 'Additional Coverages' on APEX screen. 10. Ensure that Bot enters the details for Deductible section on APEX screen. 11. Ensure that Bot enters the details for Refrigeration Breakdown. 12. Make sure that Bot selects the Refer to Multiple Deductible Schedule Endorsement checkbox on APEX screen. 13. Make sure that Bot enter the details for Reporting section on APEX screen. 14. Make sure that Bot checks the 'Adulterated Food Additional Coverage Endorsement' checkbox on APEX screen if form number IM441-0258 01 20 is present in Automation Inventory table. 15. Make sure that Bot checks the 'Designated Shipper Endorsement' checkbox on APEX screen, if form number IM441-0260 01 20 is present in Automation Inventory table. 16. Make sure that Bot checks the Additional Property Not Covered Endorsement checkbox on APEX screen, if form number IM441-0263 01 20 is present in Automation Inventory table. 17. Make sure that Bot checks the Additional Refrigeration Breakdown Coverage checkbox on APEX screen, if form number IM441-0264 01 20 is present in Automation Inventory table. 18. Make sure that Bot checks the Named Driver Exclusion checkbox on APEX screen, if form number IM441-0265 01 20 is present in Automation Inventory table. 19. Make sure that Bot checks the Additional Named Drivers checkbox on APEX screen, if form number IM441-0265 01 20 is present in Automation Inventory table. 20. Make sure that Bot checks the Non-Owned Trailer Coverage Endorsement checkbox on APEX screen, if form number IM441-0266 01 20 is present in Automation Inventory table. 21. Make sure that Bot checks the Temperature Control Endorsement checkbox on APEX screen, if form number IM441-0268 01 20 is present in Automation Inventory table. 22. Make sure that Bot checks the Scheduled Vehicle Endorsement checkbox on APEX screen, if form number IM441-0258 01 20 is present in Automation Inventory table. 23. Make sure that Bot checks the 'Scheduled Vehicle Endorsement - Limit Per Vehicle' checkbox on APEX screen, if form number IM441-0267 01 20 is present in Automation Inventory table. 24. Verify if the Bot checks the Covered Property Endorsement checkbox on APEX screen, if form number IM441-0259 01 20 is present in Automation Inventory table. 25. Make sure that Bot checks the Earthquake Exclusion checkbox on APEX screen, if form number IM441-0258 01 20 is present in Automation Inventory table. 26. Make sure that Bot checks the Flood Exclusion checkbox on APEX screen, if form number IM441 0262 01 20 is present in Automation Inventory table. 27. Make sure that Bot checks the Split Deductible checkbox on APEX screen, if form number IM441-0258 01 20 is present in Automation Inventory table. 28. Make sure that the Bot enters the details for MC 2414C Endorsement for Motor Common Carrier Policies - This endorsement is for Federal Filing - and should only be used for hazardous material hauling. 29. Make sure that the Bot enters the details for MC 2444 Uniform Motor Carrier Cargo Ins Endorsement. 30. Ensure that the Bot enters the details of 'Terms and Conditions' on APEX screen. 31. Examine Bot selects the save option from the dropdown list. 32. Make sure that Bot clicks on 'Continue' button of Motor truck cargo page. 33. Ensure that Bot enters the details in 'rate section' on premium summary page. 34. Examine Bot performs the premium field calculation correctly. 35. Ensure that information is auto populated on the 'policy coverage section' 36. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 37. Examine whether the Bot enters the details on the 'Additional Interest' page. 38. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 39. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 40. Ensure that the Bot selects the values from the dropdown list. 41. Ensure that the Bot will save the entered data in Billing Information section. 42. Ensure that the Bot selects the 'Billing Details' from the dropdown. 43. BOT clicks on the continue button and move to the Premium Summary page because subjectivities are out of the scope. "196"According to the policy ID and the coverage applicable to the policy, Bot selected the Builders Risk Reporting coverage.","1. Ensure that the Bot moves to the applicable coverage (BR-selected coverage) 2. Ensure that the Bot enters the details for Project Description on APEX screen. 3. Examine that the Bot can select the project type from dropdown list. 4. Examine that the Bot enters details in 'Property Not Subject To Reporting' section 5. Examine that Bot enters the details of 'Limits of Insurance' section 6. Confirm that Bot can select the 'Delay In Completion Coverage' checkbox. 7. Confirm that Bot can select the 'Equipment Breakdown Coverage' checkbox. 8. Check Bot is able to select the 'Permission To Occupy' checkbox on APEX screen. 9. Make sure Bot checks the Flood Coverage checkbox on the APEX screen if Flood Coverage checkbox is checked on form number IM441-1374/ IM441-1373. 10. Ensure that BOT can enter the information for Permission To Occupy. 11. Make Sure that BOT can enter the information for Earth Movement Coverage . 12. Make sure that Bot enters the details for 'Additional Coverages'. 13. Examine that Bot enters the details of 'Per Occurrence Deductible' 14. Ensure that the Bot can enter the details of Multiple Deductible Endorsement. 15. Ensure that the Bot can enter the details of Split Deductible . 16. Make sure that Bot checks the Deductible Buy Back checkbox on the APEX screen if form number IM441-1392 is present in Automation Inventory table. 17. Make sure that Bot checks the Furnishings Coverage Endorsement checkbox on the APEX screen if form number IM441-1423 is present in Automation Inventory table. 18. Make sure that Bot checks the Green Coverage Endorsement checkbox on the APEX screen if form number IM441-1349 is present in Automation Inventory table. 19. Make sure that Bot checks the Limitation on Coverage for Roof Surface checkbox on the APEX screen if form number IM441-1393 is present in Automation Inventory table. 20. Ensure that BOT can enter the information for 1. Paragraph A - Actual Cash Value at time of Loss Applies. 21. Make Sure that BOT can enter the information for 2. Paragraph B - We will not pay for cosmetic damage caused by wind/hail. 22. Make sure that Bot checks the Hail Deductible checkbox on the APEX screen, if form number IM441-1370 is present in Automation Inventory table. 23. Make sure that Bot checks the Hail Exclusion - Scheduled Locations checkbox on the APEX screen if form number IM441-1369 is present in Automation Inventory table. 24. Make sure that the Bot enters the details for Named Storm Exclusion. 25. Make sure that Bot checks the Named Storm Deductible checkbox on the APEX screen if form number IM441-1371 is present in Automation Inventory table. 26. Make sure that Bot checks the Named Storm Exclusion Scheduled Locations checkbox on the APEX screen if form number M441-1367, IM441-1366 is present in Automation Inventory table. 27. Make sure that Bot checks the Water Damage Special Deductible checkbox on the APEX screen if form number IM441-1609 is present in Automation Inventory table. 28. Make sure that Bot checks the Windstorm Exclusions checkbox on the APEX screen if form number IM441-1368 is present in Automation Inventory table. 29. Make sure that Bot checks the Windstorm Hail Exclusion Scheduled Locations checkbox on the APEX screen if form number IM441-1357 is present in Automation Inventory table. 30. Make sure that Bot checks the Windstorm Hail Deductible - Location checkbox on the APEX screen if form number IM441-1363 is present in Automation Inventory table. 31. Make Sure that BOT can enter the information for Tier 1 Counties Exclusion. 32. Make sure that Bot checks the Protective Safeguards checkbox on the APEX screen if form number IM441-1365 is present in Automation Inventory table. 33. Examine the Terms and Conditions functionality of the text area. 34. Examine that Bot selects the save option from the dropdown list. 35. Make sure that Bot clicks on Continue button on Builder Risk page 36. Ensure that the Bot enters the details in 'Rate' section on premium summary page. 37. Examine that Bot performs the premium field calculation correctly. 38. Ensure that information is auto populated on the 'policy coverage section' 39. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 40. Examine whether the Bot enters the details on the Additional Interest page. 41. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 42. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 43. Ensure that the Bot selects the values from the dropdown fields. 44. Ensure that the Bot will save the entered data in Billing Information section. 45. Ensure that the Bot selects the 'Billing Details' from the dropdown. 46. BOT clicks on the continue button and move to the Premium Summary page because subjectivities are out of the scope. "197"According to the policy ID and the coverage applicable to the policy, Bot selected the Fine Arts Floater coverage.","1. Ensure that the Bot moves to the applicable coverage (FF-selected coverage) 2. Ensure that BOT can enter the information for Does this require an NTP . 3. Ensure that the Bot enter details for 'Catastrophe Limit' section (Mandatory fields). 4. Examine that the Bot enters the value for Emergency Removal on APEX screen. 5. Examine that the Bot enters the value for Emergency Removal Expenses on APEX screen. 6. Examine that the Bot enters the value for Emergency Removal Expenses Limit on APEX screen. 7. Examine that the Bot enters the value for Newly Acquired Art (% of Catastrophe Limit) on APEX screen. 8. Examine that the Bot enters the value for Off-Premises Coverage on APEX screen. 9. Examine that the Bot enters the value for Property Used To Display Or Protect Art on APEX screen. 10. Examine that the Bot enters the value for Transit Coverage on APEX screen. 11. Ensure that the Bot enters the details for Deductible. 12. Ensure that the Bot enters the information for Multiple Deductible if form number IM441-1055 06 08 is present in the Automation Inventory table. 13. Make sure that Bot checks the Earthquake Limitation Endorsement checkbox on the APEX screen, if form number IM 7410 08 11 is present in Automation Inventory table. 14. Make sure that Bot checks the Flood Limitation Endorsement checkbox on the APEX screen, if form number IM 7411 08 11 is present in Automation Inventory table. 15. Make sure that Bot checks the Sewer Backup Limitation checkbox on the APEX screen, if form number IM 7415 08 11 is present in Automation Inventory table. 16. Make sure that Bot checks the Breakage Exclusion checkbox on the APEX screen, if form number IM 7417 08 11 is present in Automation Inventory table. 17. Make sure that Bot enters the Breakage Limit on the APEX screen if Breakage Limitation checkbox is checked on form number IM 7418 08 11. 18. Make sure that Bot checks the Fraud and Deceit Limitation checkbox on the APEX screen, if form number IM 7419 08 11 is present in Automation Inventory table. 19. Make sure that Bot checks the Storage Location Coverage checkbox on the APEX screen, if form number IM 7420 is present in Automation Inventory table. 20. Make sure that Bot checks the Dishonest Acts Exclusion checkbox on the APEX screen, if form number IM 7423 08 11 is present in Automation Inventory table. 21. Make sure that Bot checks the Declared Total Loss Endorsement checkbox on the APEX screen, if form number IM 7425 08 11 is present in Automation Inventory table. 22. Verify if the Bot checks the Fire Department Service Charge Endorsement checkbox on the APEX screen, if form number IM 7852 04 04 is present in Automation Inventory table. 23. Make sure that Bot checks the Property Excluded checkbox on the APEX screen, if form number IM 7852 04 04 is present in Automation Inventory table. 24. Make sure that Bot checks the Limited Fungus Coverage Endorsement checkbox on the APEX screen, if form number IM 7861 08 11 is present in Automation Inventory table. 25. Make sure that Bot checks the Named Storm Exclusion checkbox on the APEX screen, if form number IM 7869 02 09 is present in Automation Inventory table. 26. Make sure that Bot checks the Named Storm Deductible checkbox on the APEX screen, if form number IM 7869 02 09 is present in Automation Inventory table. 27. Make sure that Bot checks the Windstorm or Hail Exclusion checkbox on the APEX screen, if form number IM 7665 is present in Automation Inventory table. 28. Make sure that Bot checks the Split Deductible Endorsement checkbox on the APEX screen, if form number IM 7870 08 10 is present in Automation Inventory table. 29. Make sure that Bot checks the Protective Safeguards checkbox on the APEX screen, if form number IM441 1036 01 08 is present in Automation Inventory table. 30. Make sure that Bot enters the details of 'Terms and Conditions' on APEX screen. 31. Examine that Bot selects the save option from the dropdown list. 32. Make sure that Bot clicks on Continue button on Fine Arts Floater page. 33. Ensure that the Bot enters the details in 'rate' on premium summary page. 34. Ensure that Bot performs the premium field calculation correctly. 35. Examine that information is auto populated on the 'policy coverage section' 36. Make sure that the Bot enters the details for 'Rating' section on Premium Summary page. 37. Examine whether the Bot enters the details on the Additional Interest page. 38. Make sure that Bot clicks on continue button of 'Manuscripts Forms' page. 39. Ensure that the Bot is able to select the Bill to Name and Address check box on Billing information page. 40. Ensure that the Bot selects the values from the dropdown fields. 41. Ensure that the Bot will save the entered data in Billing Information section. 42. Ensure that the Bot selects the 'Billing Details' from the dropdown. 43. BOT clicks on the continue button and move to the Premium Summary page because subjectivities are out of the scope. "198The login module should let the admin and user log into the system to perform certain actions.,"1. Check the RNT Service Portfolio's login functioning with an incorrect username and password. 2. Ensure that the user is unable to log in and access the application's features and functionality on entering invalid password details. 3. Confirm that the login is successful and the user is granted access to the application's features and functionality on entering valid username and password. 4. The password should be visible in plain text when the visibility is on eye icon 5. Confirm the eye icon should change to a closed eye icon, indicating that password visibility is off or on click hides the password text. 6. Verify the Reset functionality of Login. 7. Evaluate the functionality of the 'Client Login' hyperlink in the RNT portfolio application. 8. Assess the functionality of the 'Get OTP' button. 9. Validate the behavior of the OTP field, including restrictions such as accepting only numeric input and allowing a maximum of 4 digits. 10. Evaluate the functionality of the Resend OTP button, ensuring that the user receives a new OTP on the provided email address. 11. Onclick 'Reset' button ensure that the entered data in the email and OTP fields gets cleared. 12. Examine the functionality of the Login button, which allows the user to log in as a client by entering registered email and received OTP. 13. Evaluate the visibility and functionality of the Rnt login hyperlink on the client login panel, which enables users to switch to the normal RNT login. 14. Examine the functionality of the eye icon in the client login, which allows the user to view the entered OTP upon clicking. 15. Confirm whether if an invalid OTP is entered, the system displays an error message indicating the incorrect OTP and prevent the user from accessing their account. 16. Examine the client login functionality using a valid OTP to ensure that users can log in to their accounts successfully 17. Ensure 'Email' field of client login doesn't accept email without '@' & '.' characters. 18. Verify 'Reset' and 'Login' button text on RNT login. 19. Verify 'Reset' and 'Login' button text on Client login panel. 20. Evaluate the login button functionality when a client enters only their email without providing the OTP and directly clicks on the login button. Ensure that the system displays an appropriate error message indicating that both the email and OTP are requ... 21. Examine the functionality of the Enter button when the user enters their email and OTP and hits it. Verify that the system successfully logs in the user as a client. "199"Log in for the admin will display the profile image and the name of the admin, whereas for the user login the user’s name and login avatar will reflect.","1. During the login process, ensure that the text is displayed correctly, allowing users to view the comprehensive description of the services offered by the RNT Service Portfolio. 2. Ensure the visibility of each service card contain relevant and accurate information, including a clear title and descriptive details about the respective service. 3. To examine the services cards displayed and ensure their accessibility and relevance, including comprehensive details such as project names, domain categories, tool descriptions, or technology names. 4. To examine the project cards displayed and ensure their accessibility and relevance, including comprehensive details such as services names, domain categories, tool descriptions, or technology names. 5. To examine the domains cards displayed and ensure their accessibility and relevance, including comprehensive details such as project names, service categories, tool descriptions, or technology names. 6. To examine the tool cards displayed and ensure their accessibility and relevance, including comprehensive details such as project names, domain categories, service descriptions, or technology names. 7. To examine the technologies cards displayed and ensure their accessibility and relevance, including comprehensive details such as project names, domain categories, tool descriptions and service details 8. Make sure that the appropriate project count is shown on the Projects card. 9. Validate that the Domains card correctly shows the count of domains. 10. Ensure that the Tools card accurately represents the total count of tools. 11. Confirm that the Technologies card displays the correct number of technologies in accordance with the available data. 12. Verify the visibility of project count on each service card. "200"The admin can add the new service by selecting this feature. On the click, a pop-up screen will display containing some required fields, by filling these fields the admin can add a new service.","1. To ensure that the admin has access to various services and can make changes to existing services or add new services within the system or availability of functionalities to do the same. 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown. 3. Check whether the displayed data is filtered based on the entered text, showing only the relevant information. 4. To verify the functionality of the Add Service button, ensuring that it displays a popup with the necessary fields to add a new service. 5. Onclick the 'Add Service' button should trigger the display of a pop-up window which contain a form with fields for specifying the name, description, and other required details of the service to be added 6. Ensure on clicking the Upload Icon button allows the user to select an icon file from their local system. 7. To verify the functionality of the 'Add' button in the Add Service for when all required details are entered without uploading icon. 8. To verify the functionality of the 'Add' button in the Add Service form, ensuring that it successfully adds the service to the system when all required details are entered. 9. To ensure the functionality of the Cancel button in the Add Service pop-up, ensuring that it cancels the process of adding a new service and closes the pop-up without saving any changes. 10. Examine the services name listed in the Service Name column are clickable. 11. Verify the Next pagination button. 12. Verify the Previous pagination button. "201 Admin will view the different services with detailed information.,"1. Verify that clicking on the View button displays the detailed information or overview of the service. 2. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. "202 Admin can edit the existing service by adding or removing the description.,"1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of services. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the service details and exit the edit mode. "203 Admin can remove service by selecting this action.,"1. To validate the functionality of the Delete button for services, allowing the deletion of existing services from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. "204 Admin can add the new domain by selecting this button.,"1. To ensure that the admin has access to various domains and can make changes to existing domain or add new domain within the system or availability of functionalities to do the same 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown 3. Check whether the displayed data is filtered based on the entered text, showing only the relevant information. 4. To verify the functionality of the Add Domain button, ensuring that it displays a popup with the necessary fields to add a new Domain 5. Onclick the 'Add Domain' button should trigger the display of a pop-up window which contain a form with fields for specifying the name, description, and other required details of the domain to be added. 6. Ensure on clicking the Upload Icon button allows the user to select an icon file from their local system. 7. To verify the functionality of the 'Add' button in the Add Domain for when all required details are entered without uploading icon. 8. To verify the functionality of the 'Add' button in the Add Domain form, ensuring that it successfully adds the domain to the system when all required details are entered. 9. To ensure the functionality of the Cancel button in the Add Domain pop-up, ensuring that it cancels the process of adding a new domain and closes the pop-up without saving any changes. 10. Examine the Domain name listed in the Domain Name column are clickable. 11. Verify the Next pagination button. 12. Verify the Previous pagination button. "205 Admin can able to see the different domains with detailed information.,"1. Verify that clicking on the View button displays the detailed information or overview of the domain. 2. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. "206Admin can edit the existing domain by updating the description of the domain.,"1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of domains. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the domain details and exit the edit mode. "207 Admin can delete a domain by selecting this action.,"1. To validate the functionality of the Delete button for domains, allowing the deletion of existing domain from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. "208 Only the admin can add the new project by adding all the required information.,"1. To ensure that the admin has access to various projects and can make changes to existing services or add new project within the system or availability of functionalities to do the same 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown 3. To verify the search functionality that filters displayed data based on the entered text, presenting only relevant information 4. To verify the functionality of the Add Project button, ensuring that it displays a popup with the necessary fields to add a new project. 5. To evaluate the functionality of the Add button in the Add Projects feature when all the required fields are specified or entered. 6. To analyze the behavior of the Add button in the Add Projects feature when the user intentionally leaves certain required fields blank or omits entering any data 7. Verify the Cancel button functionality of the Add Projects. "209Admin can see the different projects with detailed information.,"1. Verify that clicking on the View button displays the detailed information or overview of the project. 2. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. "210Admin can edit the existing project by updating the information of the project.,"1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of project. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the project details and exit the edit mode. "211 Admin can delete a project by selecting this action if the organization is no longer working on the project.,"1. To validate the functionality of the Delete button for projects, allowing the deletion of existing project from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. "212 User can view the projects based on the categories from the modules they are in.,"1. To ensure that the projects listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each project 2. Verify the Next pagination button. 3. Verify the Previous pagination button. "213 Only the admin can add the new tool by adding all the required information.,"1. To ensure that the admin has access to various tools and can make changes to existing tool or add new tool within the system or availability of functionalities to do the same. 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown 3. To verify the search functionality that filters displayed data based on the entered text, presenting only relevant information 4. To verify the functionality of the Add Tool button, ensuring that it displays a popup with the necessary fields to add a new tool 5. Verify the Add Tools pop-up window. 6. Ensure on clicking the Upload Icon button allows the user to select an icon file from their local system. 7. To verify the functionality of the 'Add' button in the Add Tool for when all required details are entered without uploading icon 8. To evaluate the functionality of the 'Add' button in the Add Tool form, ensuring successful addition of the tool to the system when all the required details are entered 9. To ensure the functionality of the Cancel button in the Add Tool pop-up, ensuring that it cancels the process of adding a new tool and closes the pop-up without saving any changes 10. To confirm whether the Tools name listed in the Tools Name column are clickable. 11. Verify the Next pagination button. 12. Verify the Previous pagination button. "214Admin can see the different tools with detailed information.,"1. Verify that clicking on the View button displays the detailed information or overview of the tool. 2. Make sure the functionality of the Back button in the View action, closes the view mode and returns the user to the previous page or section. "215 Admin can edit the existing tool by updating the information such as the version or description of the tool.,"1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of tools. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the tool details and exit the edit mode. "216Admin can delete a tool by selecting this action.,"1. To validate the functionality of the Delete button for tools, allowing the deletion of existing tool from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. "217 Only the admin can add the new technology by adding the required information.,"1. To ensure that the admin has access to various technologies and can make changes to existing technology or add new technology within the system or availability of functionalities to do the same. 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown. 3. Check whether the displayed data is filtered based on the entered text, showing only the relevant information. 4. To verify the functionality of the Add Technology button, ensuring that it displays a popup with the necessary fields to add a new technology. 5. Onclick the 'Add Technology' button should trigger the display of a pop-up window which contain a form with fields for specifying the name, description, and other required details of the technology to be added 6. Ensure on clicking the Upload Icon button allows the user to select an icon file from their local system. 7. To verify the functionality of the 'Add' button in the Add Technology for when all required details are entered without uploading icon. 8. To verify the functionality of the 'Add' button in the Add Technology form, ensuring that it successfully adds the technology to the system when all required details are entered. 9. To ensure the functionality of the Cancel button in the Add Technology pop-up, ensuring that it cancels the process of adding a new technology and closes the pop-up without saving any changes. 10. Confirm whether the Technology name listed in the Technology Name column are clickable. 11. Verify the Next pagination button. 12. Verify the Previous pagination button. "218Admin can see the different technologies with detailed information.,"1. Verify that clicking on the View button displays the detailed information or overview of the technology. 2. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. "219Admin can view the list of clients.,"1. To ensure that the admin has access to various clients and can make changes to existing technology or add new client within the system or availability of functionalities to do the same. 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown. 3. Check whether the displayed data is filtered based on the entered text, showing only the relevant information. 4. Confirm whether the Client name listed in the Client Name column are clickable. 5. Verify the Next pagination button. 6. Verify the Previous pagination button. 7. Verify that clicking on the View button displays the detailed information or overview of the client. 8. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. 9. To verify the functionality of the Add Client button, ensuring that it displays a popup with the necessary fields to add a new client. 10. Onclick the 'Add Client' button should trigger the display of a pop-up window which contain a form with fields for specifying the pseudo name, description, and dropdown for client name to be selected 11. To verify the functionality of the 'Add' button in the Add Client for when any of data for mandatory field is missing. 12. To verify the functionality of the 'Add' button in the Add Client form, ensuring that it successfully adds the client to the system when all required details are entered. 13. To ensure the functionality of the Cancel button in the Add Client pop-up, ensuring that it cancels the process of adding a new client and closes the pop-up without saving any changes. "220 Admin can edit the client’s description and save it.,"1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of client. 2. Examine the ability to modify client details such as pseudo name and description 3. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the client details and exit the edit mode. 4. Examine the Update button functionality of the Edit action which on click saves the edited details for client. "221Only the admin can add the new SPOC name with details.,"1. To ensure that the admin has access to various SPOC and can make changes to existing SPOC or add new SPOC within the system or availability of functionalities to do the same 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown 3. To verify the search functionality that filters displayed data based on the entered text, presenting only relevant information 4. To verify the functionality of the Add SPOC button, ensuring that it displays a popup with the necessary fields to add a new SPOC. 5. To validate the functionality of the Name dropdown field in the Add SPOC form, which allows users to select a name to be added as a (SPOC) in our system 6. To validate the functionality of the Designation dropdown field in the Add SPOC form, which allows users to select a designation for (SPOC) in our system 7. To check the behavior of the Add button in the Add SPOC pop up when incomplete data is entered, to ensure that it functions as expected 8. Confirm the behavior of the Add button in the Add SPOC pop up when all the required data is provided, to ensure that it functions correctly 9. To ensure the functionality of the Cancel button in the Add SPOC pop-up, ensuring that it cancels the process of adding a new SPOC and closes the pop-up without saving any changes. 10. Verify the Next pagination button. 11. Verify the Previous pagination button. 12. Confirm whether the SPOC name listed in the SPOC Name column are clickable 13. Examine the Next pagination button functionality of the selected SPOC. 14. Ensure the functionality of Previous pagination button of the selected SPOC. "222Admin can view the SPOC person details.,"1. Verify that clicking on the View button displays the detailed information or overview of the SPOC. 2. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. "223Admin can edit the SPOC name and the details.,"1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of SPOC. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the SPOC details and exit the edit mode. "224 Admin can delete a SPOC name by selecting this icon.,"1. To validate the functionality of the Delete button for SPOC, allowing the deletion of existing SPOC from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. "225" The business requirement for a Stationery login page may vary depending on the specific needs and goals of the company. However, some common business requirements could apply to a Stationery login page- 1) User Authentication. 2) User Access controls. ...",1. Check login functionality with a valid username and valid password. 2. Check login functionality using an invalid username and a valid password. 3. Check login functionality using an invalid username and a valid password. 4. Check login functionality with valid username and invalid password. 5. Examine the login functionality by keeping the username and password fields left blanks. 226" Admin features submodules such as 1) Stationery, where admin can view the stationery issued and available quantity in the cards, pending requests of the user, Reject and Approve buttons, and Notification icon to see who has requested the stationery in t...","1. Examine the Admins dashboard functionality, which allows the admin to see the submodules on the dashboard page. 2. Examine the notification icon functionality, which shows whether the request has been approved or pending. 3. Examine the functioning of cards that displays the issued and available quantity of stationery and housekeeping items available in the organization. 4. Examine the dashboard's scrolling button for browsing through stationery objects from the left or right side. 5. Examine the functionality of the Approved button in actions where the admin can approve the stationery request raised by user. 6. Check the functionality of Reject button in Actions where Admin can reject the request raised by the user. 7. Examine the Users dashboard functionality, which includes submodules such as cards and issued item data in table form. 8. Examine the functionality of the notification icon, in which the admin may see the request raised by the user and when a new request occurs, a red dot appears on the notification icon. 9. Determine the profile dropdown functionality on dashboard for logout and switch to user profile. 10. Check to see if the stationery tab is clickable and user redirected to the total stationery page. 11. Examine to see if the housekeeping tab is clickable and navigates you to the total housekeeping page. "227"The admin has two submodules under the Stationery Module: stationery and housekeeping. 1) In the Stationery module, the admin can purchase stationery for the organization, add stationery, and view issued stationery in the Graph form. Admin can also down...","1. Examine the functionality of the 'Stationery module' on admin side by which they can purchase or add stationery in the application. 2. Check that the 'Purchase stationery' button is clickable and enter the required information on the purchase stationery page. 3. Make sure that 'Admin' is able to select the 'Stationery Name' from the dropdown list. 4. Test the 'Quantity' field, where admin inputs figures such as 100, 200, etc. 5. Make sure that admin is able to select the 'Purchase date' from the calendar window. 6. Examine the functionality of the Add stationery button and fill out the essential information on the Add New Stationery page. 7. Examine the description field in the add new stationery page, where the admin enters descriptive information about the stationery he is adding. 8. Check the performance of the Export button in order to generate a monthly report of the stationery module by selecting year and month. 9. Examine the functionality of the year dropdown, from which the admin can select the year. 10. Examine the functionality of the month dropdown, from which the admin can choose the month. 11. Examine the 'Stationery module' feature on the User dashboard, where user raise the request for stationery. 12. Ensure that user can raise the request and check that the raised request is displayed on table of 'Stationery' module. 13. Check that the 'stationery name' field dropdown is clickable, and that the user selects the stationery from the list that appears. 14. Examine the 'Required quantity' field, where the user enters quantities such as 100, 200, etc. 15. Ensure that the user can provide the necessary information on the 'Stationery Request' form. The user then click'sthe 'Add to List' button after entering the information. 16. Examine the Edit functionality of the action's column, where the admin can modify the request as needed. 17. Examine the Delete functionality of the action's column, where admin can delete the request that was added to the list. 18. Examine the functionality of the'submit' button, and see if it is clickable after adding a stationery request to the table. 19. Examine the 'Stationery tab' on the Stationery module, which is only accessible to admin. 20. Examine the 'Housekeeping tab' on the Stationery module, which is only accessible to admin. "228Any stationery and housekeeping products that have been purchased and uploaded will have their individual invoice images displayed in the invoice module.,"1. Examine the functionality when an admin clicks on the Invoice module, the Stationery and Housekeeping tab is displayed to the admin. 2. Observe that all fields that are present on the invoice page are properly aligned. "229"Admin users will be able to view products history that have been bought and issued, including how many products have been allocated to employees and how many products have been bought in past days.","1. After clicking on the history tab/module, ensure that the Issued and Purchase history option is displayed on the page. "230User will view the different services with detailed information.,"1. Examine whether the various services are displayed in card format on the services module screen 2. To ensure that the services listed in card format on the webpage are clickable. 3. To ensure that the services listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each service. 4. To confirm that clicking on the Back button properly redirects the user back to the service module screen. "231" Admin can upload for financial year and view from 16 pdf, employee can view and download the form 16.",1. Evaluate the 'Form 16' functionality on the Home module. 2. Confirm the Financial Year dropdown functionality. 3. Determine the 'Go' button functionality for the Financial Year when Form 16 is unavailable. 4. Examine the 'OK' button functionality of the error pop-up. 5. Make sure the 'Go' button functionality for the Financial Year when Form 16 is available. 6. Confirm the 'Download' button functionality. 7. Examine the columns present on the Form 16 dashboard. 8. Evaluate the workability of the Financial Year dropdown menu. 9. Examine the search bar functionality with appropriate search inputs. 10. Ensure the working of show entries dropdown. 11. Test the pagination of the Dashboard tab screen. 12. Determine the functioning of the upload button on the dashboard tab screen. 13. Evaluate the functionality of the 'Upload' button when an admin tries to Upload a file in inappropriate conditions. 232" FNF settlement is known as the full and final settlement. It is a process of calculating different payable dues to an employee who is resigning, retired, or terminated, from an organization. Admin should be able to upload files for employees in FNF sub ...","1. Ensure 'FNF Report' screen contains all the data as per alignment, size, and style. 2. Examine all the columns present on the FNF Report dashboard screen. 3. Evaluate the working of the Choose File button present under the action column. 4. Confirm that the download function works as expected and the file only downloads in PDF format. 5. Ensure that the Action column's upload feature works as per expectations. 6. Confirm the 'view' icon's functionality. 7. Examine the search bar functionality from the 'FNF Report screen' with appropriate search inputs. 8. Ensure the working of show entries dropdown is present on the 'FNF Report' screen. 9. Test the pagination of the 'FNF Report' home screen. 10. Evaluate for navigating on the previous screen admin can use the breadcrumbs present on the 'FNF Report' screen. 11. Confirm only employees who have 'Date Of Departure' displays in the 'FNF Report' screen. "233" Admin user can view team KRA, team self-appraisal and appraise details in chart form.","1. Ensure that the admin is navigated to the admin dashboard after successful login 2. Ensure that on clicking the Dashboard module, Select Year Dropdown must be auto selected for current date and according to date dashboard data must be changed. 3. Make sure that report must be displayed after filling the details in the Select year dropdown, Appraisal type Dropdown, and hits Go button. "234User can be able to view any appraisal done by manager and download appraisal report.,"1. Ensure that the employee user is navigated to the admin dashboard after successful login 2. User unable to view dashboard, since they do not possess access to it 3. On clicking the Dashboard module, Select Year Dropdown will be auto-selected for current date ,according to date dashboard data must be changed. 4. On clicking the Select year dropdown, select Appraisal type Dropdown, and hits Go button "235" Manager can view team KRA, team self-appraisal and appraise details in chart form.","1. Ensure that the manager is navigated to the manager dashboard after successful login 2. Determine whether the manager cannot view the dashboard because they cannot access it. 3. On clicking the Dashboard module, Select Year Dropdown must be auto-selected for current date,according to date dashboard data must be changed. 4. On clicking the Select year dropdown, select Appraisal type Dropdown, and hits Go button "236 This tab should Allow the admin user to appraise any employee.Should be accessible to admin only. Admin can appraise and view previous appraisal.Screen should have 2 dashboards - Approve KRA's & Appraise,"1. On clicking on theAppraise module, Employee list must be shown in Approve KRA'S tab with KRA approve status and Employeelist must be shown in Appraise tab with appraise status. 2. Check user is able to navigate to next page, make sure the next indicator (>>) is active and make sure it is disabled for last page 3. Check user is able to navigate on previous page, make sure the previous indicator (<<) is active and make sure it is disabled for first page. 4. For the employee table, make sure the search box is functional. 5. Check KRA's status of employee table for approve KRA tab. 6. Check the functionality of submitted button which is present in the KRA's status. 7. Ensure that the approved KRA form of the employee must be displayed after clicking on the approved button KRA's status. 8. On clicking on the Appraise tab in the appraise module, the Employee list must be shown in the Appraise tab with appraise status. 9. Check user is able to navigate to next page, make sure the next indicator (>>) is active and make sure it is disabled for last page. 10. Check user is able to navigate on previous page, make sure the previous indicator (<<) is active and make sure it is disabled for first page. 11. For the employee table, make sure the search box is functional. 12. Check appraise status of employee table for appraise tab. 13. Check the functionality of appraise button which is present in the appraise status. 14. Check the functionality of complete button which is present in the appraise status. "237"KRA Key responsibility area tab should be accessible by Employee as well as Admin.Where,User can fill KRA for internship, annual, and Project end. and Admin can view and approve the KRA.",1. Examine the KRA's module and its associated functionalities. 2. Examine for innovation in KRA information fields. 3. Evaluate the execution form fields of KRA information. 4. Validate the KRA information areas on the team form. 5. Check the win form sections for KRA information. 6. Examine admin can be able to upload the excel file of employee's KRA's 7. Confirm the sample export file is downloading while clicks on the sample export file button. 238User should be able to do self-appraisal.,1. Determine the self-appraisal module for the approved employee. 2. Examine the Self Appraisal module and its associated functionalities. 3. Check the KRA information for Self appraisal tab 4. Examine innovation form fields of self-appraisal information 5. Examine the execute form fields of self-appraisal information 6. Check the 'win' form fields of self-appraisal information 7. Ensure the team form fields of self-appraisal information 8. Examine the overall assessment form fields of self-appraisal information 239Admin user should be able to add rating criteria used for appraisal purpose.,"1. Make sure that by clicking on the rating, self-rating table must appear. 2. Examine that user must be able to add the rating while clicks the add button by entering the ratings in the rating field. 3. Examine that user must be able to edit the rating by hitting the edit icon button which is available in the action column. 4. Examine that user must be able to delete the rating by hitting the delete icon button which is available in the action column. 5. Make sure that number of entries are less than 10 in the self-rating table the previous indicator (<<) and next indicator (>>) are disabled. 6. Ensure search box functionality for the rating table. "240Admin user should be able to add soft skill criteria used for appraisal purpose.,1. Ensure that the soft skill table appears while clicking the soft skill sub-tab of the admin module. 2. Examine that user can add the skill by hitting the add button by entering the skills in the skill field. 3. Examine that user can edit the skill by hitting the edit button which is available in the action column. 4. Examine that user can delete the skill by hitting the delete button which is available in the action column. 5. Make sure that number of entries are less than 10 in the soft skill table the previous indicator (<<) and next indicator (>>) are disabled. 6. Ensure search box functionality for skill table 241Admin should be able to view total working days and Leaves count.Accessible to Admin only.,"1. Ensure that the user is able to view the employee performance page after clicking on the employee performance module. 2. Make sure that the Year Dropdown must be auto-selected for the current date, and the admin can select the year from the dropdown list. 3. Examine that admin can select the employee's name from the dropdown list. "242 User can able to see the different domains with detailed information.,"1. Examine whether the various domains are displayed in card format on the domain module screen 2. To ensure that the domains listed in card format on the webpage are clickable. 3. To ensure that the domain listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each domain 4. Examine whether the user is redirected to a new page or a detailed view of the selected service within the specific domain 5. To confirm that the projects listed under specific domains are easily accessible. 6. To ensure that the clients listed under specific domains are easily accessible, allowing users to navigate to specific client detailed page. 7. Make sure that the tools listed under specific domains are easily accessible. 8. Examine whether the Technology listed under specific domains are accessible. 9. To confirm that clicking on the Back button properly redirects the user back to the domain module screen. "243Users can see the different tools with detailed information once the admin is added.,"1. Examine whether the various tools are displayed in card format on the tools module screen 2. To ensure that the tools listed in card format on the webpage are clickable 3. To ensure that the tools listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each tools 4. Verify the Next pagination button. 5. Verify the Previous pagination button. 6. Examine whether the user is redirected to a new page or a detailed view of the selected service within the specific tool 7. To confirm that the clients listed under specific tools are easily accessible 8. To ensure that the projects listed under specific tool are easily accessible, allowing users to navigate to specific project detailed page 9. Make sure that the technology listed under specific tools are easily accessible 10. Examine whether the domains listed under specific tool are accessible 11. To confirm that clicking on the Back button properly redirects the user back to the tool module screen "244 Admin can edit the existing tool by updating the information such as the version or description of the tool.,"1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of technology. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the technology details and exit the edit mode. "245Admin can delete a tool by selecting this action.,"1. To validate the functionality of the Delete button for technology, allowing the deletion of existing technology from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. "246 User can see the different technologies with detailed information.,"1. Verify the Technologies module functionality. 2. To ensure that the technologies listed in card format on the webpage are clickable. 3. To ensure that the technologies listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each technology. 4. Verify the Next pagination button. 5. Verify the Previous pagination button. 6. Examine whether the user is redirected to a new page or a detailed view of the selected service within the specific technology 7. To confirm that the clients listed under specific technology are easily accessible 8. To ensure that the projects listed under specific technology are easily accessible, allowing users to navigate to specific project detailed page 9. Make sure that the tools listed under specific technology are easily accessible 10. Examine whether the domains listed under specific technology are accessible 11. To confirm that clicking on the Back button properly redirects the user back to the technology module screen. "247"By performing these information gathering tasks, security testers gain valuable insights into the target web application and its infrastructure, enabling them to plan and execute subsequent testing activities effectively to identify and mitigate potenti...","1. To check the effectiveness of search engine queries in retrieving specific information related to the target. 2. Enumerate the sub-domains by using various other search engines (Bing,DuckDuckGo,Shodan) 3. To perform banner grabbing and analyze the response headers of the web server. 4. To check the behavior of the web server by sending incorrect or malformed requests intentionally. 5. To perform web server fingerprinting using specialized tools and analyze the server type and version based on the responses.(e.g., nmap, Netcraft, Nikto, skipfish, Netcat). 6. To review web server metafiles (e.g., configuration files, log files) for valuable information, server configuration details, potential vulnerabilities, and exposed sensitive data. 7. Check by identifying further paths or resources to include in discovery/analysis using tools(Google Webmaster, curl, wget, Burp Suite, ZAP) 8. To analyze the HTML source code of a web page to gain insights into its structure, functionality, and potential vulnerabilities. 9. Verify the parameters and request headers for GET & POST requests using a proxy tool. 10. Verify the application framework and components been used by the application (WhatWeb, Wappalyzer) 11. Enumerate for the specific files & folders using tools (dirbuster with Burp) 12. Determine the application framework identified from file extensions eg. php,aspx,jsp. 13. N/A 14. N/A 15. Check the the HTTP headers sent and received by the application for some headers, such as cookies, refer, or user-agent, may contain user-controlled or external data that can be manipulated for attacks. 16. N/A "248" Configuration and Deployment Management Testing ensures that the network infrastructure, application platform, and associated configurations are appropriately set up, hardened against potential vulnerabilities, and comply with security best practices. B...",1. To perform brute-force or dictionary attacks against common admin interface URLs or paths. 2. To check for the HTTP verbs that are supported by the web server using tools (Nmap) 3. Examine for access control bypass vulnerability by arbitrary redirect methods 4. Review for the cross-site tracing potentialities using the TRACE method to steal legitimate users’ credentials 5. Checking for HTTP Method overriding by emulating the missing HTTP verbs passing some custom header in the requests 6. Review for HSTS by examine the server response and validity by intercepting proxy 7. N/A 8. N/A 9. N/A 10. N/A 11. N/A 12. N/A 13. N/A 14. Ensure that defaults and known configuration files have been removed and the logging mechanisms set in place for the production environment. 15. N/A 16. Review the Content-Security-Policy header or meta element to identify misconfigurations. 249"Security tester ensures that user identities, roles, and access controls are properly managed. It aims to prevent unauthorized access, protect user identities, and maintain the integrity of the authentication and authorization mechanisms.",1. Check for identifiable roles used by the application through documentation and fuzzing. 2. Asure how administrator provision other administrators or just users 3. N/A 4. N/A 5. Enumerate users where possible through response analysis. 250 Authentication Testing focuses on evaluating the security and effectiveness of the authentication mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could potentially lead to unauthorized access or compr...,1. Test the server to forcefully downgrade to HTTP to exchange credentials without encryption. 2. To analyze the HTTPOnly and Secure attributes for the cookies in response 3. Check by fuzzing the username if they are created with any defaults or identifiable patterns. 4. To ensure authentication bypass by direct page request/forced browsing to check access control across the application 5. Make sure authentication bypass by parameter modification using proxy repeater/interceptor 6. To make sure for authorization bypass by Session ID prediction test 7. Verify for back refresh vulnerability for the application flaw to monitor browser history 8. For analyzing any leaking of any sensitive data into the browser cache stored in the local files 9. N/A 10. N/A 11. N/A 12. N/A 13. N/A 14. N/A 15. N/A 251 Authorization Testing focuses on evaluating the effectiveness and security of the authorization mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could lead to unauthorized access or privilege escalatio...,"1. Examine the application for injection points that pertain to path traversal by a systematic evaluation of each input vector 2. Check for input validation bypassing by enumerate all the GER/POST URLs, file upload and forms that accept content from the user. 3. Review for access to administrative pages/functionality when a non-administrative user tries access resources 4. Check for lateral movement attacks, to access resources across users with the same role or privilege 5. Check for vertical privilege escalation to access functions and resources that are role restricted above user level 6. Check if a value of a parameter is used directly to retrieve a database record 7. Revise for OAuth Authorization Server Weaknesses 8. Examine for OAuth Client Weaknesses "252" Session Management Testing focuses on evaluating the security and effectiveness of session management mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could lead to unauthorized access, session hijacki...",1. Ensure the session token by examine the structure and contents for information leakage 2. Determine the session ID randomness and predictability and encryption/encoding by analyzing sequences generated by server 3. Check for the cookie attributes like Secure and HTTPOnly are configured 4. Test for HTST by analyzing the authentication mechanism and its flow. 5. To exploit for the HTTP-based token stored in the client browser and capture the session 6. To check the logout functionality for a user to manually terminate the session 7. Examine for server-side state validation and session timeout due to inactivity 8. N/A 9. N/A 10. N/A 11. N/A 12. N/A 253" Input Validation Testing focuses on ensuring that user input is properly validated and sanitized, mitigating the risk of various types of attacks and protecting the application and its users' data. It aims to identify vulnerabilities and weaknesses...","1. Check the input vectors such as HTTP parameters in POST requests, pre-defined radio, selection values and input fields 2. Ensure the XSS by bypassing the filter via HTTP parameter pollution 3. Examine the SQL vulnerability by inject script in input vectors the interact with DB 4. Examine various SQL injections such as time-based, error-based, union, and out-of-band or vulnerabilities 5. To check the SQL filter bypass techniques (Whitespace, NULL byte, URL encoding, character encoding, Hex encoding) for vulnerabilities 6. Examine for server-side code execution on the web server by code injection 7. Determine code injection by NULL byte, path and dot injection to exploit LFI vulnerabilities 8. To check code execution on the client-side which can lead to other attacks such as cross site scripting (XSS) 9. Check for OS command injection vulnerability by using special characters( | ; & 10. > < ' ! ) in URL 11. Ensure if the chain of communication is vulnerable to smuggling use different methods in a HTTP request 12. Check by using X-Forwarded Host Header to bypass application security 13. Test for web cache poisoning, the ability to poison the caching proxy run by the application itself 14. Testing for Oracle 15. Testing for MySQL 16. Testing for SQL Server 17. Testing PostgreSQL 18. Testing for MS Access 19. Testing for NoSQL Injection 20. Testing for ORM Injection 21. Testing for Client-side 22. Testing for File Inclusion "254Security tester focuses onError Handling to evaluating the application's response to various error conditions and ensuring that sensitive information or system details are not disclosed to potential attackers. It aims to identify vulnerabilities ...,1. Reviewing the error message to bring out more information or error details from web service 2. N/A 255" Weak Cryptography validation focuses on evaluating the cryptographic mechanisms employed by a web application. It aims to identify vulnerabilities and weaknesses in encryption, transport layer security, handling of sensitive information, and maintains c...",1. Examine the server configuration with protocol versions that can have cryptographic weakness 2. Ensure for active resources (such as CSS) that are loaded into secure pages via insecure channel 3. Check form-based authentication performed over HTTP and asserting HTTP traffic 4. N/A 5. N/A 256" Business Logic Testing focuses on evaluating the correct implementation and security of the application's business logic. It aims to identify vulnerabilities and weaknesses in the application's logic flow, data validation, process timing, and ...","1. Ensure the target functionality, check if for a logical limit set on the functions and if it is properly validated. 2. Ensure the unwelcomed file types are rejected and handled safely. 3. N/A 4. N/A 5. N/A 6. N/A 7. N/A 8. N/A 9. N/A 10. N/A 11. N/A "257"Client-side Testing focuses on evaluating the security of the client-side components of a web application, including JavaScript, HTML, CSS, and browser-related features. It aims to identify vulnerabilities and weaknesses that could be exploited by attac...","1. Check for DOM-xss vulnerability of code execution on active browser content, obtaining input through source and using it in sink 2. Ensure for HTML injection vulnerabilities via innerHTML , document.write() JavaScript method. 3. Check for X-Frame-Option header to mitigate the clickjacking vulnerability 4. N/A 5. N/A 6. N/A 7. N/A 8. N/A 9. N/A 10. N/A 11. N/A 12. N/A 13. N/A 14. N/A "258" API Testing involves evaluating the security and functionality of Application Programming Interfaces (APIs) used in web applications or software systems. It focuses on identifying vulnerabilities, misconfigurations, and flaws in API implementations.",1. Verify discovering APIs for targeted application through passive recon process 2. Verify discovering APIs by actively scanning with tools and documentation 3. N/A 4. N/A 5. N/A 6. N/A 7. N/A 259 User can view the list of clients.,"1. Examine whether the various clients are displayed in card format on the client module screen. 2. To ensure that the clients listed in card format on the webpage are clickable 3. To ensure that the clients listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each cllient 4. Examine whether the user is redirected to a new page or a detailed view of the selected service within the specific client 5. To confirm that the projects listed under specific clients are easily accessible 6. To ensure that the tools listed under specific client are easily accessible. 7. Make sure that the technology listed under specific clients are easily accessible 8. To confirm that clicking on the Back button properly redirects the user back to the client module screen "260" The information gathering phase in web application penetration testing involves collecting relevant data about the target application. It includes passive techniques like open-source intelligence (OSINT), DNS enumeration, and reviewing archived web page...",1. Verify the identification of the LMS URL and its subdomains by using Search Engine Operators 2. Check for the revealing error message content and hidden directories or publicly exposed resources. 3. Verify the type and version of the Apache web server for known version-specific exploits 4. Check the information gathered by banner grabbing responses by malformed HTTP requests. 5. Verify webpage comments for information leakage. 261The Configuration and Deployment Management Testing phase in web application penetration testing focuses on evaluating the configuration and deployment processes of the web application to ensure secure and reliable operation. This phase includes activit...,"1. Verify the default or weak credentials on admin interfaces by attempting common usernames and passwords. 2. Verify the default or weak credentials on admin interfaces by using default credentials lists, or performing password spraying attacks. 3. Verify that if secure communication protocols (HTTPS) are enforced by verifying if the application uses SSL/TLS certificates. 4. Verify that HTTP and HTTPS is properly configured within the application. "262" The Identity Management Testing phase in web application penetration testing is dedicated to evaluating the authentication, authorization, and user management features of the application. This phase aims to identify potential vulnerabilities and weaknes...",1. Verify that user applying leave are aligned with business and security requirements. 2. Verify which accounts may provision other accounts and of what type. 3. Check whether the CORP application is vulnerable to account enumeration via the application's error messages. 263 The Authentication Testing phase in web application penetration testing focuses on assessing the security and reliability of the authentication mechanisms implemented in the web application. This phase involves activities such as testing the strength of...,"1. Validate the application's user accounts with default passwords. It can be built in administrative credentials. e.g. username-admin, password-12345. 2. Verify the account lockout mechanism by using the incorrect password a number of times, before using the correct password to verify that the account locked out. 3. Verify the unlock mechanisms it involve secret questions to unlock. It link should be a unique one-time link, to stop an attacker from guessing or replaying the link and performing brute force attacks in batches. 4. Verify the Force browsing by directly requesting different page that page check the credentials of user before granting access e.g. http://abc.com/users/administrator. 5. Verify the Parameter modification functionality by modifying the parameters to gain access to the protected areas without providing valid credentials. 6. Check if the CORP application stores sensitive information on the client side browser cache issue from HTTP response headers (Cache-Control: no-cache). 7. Check if access can occur without authorization in CORP application. 8. Check the browser history issue by clicking the Back button after logging out. "264 This phase focuses on evaluating the authorization mechanisms of the web application. It involves testing whether users are granted appropriate access rights based on their roles and privileges. The goal is to identify any vulnerabilities or misconfigur...,"1. Verify for injection points that pertain to path traversal. 2. Check for injection locations that are relevant to bypassing strategies. 3. Identify the extent of path traversal (dot-dot-slash attack, Local/Remote file inclusion). 4. Check if horizontal or vertical access is possible to gain administrative functions by force browsing. 5. Check if vertical access is possible to gain administrative functions by force browsing. 6. Verifying injection points related to role/privilege manipulation. 7. Validating for the points where object references may occur and attempting to access control measures and if they're vulnerable to IDOR. 8. Verifying if OAuth implementation is vulnerable or using a deprecated or custom implementation. "265" This testing involves assessing the management and security of user sessions within the web application. It aims to ensure that session tokens are securely generated, stored, and invalidated after logout or a specified period of inactivity. The goal is ...","1. Validating the session tokens, for the same user and for different users where possible to analyze and ensure randomness exists to stop session forging attacks. 2. Verify by modifying cookies that are not signed and contain information that can be manipulated. 3. Check for existing HTML tags that can cause immediate access to DOM resources such as <img> 4. Validate for proper encryption and application-level authentication standards. 5. Validate the user logout interface as a visual indication for intended uses. 6. Validating interval-based session timeout for balanced security and usability. 7. Validate for server-side session termination of the user session mitigating the cached based back-refresh attack. 8. Validate for hard session timeout, all session tokens invalidation 9. Check for enforced server-side session timeout management and expiration. 10. Verify for the JWTs expose sensitive information. 11. Verify if JWTs signature is been tampered or can be modified "266"This phase focuses on testing the web application's input validation mechanisms. It aims to identify vulnerabilities related to user input, such as SQL injection, cross-site scripting (XSS), command injection, and other input-based attacks. The goa...","1. Verify the variables that are reflected in responses and check the input they accept as well as the encoding that gets applied on return. 2. Verify the stored input variables that are reflected on the client side and verify the input they accept as well as the encoding that gets applied on return. 3. Checking SQL injection points, the severity of the injection, and the level of access that can be achieved through it. 4. Verify all the LDAP injection points in web application. 5. Checking XML injection points with XML Meta Characters 6. Checking SSI injection points (Presence of .html extension) with the characters. 7. Verify XPATH injection points by checking for XML error enumeration by supplying a single quote ('): 8. Verify IMAP/SMTP injection points (Header, Body, Footer) with special characters (i.e.: \, ‘, “, @, #, ! |) and exploit. 9. Verifying and assessing the command injection points with special characters (i.e.: |; & 10. > < ' !) 11. Checking whether injecting format string conversion specifiers into user-controlled fields causes undesired behavior from the application. 12. Verify template injection vulnerability points by checking for the templating engine and exploiting. 13. Check for SSRF injection points and test if the injection points are exploitable. "267"This testing involves evaluating how the web application handles various error conditions, such as invalid input, server errors, and exceptions. The goal is to identify any information leakage, error messages that reveal sensitive information, or error ...","1. Validating existing error output (i.e.: Random files/folders (400 series) and analyze the different output returned. 2. Check to see if error messages are logged appropriately and securely. 3. Check if the application reveals detailed error messages containing sensitive data or system information. 4. Verify how the application responds, ensuring it handles errors gracefully and securely. 5. Verify the prevention of detailed error messages that disclose sensitive information by entering invalid or malformed data. 6. Check if error messages are properly logged and monitored by causing intentional errors. 7. Verify the prevention of server and application stack trace leakage by manipulating inputs to trigger exceptions. 8. Check if stack traces or other internal information is exposed. 9. Assess the handling of unexpected or malformed input by providing unexpected or malformed input. "268"This phase focuses on testing the web application's business logic to ensure that it operates correctly and securely. It involves evaluating the application's workflows, business rules, data validation, and access control mechanisms. The goal ...",1. Check the data injection points. 2. Validate that all checks are occurring on the back end and can't be bypassed. 3. Check if you are able to break the format of the expected data and the application behavior. 269"This testing involves assessing the security of the client-side components of the web application, such as JavaScript, HTML, and CSS. It aims to identify vulnerabilities, such as cross-site scripting (XSS), client-side code injection, insecure client-si...","1. Check for DOM sinks and verify against payloads that pertain to every sink type. 2. Check for sinks and possible JavaScript injection points, ensuring that the expected functionality and behavior are achieved. 3. Check HTML injection points and assess the severity of the injected content. 4. Check injection points that handle URLs or paths. 5. Verify the locations that the system could redirect to (Open Redirect) 6. Check for CSS injection points and exploits. 7. Check sinks with weak input validation. 8. Verify endpoints that implement CORS for secure configuration. 9. Check and analyze the application's code for potential sink points and unsafe method usage. 10. Test if the CORP application is vulnerable by loading into an iframe. 11. Verify via a simple web page that includes a frame containing the target and if they are able to bypass. 12. Verify client-side stored data by the CORP application 13. Verify the code handling storage objects against the possibility of injection attacks, such as utilizing invalidated input or vulnerable libraries. "270" This phase focuses on testing the security and reliability of the web application's APIs (Application Programming Interfaces). It involves evaluating the authentication and authorization mechanisms, input validation, error handling, and access cont...","1. Check for API via Passive Recon with Google Hacking and Shodan. 2. Check for API via Active Recon Baseline Scanning with Nmap 3. Check against the password Brute-Force and Password Spraying attacks using a common password wordlist, or custom list. 4. Check for a Password Reset functionality for exploitable Multifactor Authentication Brute-Force, including Base64 Authentication. 5. Check for JSON Web Token Abuse, if it can me modified. 6. Verifying fuzzing using Burp Suite and payloads like SecList for wide and deep fuzzing tests 7. Checking for Cross-Site Scripting (XSS) 8. Checking for Cross-API Scripting (XAS) 9. Checking for SQL Injection 10. Checking by Command Injection in API 11. Check complex access control policies with different hierarchies, groups, and roles. 12. Check an unclear separation between administrative and regular functions, tend to lead to authorization flaws. "271" Information Gathering involves both passive and active techniques to gather data from publicly available sources, such as search engines, social media platforms, public records, and organizational websites. It may also include more targeted approaches l...","1. Examine that identification of the target application's URL, IP address, and subdomains by performing a DNS lookup or Search Operators 2. Make sure last cached/previous version of the targeted application in Internet Archive using Wayback Machine 3. Examine the type and version of web server that a target is running on for known version-specific exploits. 4. Determine webpage comments for information leakage. 5. Check metadata for information leakage. 6. Examine the status code 7. Examine the JavaScript files for information leakage. 8. Ensure that header of request and response analysis which covers methods of HTTP header analysis. 9. Verify where GET/POST are used including the hidden parameters and URL parameters. 10. Examine that where there are any redirects (3xx HTTP status code), 400 status codes, in particular 403 Forbidden, and 500 internal server errors during normal responses (i.e., unmodified requests). 11. Check for possible entry and injection points through custom type headers. 12. Verify for possible entry and injection points where cookies are set (Set-Cookie header), modified, or added to in response. 13. Examine the Application Architecture and technologies used in application using Wappalyzer. 14. Validate the Application Architecture and Application Components like Host, Ports, services/APIs. "272Policy Details section will help the Super Admin/ Admin to enter policy related information.,"1. Examine that admin or super admin can enter Policy name, Policy Purpose, Policy category, Policy Applicability when click on Policy details form.. "273"Configuration and Deployment Management Testing refers to the assessment of the security of configuration and deployment processes within a software system. It involves identifying vulnerabilities and weaknesses that may arise due to misconfigurations, ...","1. Determine the default or weak credentials on admin interfaces by attempting common usernames and passwords. 2. Examine the default or weak credentials on admin interfaces by using default credentials lists, or performing password brute force attacks. 3. Ensure if the application uses SSL/TLS certificates to see if secure communication protocols (HTTPS) are enforced. 4. Ensure that HTTP and HTTPS is properly configured within the application. 5. Examine the identification of unnecessary services or ports that may be accessible by conducting a port scan. "274" Identity Management Testing refers to the process of assessing the effectiveness and security of an organization's identity and access management (IAM) system. IAM systems are designed to manage user identities, their authentication, authorization,...","1. Examine the user roles used by the application, to switch or change another role. 2. Determine that the identity requirements for user registration are aligned with business and security requirements. 3. Ensure processes that pertain to user identification. 4. Determine whether the application is vulnerable to account enumeration via the application's error messages. "275Authentication testing in Penetration Testing focuses on assessing the security and effectiveness of an application or system's authentication mechanisms. The objective is to identify vulnerabilities and weaknesses that could be exploited by attack...,"1. Determine the sensitive information (credentials, Project information etc.) is transmitted through encrypted channel. It assess the privacy/security of the used channels(HTTP/HTTPS). 2. Examine the application's user accounts with default passwords. It can be built in administrative credentials. 3. Ensure the account lockout mechanism by using the incorrect password a number of times, before using the correct password to verify that the account locked out. 4. Make sure that Force browsing by directly requesting a different page that page checks the user's credentials before granting access. 5. Check that Parameter modification functionality by modifying the parameters to gain access to the protected areas without providing valid credentials. 6. Examine the ability of the application against brute Force password guessing using available password dictionaries by evaluating the length & complexity of passwords. "276Authorization testing in Penetration Testing focuses on evaluating the security and effectiveness of an application or system's authorization mechanisms. The objective is to identify vulnerabilities and weaknesses that could allow unauthorized acce...,1. Determine the injection points that pertain to path traversal. 2. Examine for injection locations that are relevant to bypassing strategies. 3. Identify the extent of path traversal 4. Ensure if horizontal or vertical access is possible? to gain administrative functions by force browsing. 5. Check if vertical access is possible? to gain administrative functions by force browsing. 6. Determine the injection points related to role/privilege manipulation. 7. Validating for the points where object references may occur and attempting to access control measures and if they're vulnerable to IDOR. 277"Considering the RBAC The Clinic Owner, HOD, and Freelancer will be able to see this ledger in order to understand the income they are receiving from scheduling appointments through the Appointment ledger for the current week, six months, twelve mon...","1. Users will not be able to view Appointment ledger page, since they do not have access to it. 2. Users will be able to view Appointment ledger page 3. Users will be able to view Appointment ledger page, since they possess access to it. 4. Users will not be able to view Appointment ledger page 5. FDM user will be able to access the Appointment ledger modules of the clinic that they would be assigned to. 6. On clicking the Appointment ledger module user navigate on OVERVIEW tab,Select Clinic Dropdown will be auto-selected, appointment collection shown for that desired clinic along with CREDIT STATEMENT and INSIGHTS 7. On clicking the Appointment ledger module user navigate on OVERVIEW tab,Select Clinic Dropdown will be auto-selected, and no information shown 8. User should able to view APPOINTMENT COLLECTION for selected desired clinic and changed weekly into monthly or yearly by clicking on arrow icon 9. User's click on IN CLINIC PAYMENTS FOR COMPLETED APPOINTMENTS and navigate on IN-CLINIC Payments,UNPAID tab for checking TODAY'S UNPAID APPOINTMENTS(COUNT) and OLDER'S UNPAID APPINTMENTS(COUNT) 10. On clicking the IN CLINIC PAYMENTS FOR COMPLETED APPOINTMENTS module user navigate on UNPAID tab,Select Clinic Dropdown will be auto-selected, appointment status for TODAY'S UNPAID APPOINTMENTS(COUNT) and OLDER'S UNPAID APPINTMENTS(C... 11. User selects a desired clinic from the Select Clinic dropdown list. 12. User attempts to select more than one clinic from Select Clinic dropdown list. 13. User does not select any clinic from the Select Clinic dropdown list. 14. Clinic is selected by default in the Select Clinic dropdown, the profile card of the respective patients of the clinic with details are displayed. 15. On selecting the desired clinic from the Select Clinic dropdown, the profile card of the respective patients of the clinic are displayed user clicks on the profile card of the patients. 16. On selecting the desired clinic from the Select Clinic dropdown, the profile card of the respective patients of the clinic are displayed user does not click on the profile card of the patients. 17. User chooses a clinic from Select Clinic dropdown and then valid year and month from both the Select Year and Select Month dropdowns respectively. 18. User chooses an invalid year or month from the Select Year and Select Month dropdowns respectively. 19. User chooses to not select any year or month from the dropdowns. 20. User can keep track of the paid appointments, User can select particular Week appointment details by clicking on downward arrow in the week section of the PAID. 21. User don't select particular Week appointment details by clicking on downward arrow in the Week section of the PAID. 22. User don't select particular Week appointment details by clicking on downward arrow in the Week section of the PAID. 23. The user can view the patient count for the chosen clinic's Total Advance Payement Collected, Total Appointment Completed, and Total Refund Given. 24. User can switch between the Today and Last 7 Days toggles by selecting the RECENT tab, browsing from the OVERVIEW tab, and having the Choose Clinic Dropdown automatically selected. 25. On selecting the desired clinic from the Select Clinic dropdown, the profile card of the respective patients of the clinic are displayed for chosen toggle option that is Today ,patients cart are shown according to date 26. On selecting the desired clinic from the Select Clinic dropdown, the profile card of the respective patients of the clinic are displayed for chosen toggle option that is Last 7 Days ,patients cart are shown according to date 27. Without selecting any clinic from the Select Clinic dropdown, the profile card of the respective patients of the clinic are displayed for choosen toggle option that is Last 7 Days ,patients cart are shown according to date 28. Choose the chosen clinic first, or stick with the one that was automatically selected, and then choose For which time do you require a statement from the options of last month, last 3 months, last 6 months, last year, or choose custom range o... 29. Choose the chosen clinic first, or stick with the one that was automatically selected, and then choose For which time do you require a statement from the options of last month, last 3 months, last 6 months, last year, and click on Share butt... 30. Without selecting any clinic from the Select Clinic dropdown, and then choose custom range of dates that is valid start date to valid End date and tries to click on Share button 31. Without selecting any clinic from the Select Clinic dropdown, and then choose For which time do you require a statement from the one of the options from last month, last 3 months, last 6 months, last year and tries to click on Share button 32. Choose the chosen clinic first, or stick with the one that was automatically selected, and without selecting any option directly tries to hit Share button 33. User attempts to select multiple For which period do you require a statement slots in a single try and tries to click Share button. 34. User selects a invalid end date first and a valid start date later, and clicks on Share button, in the CUSTOM tab of Appointment ledger 35. User selects an invalid start date and an invalid end date, and clicks on Share button, in the CUSTOM tab of Appointment ledger. "278" CTC Reconciliation for Employee Admin should be able to view active and inactive employee details in data table format, the column contains EMP name, gross CTC, variable pay, payroll status, joining date, revision date.","1. Confirm the 'Active', and 'Inactive' tabs are present under the CTC Reconciliation tab. 2. Make sure of the Search bar working in the CTC reconciliation tab. 3. Evaluate the Show Entries Functionality 4. Examine the present columns for the 'Active' records. 5. Make sure the administrator's sole role is to view the current activeemployee of the organizationrecords in the Active tab. 6. Confirm the columns which are present on the Inactive tab screen. 7. Evaluate that the admin can't modify the data present on the Inactive tab. 8. By using the pagination feature, Evaluate admin is able to view multiple data entries. "279"Using Wallet, the balance will be updated. The amount of the remaining balance will be conspicuously displayed in bold font on the screen, and the number of prescriptions will depend on the availability and Doctor can add money, view analytics, view his...","1. Users will not be able to view hamburger Wallet tab, since they do not have access to it. 2. Users will be able to view hamburger Wallet tab 3. Users will be able to view hamburger Wallet tab, since they possess access to it. 4. Users will not be able to view hamburger Wallet tab 5. FDM user will be able to access the hamburger Wallet tab of the business that they would be assigned to. 6. On clicking the Wallet tab, the user view Hey,welcome to your wallet !, the on-boarding screen with the details and user does not click on GET STARTED button 7. On clicking the Wallet tab, the user view Hey,welcome to your wallet !, the on-boarding screen with the details keep showing to the user unless the GET STARTED button is clicked. The Onboarding screen would appear by default for the first time. 8. After clicking on GET STARTED ,user navigate on Wallet screen and does not click on DISMISS button 9. The user directly hit the dismiss button of the Free gift card and information card in the Wallet screen. 10. By default for first time user ,current balance should shown 0 with 20 free prescriptions on cart 11. for first time user ,current balance should shown 0 with no free prescriptions on cart 12. Users who have access to the wallet can add money to it by using chips or entering a numerical value and hit ADD button 13. Without adding money to the wallet, the user hits the ADD button. 14. By default the value in the amount box will be 0. If The user clicks the Enter amount link in the WALLET module's card and a Change input value pop-up box appears. The user then enters the value again in the Change input value numeric box... 15. User tries to enter alphabetic data into Change input value numeric box, and clicking the DONE button. 16. User tries to enter no data(Blank data) into Change input value numeric box, and clicking the DONE button. 17. A congratulations message is displayed by clicking +Click here to add 500 more to add more money and receive a larger free balance and user does not hits CONTINUE button 18. A congratulations message is displayed by clicking +Click here to add 500 more to add more money and receive a larger free balance and user hits CONTINUE button and able to add more money using +Click here to add 1000 more 19. User select select value recharge chip for balance with free balance amount and hits CONTINUE button 20. A congratulations message is displayed by clicking +Click here to add 500 more to add more money and receive a larger free balance and user hits CONTINUE button and able to add more money using +Click here to add 1000 more 21. User select select value recharge chip for balance with free balance amount and hits CONTINUE button 22. Without selecting any balance chips user tries to hits CONTINUE button 23. User can enter promo code received from events or concerts and hit APPLY button 24. User tries to hit APPLY button without entering any promo code 25. User tries to enter promo code which is already redeem by another user and hit APPLY button 26. User tries to enter expired promo code and hit APPLY button 27. User tries to enter wrong or incorrect promo code and hit APPLY button 28. Recharge value, transaction fees, taxes, and charges, as well as the total amount with charges, are displayed to the user as a summary and click on PROCEED TO PAY button and navigate to Success! Funds added with new balance card and BACK TO WALLET ... 29. Recharge value, transaction fees, taxes, and charges, as well as the total amount with charges, are displayed blank or null to the user as a summary and hits PROCEED TO PAY button 30. Recharge value, transaction fees, taxes, and charges, as well as the total amount with charges, are displayed wrong to the user as a summary and hits PROCEED TO PAY button 31. User tries to view particular history for that Select year dropdown and do not Select Months dropdown 32. The user attempts to view a certain history for which they choose either the Select year dropdown or the Select Months option 33. User wants to view particular history for that do not any field like Select year dropdown and Select Months dropdown 34. User wants to view particular history for that do not any field like Select year dropdown and Select Months dropdown 35. When the user clicks the arrow icon to expand or vice versa, the name of the selected month with the prescription count is displayed, and the user can examine the list of weeks for prescription based on the selected Select Year and Select Month drop... 36. Click on downward arrow icon for expanding week into day list 37. Click on upward arrow icon for closing expanded list 38. Average prescription created graph ,total prescription created count ,mean number of prescriptions/patient, total free prescription and most number of prescription created are visible to Usage History Analytics for user who can have access to the wallet 39. User able to changed graph by slide and it will reflect as LAST 6 MONTHS , LAST 12 MONTHS and at last LIFETIME and hit Back to recharge button 40. user able to changed graph by slide and it will reflect as LAST 6 MONTHS , LAST 12 MONTHS and at last LIFETIME and does not hit Back to recharge button 41. User can view INSIGHTS with same count after changing graph duration because INSITES i.e. Total prescription created count, Mean number of prescriptions/patient, total free prescription, Most number of prescription created counts will be remains... 42. User can check Current balance and current balance limit should be minimum 1 rs to maximum unlimited amount 43. In Add Money ,user click on Enter an amount button and enter minimum 1 rs to maximum unlimited amount 44. In Add Money ,user click on Enter an amount button and tries to enter 0 in Wallet 45. In addition to having proper user interface (UI), the user should be able to access the cart including the wallet add money andwithdrawpolicy and desired pop-up messages "280" In view employee activity admin should be able to view in table, download or view history of payslip and form 16 with time and date of employees.",1. Evaluate the Employee Activity History button 2. Examine the column for Document Activity History page. 3. Confirm the Search functionality present on the Employee Activity History screen. 4. Ensure the working of show entries dropdown. 5. Test the pagination of the Dashboard tab screen. 281" The user will be eligible to access the application after successful login. The Employee will provide their unique identifier, such as a username and password, and will be redirected to the user dashboard page.Users will have access to modules: Home, ...","1. Examine the outcome when the Login button is clicked while the Username and Password fields are both blank and without verifying the CAPTCHA. 2. Make sure that the image in the tile is displayed on click on the check box. 3. Check whether the tile images shown on the captcha are clickable. 4. Make sure that to skip the shown images and view more options, the skip button is present before selecting any image of them. 5. Examine that when a user fills out all mandatory fields on the Login screen of the Application and clicks the reset button, all fields are successfully reset to their default state. 6. To ensure the behavior of the system when the Login button is clicked with an empty Username field, a non-empty Password field, and without verifying the CAPTCHA. 7. Check the login functionality when the user inputs the Username, leaves the Password field blank, and does not verify the CAPTCHA. 8. Examine the login functionality of the application when an invalid Username and Password are entered, and the CAPTCHA is not verified. 9. When an invalid Username and valid Password are entered, verify the CAPTCHA and click the Login button to examine the response. 10. Check the response when an invalid Username and invalid Password are entered, verify the CAPTCHA and the Login button is clicked. 11. When a valid Username and valid Password are entered, without verifying the CAPTCHA click the Login button to examine the response. 12. Examine that once the user selects any option from the shown image, the skip button will be replaced by the Verify button. 13. If to reset the selected option make sure that the reset functionality is present whenever the CAPTCHA verifies. 14. Ensure that an audio option is present for the CAPTCHA to verify it. 15. Make sure that the Help option is present so that the user may obtain guidance on how to choose the photos from the shown selections. 16. Determine that the error message is shown in case the user selects the incorrect image and verified it. 17. Make sure an error message appears when the page timeout for the verified CAPTCHA. 18. Make sure that when a user enters the invalid password for login, a pop-up notification with the number of attempts is displayed to the user. 19. Confirm that When the user attempts more than three, a new pop-up message is displayed that states, You reached the attempt limit. Please contact the administrator. 20. When a valid Username and valid Password are entered, click the Login button once verify the CAPTCHA to examine the response. 21. Once the user has accessed the Payroll Management System's Home screen, check to see if the Home, Employee, and Investment modules are available. 22. Examine that the Login page's corresponding section, fields, and buttons are displayed with the correct alignments, spellings, font sizes, and font families. "282The user home screen often includes a home that presents a summarized view of their payroll-related data and key performance indicators. andthe user dashboard will provide an introduction to the application along with the scope and vision. It contains...,"1. Ensure that the Payslip functionality, which is clickable on the Report page of the Home module, is available for users so that they can view, download, and print their payslips. 2. Make sure that the Appraisal Letter capability, which is clickable on the Report page of the Home module, is available for users to view, and download their Appraisal Letter. 3. Examine that the Form 16 feature, which is clickable on the Report page of the Home module, is available for users to view and download their Form 16. 4. To read the announcement, make sure the Announcement section is available on the Report page of the Home modulethat cannot be clicked or editable. 5. Make sure the Document & Policy section is available on the Report page of the home modulethat cannot be clicked or editable, where the user can view the documents and policies added by admin. 6. Ensure that the corresponding sections or fields on the Report page of the Payroll Management System's Home module are displayed with correct alignments, spellings, font sizes, and font families. "283"The user will have access to the payslip to view, download, and print their pay slips. A payslip will provides a detailed breakdown of an employee's earnings, deductions, and net pay for a specific pay period.","1. Ensure that the user can easily navigate from the Payslip screen to the Home screen of the Payroll Management System using the Home navigation functionality. 2. Ensure that when the user navigates to the payslip screen, they are presented with the payslip for the current month with the correct details. 3. Ensure that the dropdown functionality is available to the user on the Payslip screen, enabling them to select the year and month for the payslip. 4. Examine that the payslip is displayed for the selected month of the year once the user clicks the Go button, and if the payslip is not present for that month of the year, then the message is displayed as No Data Available. 5. Confirm that when the user clicks the Go button after selecting the year and month, the Download and Print buttons are displayed if the payslip is available for that month. 6. Ensure that when the user clicks the download button, the payslip is downloaded in PDF format. 7. Ensure that when the user clicks the Print button, a print preview pop-up window is displayed before the payslip is printed. In this window, the user can select the printer, save the payslip as a PDF, choose the page layout, and specify the number of pa... 8. Ensure that the corresponding section, fields, and buttons on the Payslip screen are displayed with accurate alignments, spellings, font sizes, and font families. "284" The employee module maintains a centralized database or directory to store employee information. It focuses on managing employee-related information and activities. This includes capturing essential information, setting up payroll profiles, defining com...","1. To view the personal details of the user, ensure that the Employee Master tab is present under the Employee module. 2. Make sure the Bank tab is included in the Employee module to display the user's bank information. 3. Ascertain that the Address tab is present in the Employee module to display the user's address information. 4. To view the user's employment details, confirm that the Employment tab is present under the Employee module. 5. Examine that the Employee modules contain theFamily Members tab is present to view the user's family information. "285"This screen displays the total number of questions added, enables a functionality for adding questions, storing images, audio file and video files and display question format table.",1. Check if all questions are correctly displayed on the question management dashboard. 2. Examinethe template is downloaded to the specified location on the user's device. 3. Ensure that users can select an Excel file for uploading questions. 4. Check whether the valid keyword or term in the search box. 5. Check the Admin can Preview the already added valid data. 6. Check the Admin can edit and update the already added valid data. 7. Check the Admin can Delete the already added valid data. 8. To Test the working of the Previous and Next buttons are clickable. 286Admin will be able to select the image file from the local PC and upload it in the application. There is a functionality to rename as well as delete the file.,1. Check whether the Image Fields tab is clickable or not 287Admin will be able to select the audio file from the local PC and upload it in the application. There is a functionality to rename as well as delete the file.,1. Examine the audio fields tab is clickable or not 288Admin will be able to select the video file from the local PC and upload it in the application. There is a functionality to rename as well as delete the file.,1. Ensure that the functioning of the Communication Test for all skills. 289" Admin after clicking on Create questions icon will navigate on new screen, Clicking on Question type dropdown menu is available offering various question types to choose, such as Pick One, Pick Many, Communication, Coding, Dropdown and Drag and Drop. Th...",1. Check whether the Create Question tab clickable or not. 2. Check the Create Question dashboard shows the question details fields. 3. Check the short name field to enter valid data. 4. Check in the Difficulty Level drop-down field to enter a valid data selection. 5. Check in the Question Type drop-down field to enter a valid data selection. 6. Check in the Skill drop-down field to enter a valid data selection. 7. Check in the Question field to enter a valid data selection. 8. Examine whether the Save functionality is clickable or not. 290" The Doctor will be able to view the welcome message on the screen. There will be 2 dropdowns 1) Select single clinic, 2) Select Doctors. Also, they can view the calendar and the holiday list which has been set by the doctor previously. If doctor clicks ...","1. Users will not be able to view Set Working Schedule sub-module in the Calendar & Appointments module, since they do not have access to it. 2. Users will not be able to view Set Working Schedule sub-module 3. ADD FIRST CLINIC: User navigates to Hybrid Schedule Setup without clicking on +ADD FIRST CLINIC , directly hits the NEXT button 4. User navigates to Hybrid Schedule Setup clicks on +ADD FIRST CLINIC and fills the form to add a Clinic, and hit NEXT button 5. User navigates to Hybrid Schedule Setup clicks on +ADD FIRST CLINIC and fills the form partially to add a Clinic. 6. User navigates to Hybrid Schedule Setup clicks on +ADD FIRST CLINIC and fills the form to add a Clinic,Clinic is added, then user attempts to add another Clinic. 7. ADD BASE OF OPERATIONS: User navigates to Hybrid Visit Schedule Setup on clicking +ADD BASE OF OPERATIONS and without addind adding a base , directly hits the NEXT button 8. User navigates to Hybrid Visit Schedule Setup clicks on +ADD BASE OF OPERATIONS and fills the form to add a base, and hit NEXT button 9. User navigates to Hybrid Visit Schedule Setup clicks on +ADD BASE OF OPERATIONS and click on Next button without filling the form. 10. User navigates to Hybrid Visit Schedule Setup clicks on +ADD BASE OF OPERATIONS and fills the form to add a base,base is added, then user attempts to add another base. 11. On clicking the Hybrid visit module,Select Base Dropdown will be auto-selected, employees checkboxes will be checked and clicks on NEXT button. 12. On clicking the Hybrid visit module,Select Base Dropdown will be auto-selected, employees checkboxes will not be checked and clicks on NEXT button. 13. On clicking the Hybrid module,Select Clinic Dropdown will be auto-selected, employees checkboxes will be checked and clicks on NEXT button. 14. On clicking the Hybrid module,Select Clinic Dropdown will be selected, employees checkboxes will not be checked and clicks on NEXT button. 15. ADD AN EMPLOYEE: User clicks on Select Base dropdown, selects base, clicks on + Add an Employee button, landing on the Registration page for adding the role of the employee. 16. EDIT HOMELOCATION ON THE MAP: The user edits Home location on map for some employees(physiotherapist) and clicks the Next button 17. The user does not edit Home location on map for some employees(physiotherapist) and clicks the Next button 18. CREATE FIRST AREA OF SERVICE: User will not select any area of service, and directly clicks finish button. 19. User will select an area of service, and directly clicks the finish button. 20. User will select multiple areas of service, and directly clicks the finish button. 21. User while selecting multiple areas of service,the areas might intersect each other and directly clicks the finish button. 22. CLINIC AND HOME VISIT APPOINTMENT DURATION: User will click on NEXT button without selecting any time slot. 23. User selects one time slot from the given slots of each Clinic and Home Visit Appointment Duration and clicks on next button. 24. User attempts to select multiple time slots in a single try in both linic and Home Visit Appointment Duration slots respectively and clicks on NEXT button. 25. ENABLE WORKING DAYS: In Enable Working Days form, User selects all the day slots, and hits finish button. (Mon-Sun) 26. In Enable Working Days form, When none of the day slots are selected user hits finish button. 27. In Enable Working Days form, user clicks on an enabled day slot , it lands on Set working hours where the user doesn't schedule working hours and directly clicks on Finish. 28. User selects either a start time or an end time, and clicks on Finish button, in the Set Working Hours page. 29. User selects a valid start time and a valid end time, and clicks on Finish button, in the Set Working Hours page. 30. User selects an invalid start time and an invalid end time, and clicks on Finish button, in the Set Working Hours page. 31. SET WORKING HOURS: HYBRID : CLINIC SPECIFIC Assuming a user has scheduled an enabled day slot in the set working hours, they can duplicate the same schedule to another enabled slot or multiple slots. 32. HYBRID : HOME SPECIFIC Assuming a user has scheduled an enabled day slot in the set working hours, they can duplicate the same schedule to another enabled slot or multiple slots. 33. Assuming a user has scheduled an enabled day slots in the set working hours, they cannot duplicate the same schedule to another disabled slot or multiple slots. 34. User attempts to set a schedule on the disabled working day slots, in the set working hours page. "291" In information gathering we collects the information about the target payroll application. This includes identifying the application's infrastructure, technologies, and potential entry points. This involves searching for any sensitive information r...",1. Verify if any sensitive information related to the payroll application is not publicly available by searching for the application name in search engines. 2. Verify the last cached/previous version of the targeted application in Internet Archive using Wayback Machine 3. Verify the Server field in the server response header reveals information about the server version and type. 4. Check for other headers that may provide about the server version and type. 5. Check if the robots.txt file contains any disallowed paths or directories. 6. Verify the HTML source code of application for tags and their content. 7. Check if the sitemap.xml file for potential information leakage. 8. Verify if there are any comments in the HTML source code of the webpage for information leakage. 9. Verify the redirect bodies within the web pages for information leakage. 10. Look for any front-end debug files that may reveal sensitive information. 11. Analyze the HTTP headers sent in requests to the payroll web application for potential vulnerabilities. 12. Verify the technologies/frameworks used in the application by using Wappalyzer. 13. Checking for the framework/components & their versions used in the application from Error messages. 292" This phase focuses on evaluating the security configuration of the underlying infrastructure and deployed components of the payroll application. It involves checking for misconfigurations, open ports or services, or any other weaknesses that could be ex...",1. Verify the payroll application enforces secure communication protocols (HTTPS) by checking the usage of SSL/TLS certificates. 2. Verify that HTTP and HTTPS is properly configured within the application. 3. Verify the identification of unnecessary services or ports that may be accessible by conducting a port scan. 293This phase involves assessing the effectiveness of identity and access management controls within the payroll application. This helps identify vulnerabilities related to user authentication and authorization or user roles.,"1. Verify the application allows users to switch or change their assigned role, potentially bypassing access restrictions. 2. Check whether the application's error messages on the login page provide attackers with the ability to enumerate valid usernames. "294Authentication testing focuses specifically on evaluating the strength of the authentication mechanisms implemented within the payroll application. It attempts to bypass or exploit authentication controls to gain unauthorized access. This includes testi...,"1. Verify the sensitive information (Username, Password) is transmitted through the security channel of the used HTTPS. 2. Verify for the admin/user accounts with default passwords on URL - http://3.18.184.127:8080/payroll/login.do. 3. Verify the account lockout mechanism by using the incorrect password for number of times on the login page. 4. Verify the unlock mechanisms in the 'Payroll application'. 5. Verify by Force browsing by directly requesting a different page where unauthorized users attempt to access restricted resources directly by manipulating URLs. 6. Verify the Parameter modification functionality by modifying the parameters to gain access to the protected areas without providing valid credentials. 7. Verify whether the application stores sensitive information on the client-side, such as in browser cookies or local storage. 8. Check the browser history issue or back refresh attack by clicking the Back button after logging out. "295 This phase focuses on evaluating the effectiveness of authorization controls within the payroll application. We attempt to bypass or escalate privileges to gain unauthorized access to sensitive payroll data. This includes testing for vulnerabilities suc...,1. Verify the presence of injection points by browsing the payroll application and testing URLs for path traversal vulnerabilities. 2. Verifying injection points related to role/privilege manipulation. For checking vertical access is possible by force browsing. 3. Verifying injection points related to role/privilege manipulation. For check the Horizontal access is possible by force browsing. (For example: Change some Employee id=2 to Employee =1) 4. Validating for the points where object references may occur (Unique Identifier) and attempting to access control measures and if they're vulnerable to IDOR. 296"In this phase, checking the security of session management mechanisms implemented within the payroll application. The objective is to identify vulnerabilities such as session fixation, session hijacking, or session timeout issues etc. that could comprom...","1. Validating the Session Tokens for the Same User. 2. Validating the Session Tokens for the Different User. 3. Check that the proper security configuration is set for cookies (HTTP Only and Secure flag, Same site=Strict) 4. Check whether the application renews the cookie after successful user authentication. 5. Verify the session timeout functionality and ensure that session tokens are unusable after the timeout period. 6. Verify whether the JWTs expose sensitive information. 7. Verify whether the JWTs can be tampered with or modified. "297"This phase involves testing input validation mechanisms implemented within the payroll application. This aims to identify vulnerabilities such as cross-site scripting (XSS), SQL injection, or other types of injection attacks that could allow an attacker...","1. Identifying any variables within the application that are directly reflected in the responses returned to the client. 2. Identifying any input variables stored by the application and reflected on the client-side. 3. Checking for SQL injection points, the severity of the injection, and the level of access that can be achieved through it. 4. Verify all the LDAP injection points in the web application. 5. Verifying and assessing the command injection points with special characters. 6. Verify the XML injection points in the application. 7. Verify template injection vulnerability points by checking for the templating engine and exploiting. 8. Check for Server-Side Request Forgery vulnerability. "298"In this phase, examines how the payroll application handles various error conditions. This includes assessing error messages, error codes, and error handling routines. The goal is to identify potential information disclosure vulnerabilities or other wea...",1. Validating existing error output (i.e.: Random files/folders (400 series) and analyzing the different output returned. 2. Check if the application reveals detailed error messages containing sensitive data or system information. 3. Verify the prevention of server and application stack trace leakage by manipulating inputs to trigger exceptions. 299 This phase focuses on evaluating the implementation of cryptographic controls within the payroll application. The objective is to identify weaknesses in encryption and decryption processes that could potentially lead to data exposure or unauthorized acc...,"1. Validate the server configuration (Identify weak ciphers/protocols (ie. RC4, BEAST, CRIME, POODLE) 2. Checking the digital certificate's cryptographic strength and validity. 3. Check for sensitive information (Information used in authentication) transmitted through the various channels (e.g., Credentials, PINs, Session identifiers, Tokens, Cookies…) 4. Check for weak encryption or hashing uses and implementations. "300"A sub-module to add new supplier details to the in-app supplier list. Supplier details include name, number, email, city, state, etc. Also, show the current list if present",1. Check for the submission of valid supply information for supplier registration. 2. Evaluate functionality to alert User when trying to remove Supplier Details that are still in use 301 As sub module to check the supply status and make the statute active or inactive of a supplier,1. Check for the submission of supplier status to add new /updated exiting items 2. Evaluate functionality to alert User when trying to remove Supplier status that is still in use 3. Test the functioning of the Submit button by making a duplicate entry of the status 302 A submodule to add/removed categories that help to identify the asset types.,1. Check for the submission of the assets category to add new /updated existing items 2. Evaluate functionality to alert User when trying to remove an assets category that is still in use 303" A submodule to add a new sub-category as per need and the admin can select the field names and also make it mandatory or non-mandatory as well, and admin can edit or delete the subcategory and fields associated with the sub-category. The system will ens...","1. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with a single click 2. Evaluate functionality to alert User when trying to remove asset subcategories that are still in use 3. Check the functioning of Add Sub Category button, without selecting the asset category 4. Test the functioning of the Add button without entering data in the Sub-category field 5. Evaluate the process and functioning of the Add button by entering the data in the subcategory field and selecting the field names 6. Ensure that the added fields to the subcategory are reflected on the Asset Registration page 7. Test the functionality of the Show Entries, Search, and pagination features in a data table. 8. Check that the table name is accurate, alignments are correct, and the UI placement of the tables meets the design specifications. 9. Make sure the functionality of the system allows the admin to modify an added sub-category and the fields associated with it by clicking on the edit icon. 10. Ensure that the updated fields to the subcategory and the necessary validations are reflected on the Asset Registration page 11. Test the functioning of mandatory buttons without selecting the field name checkbox "304 A submodule to add/remove request-type list items for the in-app Request Type dropdown list,1. Check for the submission of request type to add new /updated exiting items 2. Evaluate functionality to alert Users when trying to remove a request type that are still in use 305 A sub-module to add and remove asset maintenance type for the in-app Asset Maintenance Type dropdown list,1. Check for the submission of asset maintenance type to add new /updated existing items 2. Evaluate functionality to alert Users when trying to remove asset maintenance types that are still in use 306 The application should provide a dashboard that allows an admin or accountant to examine the revenue and expense report and keep track.,"1. Verify user can select year from option 2. Check that 'Payment Type' dropdown to list allows the user to filter data as per payment types 3. To see the response click 'Category' dropdown and select required category from list. 4. Examine the functionality of 'Go' button 5. Check the data in 'Expense Category' card 6. Observe the 'Payment Types' card for proper visibility 7. Validate the 'Revenue Category' card 8. Observe the 'Receivables' and 'Payables' card 9. Check whether all data cards, filters, and buttons along with their labels from Dashboard are appropriately positioned or not. 10. See the compatibility of the 'Dashboard' screen with different screen resolutions. "307"Application should have Expenses tab from where admin can add and store the expense, upload multiple expenses, download expenses report.","1. Check user's ability to open 'Expense' tab from sidebar 2. Observe 'Expense' screen for positioning of all the data. 3. Make sure that 'Show Entries' dropdown displays list of expense bills 4. Check whether the search box allows to fetch required expense bill after entering the input. 5. Check to see if the 'Expense' screen is compatible with different screen resolutions. 6. Make sure that all data cards, dropdown, and buttons along with their labels from expense screen are appropriately positioned. 7. Validate the '+ add expense' button for adding a new new expense bill 8. Validate 'Template' button to download upload expense template 9. Validate 'Choose File' button for selecting a file to upload 10. Check whether user can upload a file having multiple expense invoice by clicking 'Import' button 11. Validate the 'Export' button for importing the expense bill list. 12. Validate the 'Payment' dropdown for selecting a required payment type from list ... 13. Validate 'Select Year' dropdown for selecting a financial year from list 14. Check whether user can see a list of required expenses, by clicking 'View' button 15. Examine user's ability to update the expense details by clicking the Pencil icon. 16. Check the functionality of Edit button. 17. Check the functionality of Delete button. 18. Validate the 'Import' button for downloading the expense bill list "308"Revenue screen of application displays a revenue list table. User should also be able to add new revenue invoice, upload multiple bills at a time, and download revenue list.","1. Verify functionality for 'Revenue' tab from sidebar 2. Validate Revenue screen 3. Validate the 'Show Entries' dropdown to display list of Revenues Invoice 4. Validate the search box to fetch required Revenue invoice 5. Verify whether all data cards, dropdown, and buttons along with their labels from Revenue screen are appropriately positioned or not. 6. Check to see if the 'Revenue' screen is compatible with different screen resolutions. 7. Validate the '+ add revenue' button for adding a new revenue invoice. 8. Validate 'Template' button to download upload revenue invoice template 9. Validate 'Choose File' button for selecting revenue invoice file to upload 10. By selecting the 'Import' button, verify that the user can upload a file containing several revenue invoices. 11. Validate the 'Export' button for downloading the Revenue invoices list 12. Validate 'Transaction type' dropdown to select type from list 13. Check whether user can see a list of required revenues, by clicking 'View' button 14. Check the functionality of Edit button. 15. Check the functionality of Delete button. "309" There should be a report screen that lists all revenues and expenses. The user can also view reports for custom choices. User can create and export customized report by filtering Payment type, Category, Financial year, quarter of year, and month.","1. Verify functionality for 'Reports' tab from sidebar which navigates user to report screen 2. Validate Report screen 3. Validate the 'Show Entries' dropdown to display list of Expense and Revenue Invoices 4. Validate the search box to fetch required Report from list 5. Check to see all of the Report screen's data cards, dropdowns, and buttons, as well as their labels, are placed correctly. 6. Verify that the 'Report' screen works with various screen resolutions. 7. Validate the 'Payment' dropdown to sort payment types 8. Verify the functionality for 'Categories' dropdown to select a required category from list 9. Validate the 'Financial Year' dropdown to select a year from list 10. Ensure the functionality of 'quarter' dropdown which allows user to select a required quarter of year from list 11. Validate 'Month' dropdown which allows user to select a required month from quarter which he selected earlier 12. Validate the 'Generate report' button, which enables the application to display a list of expenses and income that has been filtered based on the user's selections. 13. Check to see if user is able to download the reports list by clicking 'Export report' button "310 Application should have Invoice subtab under Insurance tab from where admin can add new groups of insurance policies. Admin can also view the newly added group policy.,"1. Make sure that user can add details of new Invoice into the table by using Add Insurance button and entering the required information into respective boxes and then clicking Add button. 2. Examine user's ability to Add Insurance by entering all the data except Invoice Date. 3. To see the outcome, fill all the required data except Invoice Number and click on Add button. 4. Ensure that user cannot add the details of invoice keeping Policy Number field blank even rest of the data is filled correctly. 5. Make sure that user is unable to Add Insurance if all the details are entered and Policy Name field is kept blank. 6. To see the outcome, fill all the required data except Basic Premium and click on Add button. 7. Examine user's ability to Add Insurance by entering all the data except Addition of Members and Deletion of Members. 8. Examine user's ability to Reset the entered data after entering all the data in Add New Invoice box. 9. Make sure that all the records entered into the table can be downloaded as an excel file by using Export functionality. "311" Application should have Admin modules to add master data. It should have Payment Type, Expense Category, Revenue Category, and Cash Voucher screens to add/remove respective entities","1. Verify whether clicking on the Admin tab causes it to be further divided into 5 subtabs. 2. Validate the 'Payment type' sub tab which navigates user to payment type screen 3. Validate Payment type screen 4. Validate the search box to fetch required Payment type 5. Verify whether all data cards, list, and buttons along with their labels from Payment type are appropriately positioned or not. 6. Check to see if the 'Payment type' screen is compatible with different screen resolutions. 7. Validate '+ add payment type' button 8. Check to see if user is able to add new payment type by entering details in 'Add payment type' pop up 9. Check the functionality of the Edit icon. 10. Check the functionality of the Delete icon. "312"Admin should be able to add, edit, and delete type of expenses category in this module","1. Verify the 'expense Category' subtab, which leads to the screen where you can add expense category. 2. Validate Expense category screen which displays list of existing categories 3. Validate the search box used fetch required category from list 4. Check to see all of the Expense category screen's data cards and buttons, as well as their labels, are placed correctly. 5. Verify that the 'Expense category' screen works with various screen resolutions. 6. Check functionality of '+ add Expense category' button 7. Check the '+ Expense category' pop-up to determine if the user may add a new category by entering the necessary information. 8. Check the functionality of the Edit icon. 9. Check the functionality of the Delete icon. "313"Admin will be able to add, edit, and delete of revenue category.","1. Verify the 'Revenue Category' subtab, which leads to the screen where you can add another Revenue category. 2. Validate Revenue category screen 3. Validate the search box to fetch required category 4. Verify whether all data cards, list, and buttons along with their labels from Revenue category screen are appropriately positioned or not. 5. Check to see if the 'Revenue category' screen is compatible with different screen resolutions. 6. Validate '+ add Revenue category' button 7. Check to see if user is able to add new category by entering details in 'add expense category' pop up 8. Check the functionality of the Edit icon. 9. Check the functionality of the Delete icon. "314 Group Medical Coverage includes insured name and family members of the employee. User can directly add policy by importing excel file or manually by adding Invoice number one by one.,"1. Examine user's ability to add insurance coverage to particular employee by clicking Add button next to that particular employee's name. 2. Make sure that user can add insurance coverage to multiple employees by importing an excel file with invoice details. 3. Ensure that user cannot add the insurance coverage to the employees, if the limit of number of members to be added in that policy is exceeded. 4. To see the outcome, click the Add button and then enter an invalid Invoice Number into the box and click the Add button. 5. Make sure that an excel file with records of GPA invoice details cannot be imported in the GMC records. 6. Ensure that user can remove insurance coverage to particular employee by clicking Delete button next to that particular employee's name. 7. Examine user's ability to remove insurance coverage to particular employee by clicking Delete button next to that particular employee's name and entering same invoice number that is added to the selected employee. 8. Ensure that all the records entered into the table can be downloaded as an excel file by using Export functionality. "315Group Personal Accidental coverage includes accidental coverage for the employees only. User can directly add policy by importing excel file or manually by adding Invoice number one by one.,"1. Examine user's ability to add insurance coverage to particular employee by clicking Add button next to that particular employee's name. 2. Make sure that user can add insurance coverage to multiple employees by importing an excel file with invoice details. 3. Ensure that user cannot add the insurance coverage to the employees, if the limit of number of members to be added in that policy is exceeded. 4. To see the outcome, click the Add button and then enter an invalid Invoice Number into the box and click the Add button. 5. Make sure that an excel file with records of GMC invoice details cannot be imported in the GPA records. 6. Ensure that user can remove insurance coverage to particular employee by clicking delete button next to that particular employee's name. 7. Examine user's ability to remove insurance coverage to particular employee by clicking Delete button next to that particular employee's name and entering same invoice number that is added to the selected employee. 8. Make sure that all the records entered into the table can be downloaded as an excel file by using Export functionality. "316"The admin can navigate on the Test Assignment Dashboard by clicking on the corresponding tab. The dashboard presents the test name and its related fields in a tabular format, ready to be assigned to the interview candidates. The Action column provides ...",1. Evaluate the functionality of Batch Code for a certain candidate SME Report. 2. Check the functionality of Employee name for batch code in SME Report. 3. Test the functionality of Select Mode for Quiz SME Report. 4. Examine the 'Next' button functionality for the SME candidate report. 5. Check the admin can assign the test for the employee. 317A sub-module to maintain in-app the asset maintenance status,1. Check for the submission of assets maintenance statute change to add new /updated existing items 2. Evaluate functionality to alert User when trying to remove assets maintenance status changes that are still in use 318A submodule for the admin to check the Asset maintenance request status raised by the employee. Admin can update the status of the request as per the asset maintenance type,1. Check admin functionality to update the maintenance status of the asset under maintenance 2. Check admin users can view the asset maintenance list and their maintenance status 319 A submodule to add or remove change category for in-app change category drop-down list,1. Check for the submission of the change category to add new /updated existing items 2. Evaluate functionality to alert Users when trying to remove a change category that is still in use 320A sub-module to add or remove environment types for the in-app environment dropdown list,1. Check for the submission of the environment to add new /updated existing items 2. Evaluate functionality to alert User when trying to remove environment that are still in use 321 A sub-module to add or remove impact types for in-app impact types drop-down list,1. Check for the submission of impact type to add new /updated existing items 2. Evaluate functionality to alert Users when trying to remove impact types that are still in use 322A submodule that can offer comprehensive information on the count of a certain item by its category and subcategory. Users may also download this list. The total count represents both allocated and unallocated assets.,1. Check admin user functionality to view and download the total assets list 323A submodule that provides comprehensive information about the available assets(laptop and mouse) that are unallocated,1. Check the admin user functionality to view and download available assets details 324"A submodule that contains the list of all the suppliers with details such as name, contact, mail, and status as active, or inactive.",1. Check the admin user functionality to view and download the list of supplier details 325" PHYSIOTHERAPISTS AND INTERNS [EXCLUDING BUSINESS]:Users will not be able to set a working schedule, as per role restrictions (RBAC)According to the rules' limitations, the user will not be able to access or define their own working schedule. (RBAC)","1. Users will not be able to view Set Working Schedule sub-module in the Calendar & Appointments module, since they do not have access to it. 2. Users will not be able to view Set Working Schedule sub-module 3. Without adding any home locations for the chosen employees(physiotherapist), the user clicks the Next button. 4. The user adds home locations for some employees(physiotherapist) but not for the others and clicks the Next button 5. After adding the home locations of each employee(physiotherapist) user clicks on Next button 6. User will not select any area of service, and directly clicks finish button. 7. User will select an area of service, and directly clicks the finish button. 8. User will select multiple areas of service, and directly clicks the finish button. 9. User while selecting multiple areas of service,the areas might intersect each other and directly clicks the finish button. 10. User will click on NEXT button without selecting any time slot. 11. User selects one time slot from the given slots and clicks on next button. 12. User attempts to select multiple time slots in a single try and clicks on NEXT button. 13. User selects a valid start time and a valid end time, and clicks on Finish button, in the Set Working Hours page. 14. User selects an invalid start time and an invalid end time, and clicks on Finish button, in the Set Working Hours page. 15. User selects a valid start time and an invalid end time, in the Set Working Hours page. 16. In Enable Working Days form, User selects all the day slots, and hits finish button. (Mon-Sun) 17. In Enable Working Days form, When none of the day slots are selected user hits finish button. 18. In Enable Working Days form, user clicks on an enabled day slot , it lands on Set working hours where the user doesn't schedule working hours and directly clicks on Finish. 19. Assuming a user has scheduled an enabled day slot in the set working hours, they can duplicate the same schedule to another enabled slot or multiple slots. 20. In the Edit Profile page, Assign Clinic dropdown list, the user selects the desired clinic out of the number of clinics present. 21. In the Edit Profile page, Assign Clinic dropdown list, the user selects multiple clinics out of the number of clinics present. 22. In the Edit Profile page, Assign Clinic dropdown list, the user selects all the clinics out of the number of clinics present. 23. In the Edit Profile page, Assign Clinic dropdown list, the user selects none of the clinics out of the number of clinics present. 24. METHOD 1: In Manage Employees, user can add employees,user clicks the +, fills the details using Add an Employee Manually and manages to successfully add an employee and assign a single clinic. 25. In Manage Employees, user can add employees, user clicks the +, fills the details using Add an Employee Manually and manages to successfully add an employee and assign a multiple clinics. 26. In Manage Employees, if user wishes to discard a clinic, the schedule of the clinic will be cancelled, and the clinic would no longer be associated with the employee. 27. The user does not select any clinic so the flow would not move any further. 28. In Set Working Schedule, in the Select Employees page, user can select a desired employee, if he has work scheduled in another clinic, it will show schedule present. If the user selects employee whose schedule is already present, the employee's... 29. In Set Working Schedule, in the Select Employees page, user can select multiple employees, if employees' have work scheduled in different clinics, it will show schedule present. If the user selects multiple employees whose schedules are alrea... 30. In Set Working Schedule, in the Select Employees page, user can select multiple employees, if employees' have no work scheduled in different clinics, it will not show schedule present. If the user selects an employee the schedule will be assi... 31. In Set Working Schedule, in the Select Employees page, user can select none of the employees, the flow would not move forward. 32. User navigates to Home Visit Schedule Setup without clicking on +ADD BASE OF OPERATIONS or adding a base , directly hits the NEXT button. 33. User navigates to Home Visit Schedule Setup clicks on +ADD BASE OF OPERATIONS and fills the form to add a base, and hit NEXT button 34. User navigates to Home Visit Schedule Setup clicks on +ADD BASE OF OPERATIONS and fills the form to add a base. 35. User navigates to Home Visit Schedule Setup clicks on +ADD BASE OF OPERATIONS and fills the form to add a base,base is added, then user attempts to add another base. 36. On clicking the Home visit module,Select Base Dropdown will be auto-selected, employees checkboxes will be checked and clicks on NEXT button. 37. On clicking the Home visit module,Select Base Dropdown will be auto-selected, employees checkboxes will not be checked and clicks on NEXT button. 38. For + Add an Employee: User clicks on Select Base dropdown, selects base, clicks on + Add an Employee button, landing on the Registration page for adding the role of the employee. 39. User selects either a start time or an end time, and clicks on Finish button, in the Set Working Hours page. 40. User selects an invalid start time and valid end time, and clicks on Finish button, in the Set Working Hours page. 41. Assuming a user has scheduled an enabled day slot in the set working hours, they cannot duplicate the same schedule to another disabled slot or multiple slots. 42. User attempts to set a schedule on the disabled working day slots, in the set working hours page. 43. METHOD 2: In Home Visit Schedule Setup, User selects the clinic, and the list of employees are displayed. And the selected employees are assigned to the selected clinic as well as clinic added using Method 1, is also added. 44. The user does not select any clinic so the flow would not move any further. 45. METHOD 3: In Home Visit Schedule Setup, user clicks Set Working Schedule, user can select a desired clinic from Select a Physio to view their schedule. Clinics added in both Method 1 and 2, would be assigned to the employee, including the ... 46. The user does not select any clinic so the flow would not move any further. 47. There will be a message on the screen that reads Schedule present if an employee's working day has already been scheduled and another business user wants to allocate that individual to their firm. The revised schedule will be applied to the emplo... 48. If multiple employees' working days are already scheduled and business user wants to assign those employees to their business, it will say Schedule present on the screen. If the user still choose those employees, the new schedule will take effec... 49. The new schedule will be the default for the selected employee if the working day of an employee is not scheduled and a different business wishes to allocate the employee to their business. In this case, it will not indicate Schedule present. 50. The user does not select any employee for their business so the flow would not move any further. 51. The user can view a summary of the schedule by selecting the base and the employees after the schedule and click on BACK TO CALENDER AND APPOINTMENT MODULE "326 A sub-module to keep track of any new requests submitted by staff members that are currently marked as pending,1. Check the admin user functionality to view the list of new assets and assets maintenance requests from employees 2. Evaluate if the admin user can approve/ reject the asset request 327A submodule to keep track of all the allocated assets to staff members with their allocation date estimated release and category/asset tag,1. Check the admin user functionality to view and download the list of the assets allocated to employees 328this tab is used to display annual salary history of employee.,"1. Confirm functionality of employee salary history. 2. Check that the Admin can see employee's Annual salary details with 'Emp Id', 'Emp Name' in the table format. 3. Validate the 'View Details' workability. 4. Examine the Gross Salary and Net Salary appear in the 'Annual Salary History' tab under the Appraisal module. 5. Confirm the Paid salary will show on the Annual Salary History screen under the 'Appraisal' module for the Processed records. 6. Make sure the Paid Salary will not show on the Annual Salary History tab under the Appraisal module for the Not processed records. 7. Examine the 'Month' and 'Year' dropdown are present on the Employee Salary Details screen. 8. Validate the admin can select the 'Month' and 'Year' in a duration. 9. Make sure the Employee Salary Details will apeear for the selected 'Month' and 'Year'. 10. Validate that the 'To' date cannot be set prior to the 'From' date. 11. Confirm the 'To' date can be set beyond the System Generated End Date. 12. Evaluate the functionality of 'Back' button from the Employee Salary Details page. 13. Examine the 'Back' button from the Annual Salary History screen. 14. Evaluate the Search functionality present on the Annual Salary History screen. 15. Ensure about the working of the pagination present on the Annual Salary History page. 16. Confirm the show entries functioning. 17. Ensure the appeared details on the screen when admin clicks on the paid salary column value. "329" Allow the Clinic Owner to add, edit and register the PP, PI, FDM by filling in their registration details. Once the doctor is registered on the application, they are unable to edit their profile information unless they are affiliated with a clinic","1. Roles that can register via Manage Employee whose auto-approval will be provisioned from Pheal Web: Practicing Physiotherapist Physiotherapy Internship/Observer-ship Front Desk Manager. 2. User selects a desired clinic from the Select Clinic dropdown list. 3. User attempts to select more than one clinic from Select Clinic dropdown list. 4. User does not select any clinic from the Select Clinic dropdown list. 5. Clinic is selected by default in the Select Clinic dropdown, the profile card of the respective employees of the clinic are displayed. 6. On selecting the desired clinic from the Select Clinic dropdown, the profile card of the respective employees of the clinic are displayed user clicks on the profile card of the employee. 7. On selecting the desired clinic from the Select Clinic dropdown, the profile card of the respective employees of the clinic are displayed user does not click on the profile card of the employee. 8. On clicking the Doctor's profile,information such as Attendance related informtion, analytics and appointment related information are enlisted. User can edit the profile or delete the employee. 9. If the user wishes to edit their profile, user can click on Edit Profile, the page will redirect to the Basic Information page from the registration module. 10. If the user chooses to delete employee, user clicks Delete Employee, a pop-up is displayed enquiring the user Are you sure you want to permanently delete employee_name from your practice? followed by a See Details button, and the user clicks on th... 11. The user clicks on Delete Employee, a pop-up is displayed enquiring the user Are you sure you want to permanently delete employee_name from your practice? followed by a See Details button, and the user does NOT click on the See Details button. 12. If the user chooses to see less of the information displayed after clicking See Details, the user can click on See Less. 13. The user clicks on the cross mark to stay on the Doctor's Profile. 14. The user clicks on Delete Anyway, and the employee can be deleted. 15. (INCLUDING BUSINESS) The Delete Employee button will not be visible to a business user. 16. User chooses a valid year and month from both the Select Year and Select Month dropdowns respectively. 17. User chooses an invalid year or month from the Select Year and Select Month dropdowns respectively. 18. User chooses to not select any year or month from the dropdowns. 19. User can keep track of the late appointments, User can select Details in the Late for appointments section of the Doctor's profile. 20. User doesn't click on the Details link for Late for appointments. 21. In Manage Employees, user can add employees,user clicks the +, fills the details using Add an Employee Manually and manages to successfully add an employee and assign a single clinic. 22. In Manage Employees, user can add employees, user clicks the +, fills the details using Add an Employee Manually and manages to successfully add an employee and assign multiple clinics. 23. The user lands on What role of employee are you adding?Where the user clicks on Physiotherapy Intern the basic information of a Physiotherapy Intern is displayed. Here, the user chooses to click the Select button, then further move on to registrat... 24. User Clicks Physiotherapy Intern,it lands to the What is your role? page, The user can also choose to click the arrow to the right, to view various roles and selects the Front desk manager role, the basic information of a front desk manager... 25. The user lands on What role of employee are you adding? Where the user Clicks Physiotherapy Intern, it lands to the What is your role? page, The user can also choose to click the arrow to the left, to view various roles and selects the Physiother... 26. User can click on + Add Photo, where the user would be able to upload their photo, it will redirect to your device from where the user uploads the photo in JPEG or PNG format. 27. User can click on + Add Photo, where the user would be able to upload their photo, it will redirect to your device from where the user uploads the photo that is not in JPEG or PNG format. 28. User can click on + Add Photo, where the user would be able to upload their photo, it will redirect to your device from where the user does not upload the photo at all. 29. The user clicks the change link, under Where do you work? Clinic, the page redirects to the Where do you work? page for the user's ease. 30. The user does not click, the change link, the user will not navigate any further remaining on the same page. 31. The user clicks the change link, under What is your role? Physiotherapy Intern, the page redirects to the Let's get to know what your role is in the clinic page for the user's ease of navigation. 32. The user does not click, the change link, the user will not navigate any further remaining on the same page. 33. Mandatory field: User clicks on Full Name field, enters the Full Name , including only the characters. 34. User clicks on Full Name field, enters the Full Name , including alphanumeric characters. 35. User clicks on Full Name field and does not enter the Full Name, leaves the field blank. 36. Mandatory field: User clicks on Email Address field, enters a valid email id. 37. User clicks on Email Address field, does not enter a valid email id. 38. User clicks on Email Address field, does not enter any email id. 39. Mandatory field: For the Mobile Number field, while selecting the country code,a dropdown list is displayed with the different countries, country codes and their respective flags. User enters a valid mobile number by selecting a valid country code.... 40. For the Mobile Number field, while selecting the country code,a dropdown list is displayed with the different countries, country codes and their respective flags. User enters an invalid mobile number by selecting a valid country code. 41. User does not enter any value in the Mobile Number field. 42. Mandatory field: By clicking on the checkbox for the notification updates or any promotional offers, the user receives offers on their WhatsApp application. 43. The user chooses not to select the checkbox for WhatsApp notifications 44. Mandatory field: For the Pin-code field, user enters a valid six-digit pin-code. 45. For the Pin-code field, user enters an invalid six-digit pin-code. 46. For the Pin-code field, user does not enter any value in the field. 47. Mandatory field: When the user clicks on the Date of Birth field, a calendar would be displayed from where the user can make a valid selection. Where the minimum age criteria is greater than or equal to 21 years; The date of birth should be less than... 48. When the user clicks on the Date of Birth field, a calendar would be displayed from where the user can make an invalid selection. 49. The user does not click on the Date of Birth field, and does select any date of birth. 50. Mandatory field: The user can click on the Gender dropdown, the user can make a valid selection. 51. The user does not click on the Gender dropdown and chooses not to make any selection. 52. Mandatory field: User clicks on Select Type of Cases You Treat dropdown, user chooses from a list of specializations by clicking on one or more checkboxes. 53. User clicks on Select Type of Cases You Treat dropdown, user chooses from a list of specializations by clicking on all the checkboxes or clicks Select all option from the list. 54. User does not select any specialization from the Select Type of Cases You Treat dropdown. 55. Mandatory field: User clicks on Assign Clinic dropdown, user chooses from a list of clinics by clicking on one or more checkboxes. 56. User clicks on Assign Clinic dropdown, user chooses from a list of clinics by clicking on all the checkboxes or clicks Select all option from the list. 57. User does not select any clinic from the Assign Clinic dropdown. 58. On clicking the Next Button, if any of the mandatory fields are invalid or skipped by the user, pop-ups will be displayed to fill the respective field. Only in case of valid scenarios the user would be able to navigate to the Next Page i.e. Education I... 59. As soon as the user moves from the Basic Information to the Education Information, the progress bar on the top of the page would be highlighted in yellow for the Basic Information page. 60. GRADUATION: Mandatory field: User clicks the University of Graduation field and enters the valid University. 61. User clicks the University of Graduation field and enters an invalid University. 62. User does not enter any value in the University of Graduation field. 63. Mandatory field: User chooses the valid course from the Course For Graduation drop down. The user must ideally select BPT Course. 64. User chooses the invalid course from the Course For Graduation drop down. 65. User does not select any course from the Course For Graduation drop down. 66. Mandatory field: User enters their valid year of graduation in the Year of Graduation field. 67. User enters an invalid year of graduation in the Year of Graduation field. 68. User does not enter any year of graduation in the Year of Graduation field. 69. Mandatory field: The user uploads a valid certificate of graduation in the Upload Certificate of Graduation in the acceptable JPEG,PNG or PDF formats. 70. The user uploads an invalid certificate of graduation in the Upload Certificate of Graduation in other unacceptable formats. 71. The user doesn't upload any file. 72. ADD POST GRADUATION: To add a Post Graduation, the user would click the + sign. User clicks the University of Post Graduation field and enters an valid University. 73. User clicks the University of Post Graduation field and enters an invalid University. 74. User does not enter any value in the University of Post Graduation field. 75. User chooses the valid course from the Course For Post Graduation drop down. The user must ideally select MPT Course. 76. User chooses the invalid course from the Course For Post Graduation drop down. 77. User does not select any course from the Course For Post Graduation drop down. 78. User enters their valid year of graduation in the Year of Post Graduation field. There should be a minimum gap of 2 years, in the Year of Post Graduation and Year of Post Graduation 79. User enters an invalid year of graduation in the Year of Post Graduation field. 80. User does not enter any year of graduation in the Year of Post Graduation field. 81. The user uploads a valid certificate of graduation in the Upload Certificate of Post Graduation in the acceptable JPEG,PNG or PDF formats. 82. The user uploads an invalid certificate of graduation in the Upload Certificate of Post Graduation in other unacceptable formats. 83. The user doesn't upload any file. 84. ADD CERTIFICATION: To add a Certification, the user would click the + sign. User clicks the University of Certification field and enters an valid University. 85. User clicks the University of Certification field and enters an invalid University. 86. User does not enter any value in the University of Certification field. 87. User chooses the valid course from the Course For Certification drop down. The user must ideally select MPT Course. 88. User chooses the invalid course from the Course For Certification drop down. 89. User does not select any course from the Course For Certification drop down. 90. User enters their valid year of graduation in the Year of Certification field. There should be a minimum gap of 2 years, in the Year of Certification and Year of Certification 91. User enters an invalid year of graduation in the Year of Certification field. 92. User does not enter any year of graduation in the Year of Certification field. 93. The user uploads a valid certificate in the Upload Certificate Proof in the acceptable JPEG,PNG or PDF formats. 94. The user uploads an invalid certificate in the Upload Certificate Proof in other unacceptable formats. 95. The user doesn't upload any file. 96. On clicking the Next Button, if any of the mandatory fields are invalid or skipped by the user, pop-ups will be displayed to fill the respective field. Only in case of valid scenarios the user would be able to navigate to the Next Page i.e. Set Passwor... 97. As soon as the user moves from the Basic Information to the Education Information, the progress bar on the top of the page would be highlighted in yellow till the Education Information page. 98. On clicking the Next button, user will land to the Set Password page, where user will enter an invalid password in the Password field. 99. Once the user sets password in the Passwordfield, user will confirm the password, by entering an invalid password in the Confirm Password. 100. The user clicks on the Complete Registration button and the completes the registration process. 101. On clicking the Next button, user will land to the Set Password page, where user will enter an either a valid or an invalid password in the Password field. 102. Once the user sets password in the Password field, user will confirm the password, by entering the a password in the Confirm Password, that doesn't match the Password field. 103. The user clicks on the Complete Registration button and the registration process is incomplete. 104. On clicking the Next button, user will land to the Set Password page, where user will NOT enter a password in the Password field. 105. User will NOT enter a password in the Confirm Password field. 106. The user clicks on the Complete Registration button and the registration process is incomplete. 107. On clicking the Next button, user will land to the Set Password page, where user will enter a valid password in the Password field. 108. Once the user sets password in the Password field, user will confirm the password, by entering the same valid password in the Confirm Password. 109. The user clicks on the Complete Registration button and the completes the registration process. 110. Post, successful registration, a Successful registration message will be displayed on the screen. Along with a Back to Login button, where the user clicks the button and the page navigates to the Login page. 111. Post, successful registration, a Successful registration message will be displayed on the screen. Along with a Back to Login button, where the user does NOT click the button and the flow would not move any further. "330 The admin can add a new User by filling the required details.,"1. To ensure that the admin has access to various Uers's and can make changes to existing Users or add new User within the system or availability of functionalities to do the same 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown 3. To verify the search functionality that filters displayed data based on the entered text, presenting only relevant information 4. To verify the functionality of the Add User button, ensuring that it displays a popup with the necessary fields to add a new User 5. Onclick the 'Add User' button should trigger the display of a pop-up window which contain a form with fields for specifying the name, company name, validity, clients, projects and other required details of the User to be added 6. Check whether the displayed data is filtered based on the entered text for search functionality of project dropdown which shows only the relevant data of projects. 7. To confirm that the checkbox properly responds to user interactions, such as selection and deselection, within the dropdown menu 8. To verify the functionality of the 'Add' button in the Add User pop up, ensuring that it successfully adds the user to the system when all required details are entered. 9. To ensure the functionality of the Cancel button in the Add User pop-up, ensuring that it cancels the process of adding a new User and closes the pop-up without saving any changes. 10. Verify next pagination button 11. Verify previous pagination button "331The admin can view the user details.,"1. Verify that clicking on the View button displays the detailed information or overview of the User. 2. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. "332 Admin can edit the details of the external User.,"1. To ensure the proper functionality of the Edit action button, allowing admin to modify the details of User. 2. To confirm the functionality of the Cancel button in the Edit action, allowing admin to discard any changes made to the User details and exit the edit mode. "333 Admin can delete the User from the system.,"1. To validate the functionality of the Delete action button for User, allowing the deletion of existing User from the system. 2. To ensure that the Cancel button in the Delete action allows admin to cancel the deletion process and close the delete confirmation popup. "334The heading should be displayed on the top of the home page. The image slide with the respective name should be displayed below the heading. Marquee must be displayed below to image slide.,"1. Ensure that the user gets directed to the Palkhi application's home page after clicking the Palkhi application (Android). 2. Make sure all the modules are present on the home page and they are properly aligned. 3. Ensure that the heading of श्री साईबाबा पालखी सोहळा समिती, पुणे at the top of the home page is properly displayed. 4. Make sure that the heading श्री साईबाबा पालखी सोहळा समिती, पुणे display with correct font & size on the top of the home page. 5. Make sure the images in the slide show are displayed in the specified order. 6. Ensure that the slide show transitions smoothly between images without any glitches. 7. Check that the respective names are correctly displayed below each image in the slideshow. 8. Ensure the marquee name display below to the image slide show. 9. Make sure that the scrolling of marquee name is continuously & smoothly. 10. Make sure that user can easily read the marquee name. 11. Ensure that the marquee name is aligned properly as per requirement. "335" The Application shall include a login feature that verifies the user's credentials and authorizes access to the application. After a successful login, the user will be redirected to the user dashboard page, where they can access the features and fu...","1. Confirm that the login page works properly with the correct Username and Password. 2. Examine the Eye icon's capabilities in the password field. 3. Use an inaccurate username and password to test the login page. 4. Use an incorrect username and correct password to test the login page. 5. With an authentic Username and a faulty Password, check the login page. 6. The login button should be verified with an empty username and password field. "336"This is the User's initial screen. The modules Timesheet Management System, Leave Management System, Notification, and Profile are all accessible to users through the User Home Screen.",1. Make sure that the Timesheet Management System card is available on the user's Home page. 2. Check the Leave management system card on the User homepage. 337"Timesheet Management allows the user to record their daily tasks. The user can login to the application. The user can mark their attendance by sliding the slider available on the timesheet management screen, i.e., their IN Time and OUT Time.","1. Check that swiping slider is available to add the in-time or out-time for the user. 2. Make sure that the Timesheet status is shown as per their color notations for the Unfilled and Submitted timesheet, Holidays, and Leave. 3. Examine the timesheet calendar which has shown the color notation on the calendar for unfilled, filled timesheets, and leave holiday dates. 4. Check that the History button is available on the TMS Home page for an overview of previously filled timesheets. 5. Using the Fill timesheet button, user can fill their work task details for the current date. 6. Using the back arrow on the Timesheet Management System screen, the user can redirect to the user's Home screen. "338" The user can log in to the application. The user can mark their attendance by sliding the slider available on the Timesheet Management screen, i.e., IN Time and OUT Time. The user can mark their IN time only once, but they can mark their OUT time multip...",1. Check the slider behaviorto see if the user swiped in the right direction for the work punch-in. 2. If the user wants to add their out time of work the user needs to swipe to the left direction. 339"The user will be able to fill out a timesheet. The user can add multiple tasks to the list, edit the added tasks, and submit all tasks together.","1. Using the Fill Timesheet button, the user can add the daily work task for the current date. 2. Check user can add multiple tasks for any particular day. 3. Using the Back arrow on the top left corner user can navigated to the Timesheet management system screen. 4. The user can fill up the timesheet for a specific date by selecting the unfilled date from the calendar. 5. Check that, when a user clicks the add to list button on the form without filling out any fields. 6. Examine that if the user adds all mandatory fields only and clicks on the add to list button. 7. Check that user can edit the task, which is added first, for some changes using the edit icon. 8. Using the delete icon, the user can delete a task that has been added to the list but not submitted. "340" The user will be able to view the timesheet history. The user can get an overview of the filled-out timesheet through the history screen. The user can check the status of the filled timesheet, i.e., saved, Submitted, Approved, or rejected.","1. Check the timesheet which has been submitted, which are shown the submitted status in green color with all added details. 2. From the admin approved timesheets are shown in the history with the related details and the status, and color. 3. The Rejected status with the red color and the required, which has shown for the admin rejected timesheets. 4. Without adding any work timesheet, the user checks the history on the timesheet management system screen. "341"This is the landing screen for the admin, which allows the admin to see the requests for submitted timesheets, and Admins can Approve or reject timesheet requests.","1. Check the employee's timesheet card, which has shown details about added task. 2. Check the behavior of the Approve button when the admin clicks on any employee timesheet request as accepted. 3. Examine the Reject button work ability when admin rejects the work timesheet of employee. 4. Evaluate that If the admin wants to check the particular employee timesheet, then using the search bar and entering the name or employee ID, the admin can easily check the details. 5. Check the details by filtering the timesheet request, between today's, this week's, and this month's. "342" The user can have an overview of notifications for today and this week for filling out their pending timesheets. Also, get notified about the status of the leave request, whether it is approved or rejected by the administrator.","1. Check when user did not fill timesheet for a day, then the next day notification for the pending timesheet appears. 2. Examine that If the admin rejects the leave request, then a notification will be received by the user. 3. Evaluate that the user received the notification for admin approved leaves. "343" On the profile screen, users can see their profile photo, their respective designation, staff ID, email ID, and the logout button to get logged out of the application.","1. Check the user's profile details shown on the profile screen. 2. Examine the Logout button, the user can logout from their account. "344 Both the admin and the user must log in using the admin login information and be logged into the admin and user dashboards.,"1. Examine the application accepts the valid credentials. 2. Examine the outcome when the Login button is clicked while the User ID and Password fields are both blank. 3. Examine the outcomes and click the Login button when the User ID field is left empty and the Password field is filled in. 4. Validate the login functionality when the user enters the User ID and keeps the password field blank, 5. Check the response when an inaccurate User ID and Password are entered and the Login button is clicked. "345" The menu tray on the dashboard will allow users to access different submodules. The Dashboard should include the sections listed below:Recent events, Upcoming Event For the Month, At a Glance, Pie Chart for SO status,Number of SO according to Custome...","1. Validate the user can see the all summary of all modules under the dashboard. 2. Verify the Customer , Sales Order and Invoice modules are present by counting the number of them inside the At a glance card. 3. Validate the Customer , Sales Order, and Invoice module inside the At a glance card are clickable. 4. Validate the Pie Chart for SO Status with the Active and Renew status is present under the Dashboard module. 5. Validate the user can view the 'SO' and 'Amount' for the Active and Renew status. 6. Validate the columns for the Invoice for the month datatable. 7. Validate the sorting functionality for the Invoice for the month . 8. Validate the search functionality. 9. Validate the Upcoming Event is present under the Dashboard module. 10. Validate the View More button is present for the each customer. 11. Validate the user can click on the View More button. 12. Validate the events appear for the current month. 13. Examine the counting of a new inserted record will be increased in the At a Glance card of the Module below. 'Customer', 'Sales Order', 'Invoice'. 14. Verify the admin can create the invoices from the Invoice for the month data table. "346Admin will login using the valid credentials. Admin need to enter the correct ID and Password to get logged in to the application.,1. Ensure that the login page works properly with the using appropriate Username and Password. 2. Check the login page with an inappropriate Password and an inappropriate Username. 3. Evaluate the login page with an invalid Username and valid password. 4. Check the login page with a valid Username and an invalid Password. 5. Evaluate the functionality of the 'Eye' icon' in the password field. 6. To Examine the login button with a blank username and password. 347"This is Admin's home page. The dashboard provides Admin to see the below cards, i.e., Apply leave andApprove Leave. Admin has the authority to approve or reject leave requests.","1. Observe that the names, buttons, cards, quotes, and images that are present on the Admin homepage are visible. 2. Examine that the font size, color grades, and alignment of the Admin dashboard are visible as per the design document. 3. Evaluate the Approve Leave card on the admin home screen, from which the admin can approve or reject the leave request. 4. Check that Admin has the Apply Leave, Fill Timesheet, and Approve Timesheet cards available on the dashboard. "348" This is the User's initial screen where the modules Timesheet Management System, Leave Management System, Notification, and Profile all can be accessible to the user through the User Home Screen.","1. Ensure that the names, buttons, cards, quotes, and images that are present on the User homepage are visible. 2. Examine that the Font size, color grades, and alignment of the User homepage are visible as per the design document. "349 Manages with the leaves of the employees where user can apply for leave and view the history for applied leaves.,"1. Ensure that the Leave Management System card is present on the User dashboard with a title, images, and icons. 2. Check the functionality of the LMS card on the User homepage after clicking on it. "350" User logs-in into the application, then user can navigate to the leave management system screen by clicking on the LMS card. User can see Balance Planned leaves, Balance Casual leaves, and all the applied leaves on the screen. Also the user will be able...","1. Ensure that the Holiday Calendar, Apply Leave, and History buttons and images that are present on the LMS homepage are visible. 2. Examine that the Font size, color grades, and alignment of the LMS homepage are visible as per the design document. "351" The user logs-in into the application, then user can navigate to the leave management system screen by clicking on the LMS card then user can apply for leave.","1. Make sure that the apply leave screen contains all necessary fields such as leave from date, leave to date, leave type, and the reason for leave, etc. 2. Examine the functionality of the 'From and To' date field of the apply leave. 3. Ensure that the user may select the option to type of leave they want to apply from the dropdown list for leave type. 4. Evaluate the Reason box Text field on the Apply Leave Screen's functionality. 5. Verify the reason box on apply leave page accepts up to hundred characters as per requirement. 6. Examine the 'Submit button' functionality by letting all the fields blank. 7. Ensure that the submit button functionality by entering valid data in all fields. 8. Examine that when a user fills out all mandatory information and hits the reset button, all fields on the Apply Leave screen are reset. 9. Verify the functionality when the user-filled From date is greater than the To date. 10. Make sure that after clicking the back arrow on the Apply Leave page, the user returns to the Home screen of the Leave Management screen. 11. Make sure functionality of the sandwich leaves. 12. Ensure that when a user requested the PL or CL leaves for a few days and the request is approved by the admin, the number of those days is subtracted from the total PL or CL leave count displayed on the LMS home screen. 13. Check when a user requests for PL or CL it should get deducted from the PL or CL total leave on the LMS home screen. 14. Observe the changes in total leave on the LMS home screen after every working day. "352"User can have an overview of the applied leaves for the current month. Also user can check the status of the applied leaves i.e., Awaiting, Approved, Rejected. User can see the date, type of leave, reason and number of days the leave is applied.","1. Ensure that the names, buttons, cards, boxes, arrows and images that are present on the LMS History page are visible. 2. Examine that the Font size, color grades, and alignment of the LMS History page are visible as per the design document. 3. Make sure that the History page contains the Pending/ Approved/ Rejected status of the leaves. 4. Check the functionality of the back button arrow on the LMS module history page. "353"Admin login into the application and can navigate to the Admin Home screen by clicking on the Approve Leave card. Admin can be able to see the leave requests, approve or reject the leave requests, view the updated status of leave requests on the screen,...","1. Make sure that the Leave request list of the employee, Leave request status, search bar, and dropdown are present on the Approve leaveHome screen(Admin). 2. Examine that the Font size, color notations, and alignment of the Approve leaveHome screen are visible as per the design document. 3. Check the functionality of the back button arrow on the Approve leavepage (Admin). 4. Make sure that the apply leave screen contains all necessary fields such as leave from date, leave to date, leave type, and the reason for leave, etc. 5. Examine the functionality of the From and To date field of the apply leave. 6. Ensure that the admin user may select the option to type of leave they want to apply from the dropdown list for leave type. 7. Evaluate the Reason box Text field on the Apply Leave Screen. 8. Verify the reason box on apply leave page accepts up to hundred characters as per requirement. 9. Examine the Submit button functionality by letting all the fields blank. 10. Ensure that the submit button functionality by entering valid data in all fields. 11. Examine that when a user fills out all mandatory information and hits the reset button, all fields on the Apply Leave screen are reset. 12. Verify the functionality when the user-filled From date is greater than the To date. 13. Make sure that after clicking the back arrow on the Apply Leave page, the user returns to the Home screen of the Leave Management screen. 14. Make sure functionality of the sandwich leaves. 15. Ensure that when a user requested the PL or CL leaves for a few days and the request is approved by the admin, the number of those days is subtracted from the total PL or CL leave count displayed on the LMS home screen. 16. Ensure that the names, buttons, cards, boxes, arrows and images that are present on the Apply leave History page are visible. 17. Examine that the Font size, color grades, and alignment of the Apply leave History page are visible as per the design document. 18. Make sure that the History page contains the Pending/ Approved/ Rejected status of the leaves. 19. Check the functionality of the back button arrow on the Apply leave module history page. 20. Evaluate the Optional holiday list displaying the total optional holidays with the respective holiday image for the specific date. 21. Check for the Fixed holiday list displaying the total fixed holidays with the respective holiday image for the specific date. 22. Ensure the All holiday list is displaying the total All holidayswith the respective holiday image for the specific date. 23. Check the functionality of the Approve leave card on the admin home screen after clicking on it. 24. Check to see that the leave requests are showing according to the current status of the request. 25. Verify the functionality of the search text field in the Approve Leave home screen (Admin). 26. Evaluate the dropdown button functionality on the Approve Leavehome screen (Admin). 27. Ensure the functionality of the Approve button on the Approve Leavehome screen (Admin). 28. Ensure the functionality of the Reject button on the Approve Leavehome screen (Admin). 29. Examine the functionality of the Reset button by filling in all the fields of Apply Leave form with the correct data. "354" User can view the list of Holidays i.e., All/Optional/Fixed Holidays.",1. Evaluate the 'Optional' holiday list displaying the total optional holidays with the respective holiday image for the specific date. 2. Check for the 'Fixed' holiday list displaying the total fixed holidays with the respective holiday image for the specific date. 3. Ensure the 'All' holiday list is displaying the total All holidayswith the respective holiday image for the specific date. 355 Users can have an overview of notifications for today and this week for filling their pending timesheets. User also get the notification for the leave request status whether it is approved or rejected.,"1. Examine that if the user has applied for a leave, he/she gets a notification if the applied leave is approved or rejected. 2. Ensure that the user got the notification when applied for the leave. 3. Check that the notification disappears from notification page after 7 days. "356 A session management system is a software component or framework that helps manage and track user sessions in a web application or system. It is responsible for maintaining user state and providing a seamless experience during the user's interactio...,"1. Validating the session tokens, for the same user and for different users where possible to analyze and ensure randomness exists to stop session forging attacks. 2. Check for the Secure attribute is set for the cookie. 3. Verify Encryption of Session variables and poor tokens management for every HTTP requests. 4. Validate for GET & POST vulnerabilities regarding exposure of session variables in proxy or firewall logs. 5. Check the transportation vulnerabilities and methods' security. 6. Check for existing HTML tags that can cause immediate access to DOM resources such as <img>. 7. Validate the user logout interface as a visual indication for intended uses. 8. Validating interval-based session timeout for balanced security and usability. 9. Validate for server-side session termination of the user session mitigating the cached based back-refresh attack. 10. Verify for the JWTs expose sensitive information. 11. Verify for the JWTs signature is tampering/modified attack. "357" In the profile screen user will be able to see their profile photo their respective designation, staff id, Joining date, and the logout button to get logged out of the application.","1. The user information like Profile photo, name, designation, employee id and Joining date is shown on the profile screen. 2. Examine the Logout button, which has been shown on the profile screen, Using this button, users can logout from their account. "358 Input validation testing is a critical aspect of software testing that focuses on assessing the effectiveness and robustness of input validation mechanisms within an application or system. The goal of input validation testing is to identify vulnerabilit...,"1. Check the variables reflected in responses, as well as the input they accept and the encoding that is applied on return. 2. Verify the stored input variables that are reflected on the client side and verify the input they accept as well as the encoding that gets applied on return. 3. Checking injection points, the parsing method used, and trying bypassing input filters using HPP. 4. Validating SQL injection sites, the severity of the injection, and the level of access that can be obtained by it. 5. Verifying and assessing the command injection points with special characters. 6. Check for SSRF injection points and test if the injection points are exploitable. "359" Error handling refers to the process of identifying, analyzing, and exploiting errors or vulnerabilities within a system or application. Penetration testers intentionally trigger and manipulate error conditions to uncover security weaknesses and potenti...",1. Validating existing error output (i.e.: Random files/folders (400 series) and analyzing the different output returned. 2. Check if the application reveals detailed error messages containing sensitive data or system information. 3. Verify the prevention of detailed error messages that disclose sensitive information by entering invalid or malformed data. 4. Verify the prevention of server and application stack trace leakage by manipulating inputs to trigger exceptions. 360" Penetration testers analyze the cryptographic mechanisms employed, such as encryption algorithms, key management, random number generation, and secure protocols, to assess their effectiveness and security. By exploiting cryptographic failures, testers a...","1. Validate the server configuration (Identify weak ciphers/protocols (ie. RC4, BEAST, CRIME, POODLE) 2. Checking the digital certificate's cryptographic strength and validity. 3. Verify that the TLS security is not by passable and is properly implemented across the application. 4. Verify encrypted messages that rely on padding and attempt to break the padding of the encrypted messages to analyze the returned error messages. 5. Check for sensitive information(Information used in authentication) transmitted through the various channels. 6. Check for weak encryption or hashing uses and implementations. "361" Business logic in penetration testing refers to the critical set of rules, processes, and workflows that govern the operations and functionality of a software application from a business perspective. During penetration testing, business logic vulnerabil...","1. Validate all checks are occurring on the back end and can't be bypassed also check data injection points. 2. Check for user-level access to modify or read that data in each component. 3. Validate the defenses in place and verify protect the system against bypassing techniques (in-built self-defense: Changed responses, Blocked requests, Actions that log a user out or lock their account) 4. Verify that the unwelcomed file types are rejected and handled safely and check for Content-type or file extension. 5. Verify that file batch uploads are secure and that any bypass against the set security measures. 6. Test to upload the malicious files to the application and determine whether it is accepted and processed. "362"In payroll systems, the Employee Master refers to a comprehensive and centralized repository that stores essential information about employees within an organization. It serves as a foundational component of the payroll application and contains key empl...","1. Ensure that when the user clicks on the Personal Details tab, which is located under the Employee Master tab, the personal details are displayed. 2. Examine that the contact information is displayed when the user clicks on the Contact Details tab within the Employee Master tab. 3. Confirm that when the user clicks on the Passport, PAN, Aadhaar & Other Card Details tab, the corresponding information related to those cards is displayed. 4. Examine that the Employee Master's tab's corresponding section and fields are displayed with the correct alignments, spellings, font sizes, and font families. 5. Examine that the user's qualification information is displayed if they click on the Qualification Information tab. 6. Confirm the show entries functionality is available and ensure that when the user selects an option from the Show Entries dropdown, the data table updates accordingly by displaying the specified number of entries per page. 7. Check to see if the search feature displays the right results if the user enters any text in the field. 8. Ensure that the user can utilize the Next pagination feature to navigate to the next page and view additional entries. 9. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 10. Examine that the Qualification Information's tab corresponding section, fields, and buttons are displayed with the correct alignments, spellings, font sizes, and font families. 11. Determine that the user's other details are showing once click the Other Details tab. 12. Confirm the show entries functionality is available and ensure that when the user selects an option from the Show Entries dropdown, the data table updates accordingly by displaying the specified number of entries per page. 13. Check to see if the search feature displays the right results if the user enters any text in the field. 14. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 15. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 16. Examine that the Other Detail's tab corresponding section, fields, and buttons are displayed with the correct alignments, spellings, font sizes, and font families. "363"Users can view bank details. By incorporating the bank functionality into the payroll system, Employees can streamline the salary payment process","1. Ensure that the salary bank details are displayed once the user clicks on the Bank tab which is under the Employee module. 2. Examine that the Bank's tab corresponding section and fields are displayed with the correct alignments, spellings, font sizes, and font families. "364 An employee can view their Permanent address as well as their local Address under the Employee module.,"1. Make sure that to view the current address details of the user, the Local Address section is present under the Address tab. 2. Confirm that to view the permanent address details of the user, the Permanent Address section is present under the Address tab. 3. Examine that the Address's tab corresponding section and fields are displayed with the correct alignments, spellings, font sizes, and font families. "365 An employee can access their total Experiencewith the designation and company-related information.,"1. Evaluate that the user's employment details are showing once click the Employment tab. 2. Examine the dropdown menu with options available provided for the Show Entries capability to display many entries on a single page. 3. Check to see if the search feature displays the right results if the user enters any text in the field. 4. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 5. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 6. Examine that the Employment's tab corresponding section, fields, and buttons are displayed with the correct alignments, spellings, font sizes, and font families. "366 An employee can view their family Details details under the Family Members tab.,"1. Evaluate that the user's family details are showing once click the Family Members tab. 2. Examine the dropdown menu with options available provided for the Show Entries capability to display many entries on a single page. 3. Check to see if the search feature displays the right results if the user enters any text in the field. 4. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 5. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 6. Examine that the Family Members tab's corresponding section, fields, and buttons are displayed with the correct alignments, spellings, font sizes, and font families. "367"The user of the invoice management system (IMS) has access to Add, Edit, Delete, Search Customers, Sidebar, Scroll Bar, etc. as needed by each Sub-Module.",1. Validate the columns of customer module. 2. Validate the Actions column has Edit and View button. 3. Validate the Search functionality 368" When the user selects the “View” option from the dropdown, the user should be able to see all the details related to the customer selected as a popup.","1. Validate the Edit Customer button is clickable. 2. Validate the Contact, Billing, Shipping and More is present inside the edit functionality. 3. Validate the Customer, Email,Phone,Contact and Last Name is present inside the contact tab. 4. Validate the Save and Cancel button is clickable. 5. Validate the Addressline 1,Addressline 2,City,Postal/ZIP Code,Country,and Province/State. field is present inside the Billing tab 6. Validate the Save and Cancel button is clickable under the Billing tab. 7. Verify that the address-related fields are present and the Same as billing address checkbox is enabled. 8. Validate the Save and Cancel button is clickable under the shipping tab. 9. Validate the Account Number,GSTIN,Mobile,PAN,Website,Internal Notes. are present inside the More tab. 10. Validate the Save and Cancel button is clickable under the More tab. "369"When we click the Save button, the Edit Customer feature is verified.",1. Validate the View button is clickable under the Customer module. 2. Validate the Customer Details can be visible to the user. 370" The employee module maintains a centralized database or directory to store employee information. It focuses on managing employee-related information and activities. This includes capturing essential information, setting up payroll profiles, defining com...","1. Make sure 'Personal Details' sub-tab functionality. 2. Confirm admin can only view the 'Personal Details' of an employee and it's not editable. 3. Examine the Contact Details functionality. 4. Evaluate admin can only view 'Contact Details' of employees, which are not editable. 5. Ensure the Passport, PAN, Aadhaar & Other Card Details functionality. 6. Validate the admin can only view 'Passport, PAN, Aadhaar, & Other Card Details, which are not editable. 7. Verify the 'Qualification Information' sub-tab functionality. 8. Make sure that the admin can only view Qualifications Information, which is not editable. 9. Examine the Other Details functionality. 10. Confirm admin can only view 'Other Details' of employees, which are not editable. 11. Confirm when admin opens the 'Employee' module it contain employee's personal details, bank detail, address, employment, Exemption, and family members information. 12. Evaluate 'Address' sub-tab functionality. 13. Confirm that the admin can only view ' Address' information of employee's and it's not be editable. 14. Examine the fields for the Local Address are present Under the Address tab. 15. Make sure that the Local Address fields are not editable. 16. Examine the fields for the Permanent Address are present Under the Address tab. 17. Verify that the Permanent Address fields are not editable. 18. Confirm 'employment ' sub-tab functionality. 19. Ensure admin can only view ' Employment' information and it's not be editable. 20. Examine the 'Family Member' sub-tab functionality. 21. Confirm that the admin can only view ' Family Member ' information and it's not be editable. "371" The user should be able to add, view, edit and delete sales order. The user should be able to add milestones to sales order and should also have functionality to filter and view different purchase orders accordingly.","1. Validate the Sales Order dashboard is visible to the user. 2. Validate the Milestone Button is clickable. 3. Validate the Add SO button is clickable. 4. Validate the records count for the SO's is appear on the sales order dashboard. 5. Validate the All Customer dropdown functionality. 6. Validate the From, To, and Search functionality. 7. Validate the Columns for the Sales Order. 8. Validate the Action column has button for each records. 9. Validate that the user can view the PO under the PO column. 10. Validate that the user can click on 'Milestone' button. 11. Validate the Milestone screen. 12. Validate the All Customers functionality. 13. Validate the From, To, and Search functionality. 14. Validate the Milestone data table. 15. Validate the Milestone with View , Edit and Delete buttons. 16. Validate the View Milestone screen. 17. Validate that the all fields is noneditable on the View Milestone screen. 18. Validate the Edit Milestone screen. 19. Validate the columns on the Edit Milestone screen. 20. Validate the all columns is editable except the Milestone column. 21. Validate the delete functionality. 22. Validate the Reset and Submit button. 23. Validate the Delete button inside the Action column. 24. Validate user is able to delete 'Milestone' by clicking on delete button. 25. Validate that the Add PO button is clickable to the user. 26. Validate the New SO screen opens after clicking on Add PO button. 27. Validate the Add a Customer tab on the New SO screen under the Sales Order. 28. Validate that the user can fill the SO form under the Sales Order. 29. Validate user is able to add 'Item' using the 'Add an Item button. 30. Validate the user ca change the currency by clicking on the currency tab. 31. Validate the submit and cancel button. 32. Validate user is able to create 'Sales Order' by entering all the valid details in mandatory fields and non-mandatory fields. 33. Validate if user is able to create 'Sales order' by just entering non-mandatory fields. 34. Validate if user is able to select the Customer from 'Add a customer' functionality and then that Customer Details are displayed. 35. Validate if user is able to create 'Sales order' by without selecting 'Customer'. 36. Validate 'Sourcing manager Email' accepts valid input Email from the user. 37. Validate 'Requester Email' accepts valid input Email from the user. 38. Check if dropdown of 'Payment Terms' is displayed on the screen, when user clicks on 'Select payment terms'. 39. Check if 'No of Milestones' field accepts only Numeric data, and that many milestones are created. 40. Validate 'GST Number' field accepts valid GST number as per user requirement. 41. Validate if user is able to upload PO. 42. Validate user is able to select the SO status from the dropdown of 'SO Status' according to the status. 43. Check if 'Please enter item name' popup is displayed on screen when Item no is not added. 44. Check if user can select different currency from the Currency dropdown, and accordingly the amount is displayed of the 'SO'. 45. Check if ' SO added Successfully' is displayed on screen when user submits the SO. 46. Validate if user is able to add that number of milestones which are filled in in SO detail. 47. Validate user is able to Add milestone by clicking on 'Add an item'. 48. Validate 'Your milestone limit has been reached.' is displayed if the number of Milestone has reached limit. 49. Validate if 'Please fill out this field' is displayed when user directly clicks on Submit button without entering 'Item name', 'Description', 'Amount' & 'Date' in the Milestone. 50. Validate when user submits the Milestone by clicking on 'Submit' button 'Milestone Added Successfully' is displayed on screen. 51. Validate Calendar is displayed on screen attached to 'From' & 'To' date selection textbox when user clicks on it. 52. Validate the Edit SO functionality present on the 'Sales Order' module. 53. Validate the admin can edit the SO using the Edit SO functionality. 54. Verify the admin can view the edited SO. 55. Verify the Invoice for SO NO. screen appear when admin click on any SO. 56. Validate the count of the milestone is displayed in below format. Total Milestone', Achieved Milestone, Balanced Milestone. 57. Verify the below columns are present on the Invoice for SO.NO. screen. Status, Due Date, Invoice#, Customer, Total, Amount Due, Actions 58. Validate the admin can only view the Invoices by clicking on view button. "372" The Activity Log is visible on the User module screen, Admin can click on the Activity Log, With a click, the admin can view the activity of the user, it displays the list of client names, project, date, and activity if user has visited or downloaded an...","1. To confirm that the 'Activity Log' hyperlink is clickable and leads the admin to the activity log page in the Users module 2. To examine whether the admin can view the activity of clients, including 'visited' or 'downloaded' actions, along with the associated project and client details "373" Admin will be able to add, edit, view, and delete cash voucher for expenses","1. Validate the 'Cash voucher' sub tab which navigates user to Cash voucher screen 2. Validate Cash Voucher screen which displays list of active vouchers 3. Validate the search box used fetch required voucher from list 4. Validate the 'Show Entries' dropdown to display enlarged list of Vouchers 5. Check to see all of the Cash Voucher screen's data cards and buttons, as well as their labels, are placed correctly. 6. Verify that the 'Cash Voucher' screen works with various screen resolutions. 7. Check functionality of '+ add Cash Voucher' button 8. Check the '+ Cash voucher' pop-up to determine if the user may add a new category by entering the necessary information. 9. Check the functionality of the Edit icon. 10. Check the functionality of the Delete icon. 11. Check the functionality of the View Action button. "374" It shall have 3 sections naming Unpaid, Draft, Paid and All Invoices having List of Invoices on which different Actions can be performed, Overdue mount will be displayed, Due within next 30 days, Average time to get Paid and Create Invoice Button to cre...","1. Validate the Invoice module is clickable. 2. Validate the Invoice dashboard screen. 3. Validate the Excel, Upload Excel File, Create an Invoice and Upload buttons are clickable. 4. Validate the user can create the invoice using the Create an Invoice button. 5. Validate the Total and 'Due amount', which appears on the Invoice dashboard. 6. Validate the All Customers dropdown. 7. Validate that All Statuses has dropdown functionality. 8. Validate the From, To, and Search functionality. 9. Validate the Unpaid, Draft, Paid, and All Invoices tabs under the Invoice module. 10. Validate the columns for the invoices customer. 11. Validate the Company details with the Business Address and Contact Details. 12. Validate the Add Customer button on the New Invoice screen. 13. Validate the user can enter the invoices details on the New Invoice screen. 14. Validate the columns on the New Invoice screen. 15. Validate that the user can select the tax using Select a Tax dropdown. 16. Validate the user can add multiple item. 17. Validate the Save and Continue button. 18. Validate the user can View,Edit,Duplicate,Export as PDF,Print and Delete the invoices. 19. Validate the user View the invoice using the View button inside the Action column. 20. Validate the user can Edit the invoice. 21. Validate the user can duplicate the invoice. 22. Validate the user can delete and print the invoices. 23. Validate user is able to search the invoice by using Search functionality. 24. Validate if user is able to edit invoice by clicking on 'Edit Invoice' option. 25. Validate 'Send this Invoice' popup is displayed when user clicks on 'Send Invoice', where user can enter 'Mail' of receiver to which mail of Invoice has to be send, and also send a description message about the invoice. 26. Validate when user clicks on 'Preview as a customer' present on More actions dropdown the invoice is displayed on the screen as a customer preview. 27. Validate if status of Created invoice is 'Draft.' 28. Validate approved Draft by user is displayed on 'Invoice page' in Draft status sheet. 29. Validate if user can filter the invoices by selecting status from 'All Status' dropdown as ' All status', 'Draft', 'Unsent', 'Sent','Partial , Paid,'Overdue' in the invoice page. 30. Validate whether 'Invoice number' is editable. 31. Validate when user deletes Draft invoice 'Invoice deleted successfully!' popup is displayed on screen. 32. Validate when user clicks on 'Send' button, 'Send This Invoice' popup is displayed on screen and check if user can fill the details and send the invoice. 33. Validate when user clicks on 'Send a reminder' than send a 'Payment Reminder' popup is displayed on screen and user can fill the required details and then send reminder. 34. Validate when user clicks on 'Approve' button for invoice then Invoice of approved invoice is displayed on screen. 35. Validate if user is able to send the receipt of the Payment that is recorded. 36. Validate whether correct milestone and correct number of milestones is displayed on screen for selected SO when user selects that SO/PO number. "375" Create an Invoice, and check if they are displayed in the table where they are filtered in 'Unpaid', 'Draft', 'Paid ' & ' All invoices' according to their status.","1. Validate newly added invoices are added in Draft status table where user can Approve draft. 2. Validate approved drafts are present in Unpaid list of invoices. 3. Validate Paid invoices are displayed in 'Paid' filter status. 4. Validate when user clicks on 'All Invoices' filter, all the invoices list is displayed below. "376"The system should provide the admin with the ability to raise service tickets for themselves and for New Hires. The admin should be able to select the request type, which includes options for New, Maintenance, and New Hires.","1. Confirm that by clicking on the Service Request module, the list of submodules appears on the sidebar "377" The Admin has the ability to raise various types of service requests, including new service requests, maintenance requests, and new hire requests. This system will facilitate efficient communication and workflow management, ensuring that the appropriate...","1. Evaluate that by clicking on the Raise Request, the admin navigates to the Raise Request page 2. Click and check the functionality of breadcrumbs present on the page 3. Confirm that, the admin can raise the New Request by filling the necessary fields 4. Validate the functioning of Submit button without filling mandatory fields 5. Make sure that the admin can raise the service tickets for the new joiners by selecting the request type as New Hire 6. Validate that by selecting selection status and joining date the list of Hire details appears and source of the data is Onboarding Application 7. Ensure that selected number of entries from the dropdown must be appear only 8. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries appear only 9. Verify the functionality of Search textbox by entering invalid data in that, the error message appear on the screen 10. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 11. Validate that by clicking on pagination buttons admin user is navigating to the respective page 12. Validate the functioning of Submit button without filling mandatory fields 13. Verify that all data related to self-raised request details are displayed accurately in the data table within the Requested History container. 14. Ensure that selected number of entries from the dropdown must be appear only 15. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries appear only 16. Verify the functionality of Search textbox by entering invalid data in that, the error message appear on the screen 17. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 18. Validate that by clicking on pagination buttons admin user is navigating to respective page 19. Ensure that by clicking on the Request ID the pop-up with Asset Details appears on the screen "378" The New Customer is visible on the User module screen, Admin can click on the New Customer, With a click, the admin can view a list of new customers and their details.","1. To confirm that the 'New Customer' hyperlink is clickable and leads the admin to the New Customer screen in the Users module 2. Clicking on the 'New Customer' hyperlink successfully redirects the admin to a new page or opens a modal window/form for adding a new customer. 3. To ensure the functionality of the Cancel button in the Add Customer pop-up, ensuring that it cancels the process of adding a new Customer and closes the pop-up without saving any changes. 4. To verify the functionality of the 'Add' button in the Add Customer pop up, ensuring that it successfully adds the customer to the system when all required details are entered "379"In this phase, checking the application's business logic to identify any vulnerabilities that could be exploited. This includes testing for business logic flaws.",1. Validate that all checks are occurring on the back end and can't be bypassed & test to break the format of the expected data and the application behavior. 2. Check for user-level access to modify or read. That data in application which have not access to user for read or modify. 3. Verify that the unwelcomed file types are rejected and handled safely and check for Content-type or file extension. 4. Test to upload the malicious files to the application and determine whether it is accepted and processed. 5. ghjk o8765 380All invoice images of purchased stationery products is viewing properly after entering Stationery Invoice module.,"1. Check whether the admin clicks on the Invoice Stationery module, it will display invoice images of stationery data along with their invoice number. 2. Examine the functionality of the Invoice module's Search field' to search the invoice added while purchasing the stationery. 3. Ensure that after hovering the mouse over the image, view icon gets visible, and when the admin clicks on view icon, image will display in full size. 4. Observe that the tabs, texts, and font style of text that are present in the Invoice Stationery module are properly aligned. 5. Observe that each tab, text, font style, and field that are present on Invoice Stationery module are properly aligned. 6. Admin is able to click on download icon and ensure that selected 'Invoice' is downloaded. 7. When an admin clicks on the close icon (cross icon),' the image closes, and the admin is redirected to the previous page. "381All invoice images of purchased housekeeping products is viewing properly after entering housekeeping Invoice module.,"1. When the admin clicks on the 'Invoice Housekeeping' module, it displays the invoice image of housekeeping details along with the invoice number. 2. Examine the functionality of the Invoice module's Search field' to search the invoice added while purchasing the housekeeping item. 3. Confirm that after hovering the mouse over the invoice image, view icon gets visible, and when admin clicks on the view icon, invoice image is displayed in full size. 4. Observe that each tab, text, font style, and field that are present in the invoice housekeeping module are properly aligned. 5. Ensure that the Download' icon functionality for invoice housekeeping module: Admin will click on download icon, and the image will download in the default system's browser. 6. On the view close window functionality for invoice housekeeping module, admin will click on the cross icon, image will close, and admin will be redirected to the previous page. "382Admin user will check history of stationery and housekeeping products which are allocated to employees and offices as well as see the number of issued product and details of the product.,"1. Check that the admin clicks on the issued history tab to view stationery and housekeeping history details on issued history page. 2. After clicking on 'stationery tab' in the Issued History module, ensure that admin can access the stationery tab and view the issued stationery history details. 3. Observe that each text and field that are present in the issued history module is properly aligned. 4. Check that the admin can select the Show entries option from the dropdown list. 5. Check that admin can select year and month from the calendar dropdown to see that particular month's history. 6. Make sure that admin has gone to the next page or previous pages after clicking on the next and previous navigation arrows. 7. Confirm that after clicking on 'housekeeping' tab in the Issued History module, admin may see the allocated housekeeping history details by clicking on the housekeeping tab. 8. Ensure that the admin can see issued stationery product details in tabular form after clicking on the Stationery tab in Issued History module. 9. Check that admin can see allocated housekeeping product history details in tabular form after clicking on the Housekeeping tab in Issued History module. 10. Confirm that the issued history details of stationery products excel file has downloaded in the system's browser after clicking on the Export icon. 11. Check that the alignment of all fields, texts, and fonts that are present in the Issued History module is proper. "383" The admin user will look up the history of items that have been purchased from the store. Admin user will check the quantity of products purchased, their prices, and other information.","1. Examine that admin can click on the purchased history tab and open particular stationery and housekeeping history details. 2. Make sure that admin is able to click on the stationery tab and see the purchased stationery history details after clicking on stationery in Purchased History module. 3. Observe that each text and field that are present in the purchased history module is properly aligned. 4. Ensure that show entry dropdown functionality, admin will select a number from the dropdown to see the number of entries. 5. Check that calendar dropdown functionality; user will select year and month from the calendar dropdown to see that particular month's history. 6. Make sure that admin has gone to the next page or previous pages after clicking on the next and previous navigation arrows. 7. Confirm that admin is able to click on the housekeeping tab and see the purchased housekeeping history details after clicking on 'housekeeping' in purchased history module. 8. Confirm that the purchased history details of stationery products excel file has downloaded in System's browser after clicking on the Export icon. 9. Check that an excel file of the purchased stationery history for a particular stationery product is downloaded after clicking on the Export icon' in issued column. 10. Observe that the admin can see purchased housekeeping product details in tabular form after clicking on the Housekeeping tab in purchased history module. 11. Ensure that admin can see purchased stationery product details in tabular form after clicking on the Stationery tab in purchased history module. 12. Check that the alignment of all fields, texts, and fonts that are present in the purchased history module is proper. "384Nomination module is implemented to accept or reject the nominations of employee for the batch which is under that project manager.,"1. Analyze the functionality of view icon used to view the nomination. 2. Check the working of accept icon , after clicking on it to accept the nomination and make sure that popup must be appear after accepting the nomination. 3. Ensure that on clicking reject icon, nomination must be rejected and popup appear as Nomination rejected successfully. 4. Check the functionality of the show history button, whether it is showing accurate data with proper status. 5. Analyze that, on clicking nominations module, it is showing module name , data in proper size, color and font. "385User will login using the valid credentials. User need to enter the correct ID and Password to get logged-in into the application.,1. Make sure the login page works fine with a correct username and password. 2. Check the login page with an invalid Password and an invalid Username. 3. Evaluate the login page with an invalid Username and valid password. 4. Check login page with a valid Username and invalid Password. 5. To test the login button with a blank username and Password. 6. Evaluate the functionality of the 'Eye icon' in the password field. 386"The admin/consultant will be able to evaluate Occupancy designs, generate reports, and able to perform water supply analysis in this module.","1. Ensure that Occupancy button takes the consultant to the occupancy screen. 2. Validate the Occupancy dashboard. 3. Validate data cards (Total Reports, Completed Reports, and Pending Reports). 4. Check the 'Action' column functionality from the dashboard which allows consultant to edit, view and delete the report. 5. Check the functionality of the view (eye icon) button. 6. Check the functionality of the edit (icon) button. 7. Check the functionality of the 'Save&Exit' button which allows consultant to make changes in existing report. 8. Check the functionality for delete (icon) button. 9. Validate the search box to find a desired report. 10. Check the functionality of show entry dropdown. 11. Validate the functionality of the 'Pagination' buttons of occupancy report table. 12. Check the all data cards, filters, and buttons along with their labels from Dashboard are appropriately positioned or not. 13. Check that the 'Dashboard' screen is compatible with different screen resolutions. 14. Validate '+ Create Report' button to create new occupancy design report 15. Check the functionality of the 'Policy number' field from the insured details screen. 16. Validate 'Customer number' field from the insured details screen. 17. Check the functionality of the 'Insured name' field on the insured detailscreen. 18. Check the report'Date' functionality. 19. Check the 'Consultant Name' field on the insured details screen. 20. Validate 'Occupancy' dropdown from insured details screen. 21. Check the 'Business Unit' dropdown list functionality. 22. Check the 'Location Address' field functionality. 23. Check the 'Location Description' functionality. 24. Validate 'Consultant Name' field. 25. Check the 'Report Name' field. 26. Check the functionality of the 'Save&Next' button from 'Insured detail' screen by leaving the mandatory fields blank. 27. Validate 'Save &Next' button from Insured details screen which allows consultant to move further. 28. Check the functionality of the 'Back' button on the Insured details screen. 29. Examine Insured details screen to ensure that all text boxes and labels are appropriately positioned. 30. Check to see if the 'Insured Details' screen is compatible with different screen resolutions. 31. Check the dropdown list functionality for 'Occupancy name' from Area Specification screen. 32. Validate the functionality of the 'Save & Next' button on the Area Specification screen without selecting any value from the dropdown list. 33. Check the functionality of the 'Submit' button on the Area Specification screen. 34. Check the functionality for 'Back' button from Area Specification screen. 35. Check to see if 'Occupancy Name' dropdown along with its label from 'Area Specification' screen is appropriately positioned or not. 36. Check to see if the 'Area Specification' screen is compatible with different screen resolutions. 37. Validate 'Suggested design' screen which displays designs based on inputs provided by consultant. 38. Check the checkbox functionality on the 'Suggested Design' screen. 39. Validate 'Additional Comment' text box from the Suggested design screen. 40. Check the functionality of the 'Save &Next'button on the Suggested Design screen when no check box is selected. 41. Check the functionality of the 'Back' button from the Suggested design screen. 42. Validate 'Save &Next'button from Suggested design screen. 43. Check that all check boxes and labels from the 'Suggested Design' screen are properly positioned. 44. Check to see if the 'Suggested Design' screen is compatible with different screen resolutions. 45. Validate 'Skip & Preview' button on the Sprinkler Demand screen which allow consultant to proceed to preview page. 46. Check the functionality for Preview screen, when water supply analysis is skipped. 47. Check that all texts along with their labels from 'Preview' screen (Water Supply analysis Skipped) are appropriately positioned or not. 48. Check to see if the 'Preview' (Water Supply analysis Skipped) screen is compatible with different screen resolutions. 49. Validate 'Generate Report' button 50. Validate 'Download' button on the Preview screen to download sprinkler design report. 51. Check all icons, graph, headers along with their labels from downloaded PDF (water supply analysis is skipped), are appropriately positioned or not. 52. Validate 'Back' button from Preview screen through which consultant will navigate to sprinkler demand screen. 53. Validate Area/Density radio button from Sprinkler Demand screen. 54. Validate K/Pressure radio button from Sprinkler demand screen. 55. Verify functionality of 'Flow' field from Demand section. 56. Check the functionality of 'Pressure' text box under Demand section. 57. Validate 'Elevation' text field from Sprinkler Head section. 58. Check the operation of the 'Hose' Allowance field. 59. When mandatory fields are left blank, check the functionality of the 'Save &Next'button on the Sprinkler demand screen. 60. Validate Back button from Sprinkler demand screen. 61. Validate 'Save &Next'button from Sprinkler demand screen. 62. Check that all text boxes, radio buttons and labels on the 'Sprinkler Demand' screen are properly positioned. 63. Check to see if the 'Sprinkler Demand' screen is compatible with different screen resolutions. 64. Validate 'Water-Source' dropdown from Water supply the screen. 65. Examine the behavior of the application when the consultant picks the 'Hydrant flow test' option from the Water source dropdown. 66. Check the behavior of the application when the consultant picks the 'Pump flow test' option from the Water source dropdown. 67. Check the behavior of the application when the consultant picks the 'Hydrant flow + Pump flow test' option from the Water source dropdown. 68. Validate 'Reset' button to erase existing data 69. Validate 'Date' field which allows consultant to select water supply date. 70. Validate 'Save &Next'button functionality from 'Water Supply' screen when any of input fields are kept blank. 71. Check Back button functionality from 'Water Supply' screen. 72. Check 'Save &Next'button functionality from 'Water Supply' screen. 73. Check whether all text boxes, radio buttons and dropdown boxes, as well as their labels, are properly positioned on the 'Water Supply' screen. 74. Check to determine if the 'Water Supply' screen is compatible with different screen resolutions. 75. Validate Graph screen. 76. Check the functionality of the Back button on the Graph screen. 77. Check the functionality of the 'Save &Next'button on the Graph screen. 78. Check to see if the 'Graph' screen is compatible with different screen resolutions. 79. Validate the 'Required Density' dropdown list functionality from Performance Estimation. 80. Validate 'Save & Next' button from Performance Estimation screen which display performance point and Required point value for provided input . 81. When no value is selected from the dropdown list, Check the functionality of the Preview button from Performance Estimation screen. 82. Check that all text boxes, dropdown boxes and buttons, as well as their labels, from the 'Performance Estimation' screen are properly positioned. 83. Check to see if the 'Performance Estimation' screen is compatible with different screen resolutions. 84. Validate Back from Performance Estimation screen. 85. Validate 'Save & Preview' button functionality from Performance Estimation screen when Water supply analysis is performed. 86. Validate 'preview' screen which contains sprinkler design as well as water supply analysis 87. Check 'Generate Report' button functionality when Water Supply Analysis is Performed. 88. Validate 'Download' button on the Preview screen to download sprinkler design and water supply analysis report 89. Validate the Back button from Preview screen which contains sprinkler design and Water supply analysis 90. Validate all icons, texts along with their labels from 'Preview' screen which contains water supply analysis, are appropriately positioned or not. 91. Check to see if the 'Preview' screen which contains sprinkler designs along with water supply analysis, is compatible with different screen resolutions. 92. Check all icons, graph, headers along with their labels from downloaded PDF (water supply analysis is Performed), are appropriately positioned or not. "387" The admin/consultant will be able to evaluate Miscellaneous Storage designs, generate reports, and able to perform water supply analysis in this module","1. Validate Miscellaneous tab, which redirects consultant to Miscellaneous dashboard. 2. Validate the Miscellaneous dashboard. 3. Validate data cards (Total Reports, Completed Reports, and Pending Reports). 4. Check the 'Action' column functionality from miscellaneous reports table, which allows consultant to edit, view and delete the report. 5. Check the functionality of the view (eye icon) button. 6. Check the functionality of the edit (icon) button. 7. Check the functionality of the 'Save & Exit' button which allows consultant to make changes in insured details of report. 8. Check the functionality for delete (icon) button. 9. Validate the search box to find a desired sprinkler design report for design type miscellaneous. 10. Check the functionality of show entry dropdown. 11. Validate the functionality of the 'Pagination' buttons of Miscellaneous report table. 12. Check all data cards, filters, and buttons along with their labels from Miscellaneous Dashboard are appropriately positioned or not. 13. Verify if Miscellaneous Dashboard is compatible with various screen resolutions. 14. Validate '+ Create Report' button to create new Miscellaneous design report 15. Validate 'Policy number' field from insured details screen. 16. Validate 'Customer number' field from the insured details screen. 17. Check the functionality of the 'Insured name' field from insured detail screen. 18. Check the report 'Date' functionality. 19. Check the 'Consultant Name' field on the insured details screen. 20. Validate 'Occupancy' dropdown from insured details screen. 21. Check the 'Business Unit' dropdown list functionality. 22. Check the 'Location Address' field functionality. 23. Validate 'Location Description' field 24. Validate 'Consultant Name' field. 25. Check the 'Report Name' field. 26. Check the functionality of the 'Save & Next' button from 'Insured detail' screen by leaving the mandatory fields blank. 27. Validate 'Save &Next' button from Insured details screen which allows consultant to move further. 28. Check the functionality of the 'Back' button on the Insured details screen. 29. Examine Insured details screen to ensure that all text boxes and labels are appropriately positioned. 30. Check to see if the 'Insured Details' screen is compatible with different screen resolutions. 31. Check the 'Commodity' dropdown list functionality from the Area Specification Screen. 32. Validate dropdown list functionality for 'Storage Configuration' from Area Specification Screen. 33. Verify functionality for 'Storage Height' field 34. Verify functionality for 'Ceiling Height' 35. Validate the functionality of the 'Submit' button on the Area Specification screen by leaving one of the fields blank. 36. Check the functionality of the 'Submit' button on the Area Specification screen. 37. Check the functionality for 'Back' button from Area Specification screen. 38. Check to see if all dropdowns, text boxes along with their labels from 'Area Specification' screen is appropriately positioned or not. 39. Check to see if the 'Area Specification' screen is compatible with different screen resolutions. 40. Validate 'Suggested design' screen which displays designs based on inputs provided by consultant. 41. Validate 'Additional Comment' text box from the Suggested design screen. 42. Check the functionality of the 'Back' button from the Suggested design screen. 43. Validate 'Save &Next' button from Suggested design screen. 44. Check that all check boxes and labels from the 'Suggested Design' screen are properly positioned. 45. Check to see if the 'Suggested Design' screen is compatible with different screen resolutions. 46. Validate 'Skip & Preview' button on the Sprinkler Demand screen which allow consultant to proceed to preview page. 47. Check the functionality for Preview screen, when water supply analysis is skipped. 48. Check that all texts along with their labels from 'Preview' screen (Water Supply analysis Skipped) are appropriately positioned or not. 49. Check to see if the 'Preview' (Water Supply analysis Skipped) screen is compatible with different screen resolutions. 50. Validate 'Generate Report' button. 51. Validate 'Download' button on the Preview screen to download sprinkler design report. 52. Check to see if the downloaded PDF (water supply analysis not selected) is compatible with every screen resolution. 53. Validate 'Back' button from Preview screen through which consultant will navigate to sprinkler demand screen. 54. Validate Area/Density radio button from Sprinkler Demand screen. 55. Validate K/Pressure radio button from Sprinkler demand screen. 56. Verify functionality of 'Flow' field from Demand section. 57. Check the functionality of 'Pressure' text box under Demand section. 58. Validate the text box 'Elevation' from Sprinkler Head section. 59. Check the operation of the 'Hose' field from Allowance section. 60. When mandatory fields are left blank, check the functionality of the 'Save &Next' button on the Sprinkler demand screen. 61. Validate Back button from Sprinkler demand screen. 62. Validate 'Save &Next' button from Sprinkler demand screen. 63. Check that all text boxes, radio buttons and labels on the 'Sprinkler Demand' screen are properly positioned. 64. Check to see if the 'Sprinkler Demand' screen is compatible with different screen resolutions. 65. Validate 'Water-Source' dropdown from Water supply the screen. 66. Examine the application's behavior when the consultant selects the 'Hydrant flow test' option from the Water source menu. 67. Check the behavior of the application when the consultant picks the 'Pump flow test' option from the Water source dropdown. 68. Examine the application's behavior when the consultant selects the 'Hydrant flow + pump flow test' option from the Water source menu. 69. Validate 'Reset' button to erase existing data 70. Validate 'Date' field which allows consultant to select water supply date. 71. Validate 'Save &Next' button when any of input fields are kept blank. 72. Check Back button functionality from 'Water Supply' screen. 73. Check 'Save &Next' button functionality from 'Water Supply' screen. 74. Check whether all text boxes, radio buttons and dropdown boxes, as well as their labels, are properly positioned on the 'Water Supply' screen. 75. Check to determine if the 'Water Supply' screen is compatible with different screen resolutions. 76. Examine Graph screen. 77. Check the functionality of the Back button on the Graph screen. 78. Check the functionality of the 'Save &Next' button on the Graph screen. 79. Check to see if the 'Graph' screen is compatible with different screen resolutions. 80. Verify 'Required Density' dropdown from Performance Estimation screen. 81. Validate 'Save&Next' button from Performance Estimation screen which display performance point and required point value for provided input. 82. Check the operation of the Preview button on the Performance Estimation screen when there is no value chosen from list. 83. Check that all text boxes, dropdown boxes and buttons, as well as their labels, from the 'Performance Estimation' screen are properly positioned. 84. Check to see if the 'Performance Estimation' screen is compatible with different screen resolutions. 85. Examine the functionality for Back from Performance Estimation screen. 86. Examine 'Save & Preview' button functionality from Performance Estimation screen when Water supply analysis is performed. 87. Validate 'preview' screen which contains sprinkler design as well as water supply analysis 88. Check operation of 'Generate Report' button to save sprinkler design & Water Supply Analysis report 89. Validate 'Download' button on the Preview screen to download sprinkler design and water supply analysis report 90. Validate the Back button from Preview screen which contains sprinkler design and Water supply analysis 91. Check to see that all icons, texts along with their labels from 'Preview' screen which contains water supply analysis, are appropriately positioned 92. The 'Preview' screen, which includes sprinkler designs and a water supply analysis, should be checked to verify if it works with different screen resolutions. 93. Check all icons, graph, headers along with their labels from downloaded PDF (water supply analysis is Performed), are appropriately positioned or not. 94. Check the checkbox functionality on the 'Suggested Design' screen. "388"The admin/consultant will be able to evaluate Rack Storage designs, generate reports, and able to perform water supply analysis in this module","1. Validate Rack Storage tab, which redirects consultant to Rack Storage dashboard. 2. Validate the Rack Storage dashboard. 3. Verify the statistics on the report cards (total reports, completed reports, and pending reports). 4. Check the 'Action' column functionality from Rack storage reports table, which allows consultant to edit, view, delete the report. 5. Check the functionality of the view (eye icon) button. 6. Check the functionality of the edit (icon) button. 7. Examine the 'Save & Exit' button's functionality to see if it allows the consultant to edit the insured details. 8. Check the functionality of delete (icon) button. 9. Validate the search box to find a desired sprinkler design report for design type Rack Storage. 10. Check the functionality of show entry dropdown. 11. Validate the functionality of the 'Pagination' buttons of Rack Storage report table. 12. Check all data cards, filters, and buttons along with their labels from Rack Storage Dashboard are appropriately positioned or not. 13. Verify if Rack Storage Dashboard is compatible with various screen resolutions. 14. Validate '+ Create Report' button to create new Rack Storage design report. 15. Validate 'Policy number' field from insured details screen. 16. Validate 'Customer number' field from the insured details screen. 17. Validate 'Insured name' field 18. Check the report 'Date' functionality. 19. Check the 'Consultant Name' field on the insured details screen. 20. Validate 'Occupancy' dropdown from insured details screen. 21. Check the 'Business Unit' dropdown 22. Check the 'Location Address' field functionality. 23. Validate 'Location Description' field 24. Validate 'Consultant Name' field. 25. Check the 'Report Name' field. 26. Check the functionality of the 'Save & Next' button from 'Insured detail' screen by leaving the mandatory fields blank. 27. Check the functionality of the 'Back' button on the Insured details screen. 28. Validate 'Save &Next' button from Insured details screen which allows consultant to move further. 29. Examine Insured details screen to ensure that all text boxes and labels are appropriately positioned. 30. Check to see if the 'Insured Details' screen is compatible with different screen resolutions. 31. Check radio button functionality for 'Commodity' from Area Specification form. 32. Validate radio button functionality for 'Shelving' from Area Specification form. 33. Verify dropdown list functionality for 'Aisle Width' field 34. Verify dropdown list functionality for 'Multirow Rack' field 35. Validate 'Storage Height' field from Area Specification form. 36. Validate 'Ceiling Height' field 37. Verify check box functionality for 'In rack' field 38. Verify check box functionality for 'Product fully Encapsulated' field 39. Validate the functionality of the 'Submit' button on the Area Specification screen by leaving one of the fields blank. 40. Check the functionality of the 'Submit' button on the Area Specification screen. 41. Check the functionality for 'Back' button from Area Specification screen. 42. Check 'Aisle width' and 'Multirow Rack' dropdown along with its label from 'Area Specification' screen is appropriately positioned or not. 43. Check to see if the 'Area Specification' screen is compatible with different screen resolutions. 44. Examine 'Suggested design' screen which displays designs based on inputs provided by consultant. 45. Test the checkbox functionality on the 'Suggested Design' screen. 46. Check the 'Additional Comment' text box from the Suggested design screen. 47. Ensure Toggle button of New and Existing systems of CMDA section from the suggested design page. 48. Test the functionality of the Compare button of CMDA Section from suggested design page. 49. Ensure the functionality of the Check Box of the Compare Pop-up window from CMDA design criteria 50. Test functionality of the 'Close' button from Compare Pop-up (CMDA). 51. Ensure Toggle button of Basic and Alternate Design Criteria for the CMSA section from suggested design screen. 52. Examine the functionality Compare button of the CMSA Section from suggested design screen. 53. Examine functionality of Check Box of Compare button Pop-up window from CMSA section. 54. Test functionality of the 'Close' button of Compare button Pop-up (CMSA). 55. Ensure the functionality of the 'Save &Next' button on the Suggested Design screen when no check box is selected. 56. Test 'Save &Next' button from Suggested design screen. 57. Check the functionality of the 'Back' button from the Suggested design screen. 58. Check that all check boxes and labels from the 'Suggested Design' screen are properly positioned. 59. Ensure if the 'Suggested Design' screen is compatible with different screen resolutions. 60. Examine 'Skip & Preview' button on the Sprinkler Demand screen which allow consultant to proceed to preview page. 61. Check the functionality for Preview screen, when water supply analysis is skipped. 62. Check that all texts along with their labels from 'Preview' screen (Water Supply analysis Skipped) are appropriately positioned or not. 63. Ensure if the 'Preview' (Water Supply analysis Skipped) screen is compatible with different screen resolutions. 64. Examine 'Generate Report' button. 65. Test 'Download' button on the Preview screen to download sprinkler design report. 66. Check all icons, graph, headers along with their labels from downloaded PDF (water supply analysis is Performed), are appropriately positioned or not. 67. Examine 'Back' button from Preview screen through which consultant will navigate to sprinkler demand screen. 68. Test Area/Density radio button from Sprinkler Demand screen. 69. Test K/Pressure radio button from Sprinkler demand screen. 70. Ensure functionality of 'Flow' field from Demand section. 71. Check the functionality of 'Pressure' text box under Demand section. 72. Test 'Elevation' text field from Sprinkler Head section. 73. Check the operation of the 'Hose' Allowance field. 74. Leave mandatory fields blank to check the functionality of the 'Save &Next' button on the Sprinkler demand screen. 75. Test Back button from Sprinkler demand screen. 76. Check 'Save &Next' button from Sprinkler demand screen. 77. Check that all text boxes, radio buttons and labels on the 'Sprinkler Demand' screen are properly positioned. 78. Ensure if the 'Sprinkler Demand' screen is compatible with different screen resolutions. 79. Examine 'Water-Source' dropdown from Water supply the screen. 80. Examine the behavior of the application when the consultant picks the 'Hydrant flow test' option from the Water source dropdown. 81. Test the behavior of the application when the consultant picks the 'Pump flow test' option from the Water source dropdown. 82. Check the behavior of the application when the consultant picks the 'Hydrant flow + Pump flow test' option from the Water source dropdown. 83. Investigate 'Reset' button to erase existing data 84. Check 'Date' field which allows consultant to select water supply date. 85. Examine 'Save &Next' button functionality from 'Water Supply' screen when any of input fields are kept blank. 86. Test Back button functionality from 'Water Supply' screen. 87. Check 'Save &Next' button functionality from 'Water Supply' screen. 88. Check whether all text boxes, radio buttons and dropdown boxes, as well as their labels, are properly positioned on the 'Water Supply' screen. 89. Ensure if the 'Water Supply' screen is compatible with different screen resolutions. 90. Test the functionality of the Back button on the Graph screen. 91. Ensure the functionality of the 'Save &Next' button on the Graph screen. 92. Ensure if the 'Graph' screen is compatible with different screen resolutions. 93. Test the 'Required Density' dropdown list functionality from Performance Estimation. 94. Investigate 'Save &Next' button from Performance Estimation screen which display performance point value for provided input . 95. When no value is selected from the dropdown list, Check the functionality of the Preview button from Performance Estimation screen. 96. Check that all text boxes, dropdown boxes and buttons, as well as their labels, from the 'Performance Estimation' screen are properly positioned. 97. Ensure if the 'Performance Estimation' screen is compatible with different screen resolutions. 98. Test Back button from Performance Estimation screen. 99. Check 'Save & Preview' button functionality from Performance Estimation screen when Water supply analysis is performed. 100. Examine 'preview' screen which contains sprinkler design as well as water supply analysis. 101. Test 'Generate Report' button functionality when Water Supply Analysis is Performed. 102. Ensure 'Download' button on the Preview screen to download sprinkler design and water supply analysis report. 103. Test Back button from Preview screen which contains sprinkler design and Water supply analysis 104. Examine all icons, texts along with their labels from 'Preview' screen which contains water supply analysis, are appropriately positioned or not. 105. Ensure if the 'Preview' screen which contains sprinkler designs along with water supply analysis, is compatible with different screen resolutions. 106. Check all icons, graph, headers along with their labels from downloaded PDF (water supply analysis is Performed), are appropriately positioned or not. 107. Check the Graph screen functionality. "389" The admin/consultant will be able to evaluate Pile Storage designs, generate reports, and able to perform water supply analysis in this module","1. Ensure that Pile Storage tab takes the consultant to the Pile Storage screen. 2. Examine the functionality of Pile Storage dashboard. 3. check data cards (Total Reports, Completed Reports, and Pending Reports). 4. Check the 'Action' column functionality from the dashboard which allows consultant to edit, view and delete the report. 5. Test the view (eye icon) button's operation. 6. Test the functionality of the edit (icon) button. 7. Check the functionality of the 'Save details' button which allows consultant to make changes in existing report. 8. Test the functionality for delete (icon) button. 9. Test the search box functionality to find a desired report. 10. Ensure the functionality of show entry dropdown. 11. Check the functionality of the 'Pagination' buttons of Pile Storage report table. 12. Test all data cards, filters, and buttons along with their labels from Dashboard are appropriately positioned or not. 13. Check that the 'Dashboard' screen is compatible with different screen resolutions. 14. Test '+ Create Report' button to create new Pile Storage design report 15. Check the functionality of the 'Policy number' field from the insured details screen. 16. Test 'Customer number' field from the insured details screen. 17. Check the functionality of the 'Insured name' field on the insured detail screen. 18. Check the report 'Date' functionality. 19. Test the 'Consultant Name' field on the insured details screen. 20. Examine 'Occupancy' dropdown from insured details screen. 21. Examine the 'Business Unit' dropdown list functionality. 22. Test the 'Location Address' field functionality. 23. Test the 'Location Description' functionality. 24. Ensure 'Consultant Name' field. 25. Check the 'Report Name' field. 26. Ensure the functionality of the 'Save&Next' button from 'Insured detail' screen by leaving the mandatory fields blank. 27. Examine 'Save &Next' button from Insured details screen which allows consultant to move further. 28. Test the functionality of the 'Back' button on the Insured details screen. 29. Examine Insured details screen to ensure that all text boxes and labels are appropriately positioned. 30. Check to see if the 'Insured Details' screen is compatible with different screen resolutions. 31. Ensure the Radio button functionality of the Commodity Class of Area specifications form of Pile Storage. 32. Ensure the Radio button functionality of the Storage configuration of Area specifications form of Pile Storage. 33. Test the Storage height text box field functionality of the Area specification form of Pile Storage 34. Test the Ceiling height text box field functionality of the Area specification form of Pile Storage. 35. Ensure the functionality of the 'Submit' button on the Area Specification screen without selecting any value from the dropdown list. 36. Test the functionality of the 'Submit' button on the Area Specification screen. 37. Test the functionality for 'Back' button from Area Specification screen. 38. Ensure if all radio buttons, text box, and dropdowns along with its label from 'Area Specification' screen is appropriately positioned or not. 39. Examine the 'Area Specification' screen to see if it is compatible with various screen resolutions. 40. Examine 'Suggested design' screen which displays designs based on inputs provided by consultant. 41. Test the checkbox functionality on the 'Suggested Design' screen. 42. Checkthe 'Additional Comment' text box from the Suggested design screen. 43. Ensure the functionality of theToggle button of New and Existing systems of CMDA section from the suggested design page. 44. Test the functionality of the Compare button of CMDA Section from suggested design page. 45. Ensure the functionality of the Check Box of the Compare Pop-up window from CMDA design criteria 46. Test functionality of the 'Close' button from Compare Pop-up (CMDA) 47. Ensure the functionality of theToggle button of Basic and Alternate Design Criteria for the CMSA section from suggested design page. 48. Examine the functionality Compare button of the CMSA Section from suggested design page. 49. Examine functionality of Check Box of Compare button Pop-up window from CMSA section. 50. Test functionality of the 'Close' button of Compare button Pop-up (CMSA) 51. Ensure the functionality of the 'Save &Next' button on the Suggested Design screen when no check box is selected. 52. Test 'Save &Next' button from Suggested design screen. 53. Check the functionality of the 'Back' button from the Suggested design screen. 54. Check that all check boxes and labels from the 'Suggested Design' screen are properly positioned. 55. Ensure if the 'Suggested Design' screen is compatible with different screen resolutions. 56. Examine 'Skip & Preview' button on the Sprinkler Demand screen which allow consultant to proceed to preview page. 57. Check the functionality for Preview screen, when water supply analysis is skipped. 58. Check that all texts along with their labels from 'Preview' screen (Water Supply analysis Skipped) are appropriately positioned or not. 59. Ensure if the 'Preview' (Water Supply analysis Skipped) screen is compatible with different screen resolutions. 60. Examine 'Generate Report' button 61. Test 'Download' button on the Preview screen to download sprinkler design report. 62. Check all icons, graph, headers along with their labels from downloaded PDF (water supply analysis is Performed), are appropriately positioned or not. 63. Examine 'Back' button from Preview screen through which consultant will navigate to sprinkler demand screen. 64. Test Area/Density radio button from Sprinkler Demand screen. 65. Test K/Pressure radio button from Sprinkler demand screen. 66. Ensure functionality of 'Flow' field from Demand section. 67. Check the functionality of 'Pressure' text box under Demand section. 68. Test 'Elevation' text field from Sprinkler Head section. 69. Check the operation of the 'Hose' Allowance field. 70. Leave mandatory fields blank to check the functionality of the 'Save &Next' button on the Sprinkler demand screen. 71. Test Back button from Sprinkler demand screen. 72. Check 'Save &Next' button from Sprinkler demand screen. 73. Check that all text boxes, radio buttons and labels on the 'Sprinkler Demand' screen are properly positioned. 74. Ensure if the 'Sprinkler Demand' screen is compatible with different screen resolutions. 75. Examine 'Water-Source' dropdown from Water supply the screen. 76. Examine the behavior of the application when the consultant picks the 'Hydrant flow test' option from the Water source dropdown. 77. Test the behavior of the application when the consultant picks the 'Pump flow test' option from the Water source dropdown. 78. Check the behavior of the application when the consultant picks the 'Hydrant flow + Pump flow test' option from the Water source dropdown. 79. Investigate 'Reset' button to erase existing data 80. Check 'Date' field which allows consultant to select water supply date. 81. Examine 'Save &Next' button functionality from 'Water Supply' screen when any of input fields are kept blank. 82. Test Back button functionality from 'Water Supply' screen. 83. Check 'Save &Next' button functionality from 'Water Supply' screen. 84. Check whether all text boxes, radio buttons and dropdown boxes, as well as their labels, are properly positioned on the 'Water Supply' screen. 85. Ensure if the 'Water Supply' screen is compatible with different screen resolutions. 86. Examine Graph screen. 87. Test the functionality of the Back button on the Graph screen. 88. Ensure the functionality of the 'Save &Next' button on the Graph screen. 89. Ensure if the 'Graph' screen is compatible with different screen resolutions. 90. Test the 'Required Density' dropdown list functionality from Performance Estimation. 91. Investigate 'Save &Next' button from Performance Estimation screen which display performance point value for provided input . 92. When no value is selected from the dropdown list, Check the functionality of the Preview button from Performance Estimation screen. 93. Check that all text boxes, dropdown boxes and buttons, as well as their labels, from the 'Performance Estimation' screen are properly positioned. 94. Ensure if the 'Performance Estimation' screen is compatible with different screen resolutions. 95. Test Back button from Performance Estimation screen. 96. Check 'Save & Preview' button functionality from Performance Estimation screen when Water supply analysis is performed. 97. Examine 'preview' screen which contains sprinkler design as well as water supply analysis 98. Test 'Generate Report' button functionality when Water Supply Analysis is Performed. 99. Ensure 'Download' button on the Preview screen to download sprinkler design and water supply analysis report 100. Test Back button from Preview screen which contains sprinkler design and Water supply analysis 101. Examine all icons, texts along with their labels from 'Preview' screen which contains water supply analysis, are appropriately positioned or not. 102. Ensure if the 'Preview' screen which contains sprinkler designs along with water supply analysis, is compatible with different screen resolutions. 103. Check all icons, graph, headers along with their labels from downloaded PDF (water supply analysis is Performed), are appropriately positioned or not. 104. Test the Product fully Encapsulated check box functionality on Area specification form of Pile Storage. "390"The admin/consultant will be able to evaluate Pile Plastic designs, generate reports, and able to perform water supply analysis in this module.","1. Ensure that Pile Plastic tab takes the consultant to the Pile Plastic screen. 2. Check the Pile Plastic dashboard. 3. Check data cards (Total Reports, Completed Reports, and Pending Reports). 4. Check the 'Action' column functionality from the dashboard which allows consultant to edit/view the report. 5. Check the functionality of the view (eye icon) button. 6. Check the functionality of the edit (icon) button. 7. Check the functionality of the 'Save details' button which allows consultant to make changes in existing report. 8. Check the functionality for delete (icon) button. 9. Check the search box to find a desired report. 10. Check the functionality of show entry dropdown. 11. Check the functionality of the 'Pagination' buttons of pile plastic report table. 12. Check the all data cards, filters, and buttons along with their labels from Dashboard are appropriately positioned or not. 13. Check that the 'Dashboard' screen is compatible with different screen resolutions. 14. Examine '+ Create Report' button to create new pile plastic design report 15. Check the functionality of the 'Policy number' field from the insured details screen. 16. Test 'Customer number' field from the insured details screen. 17. Check the functionality of the 'Insured name' field on the insured detail screen. 18. Test the report 'Date' functionality. 19. Check the 'Consultant Name' field on the insured details screen. 20. Check 'Occupancy' dropdown from insured details screen. 21. Check the 'Business Unit' dropdown list functionality. 22. Examine the 'Location Address' field's functioning. 23. Test the 'Location Description' functionality. 24. Check 'Consultant Name' field. 25. Examine the 'Report Name' box. 26. Leave the required information empty to test the 'Save&Next' button's functionality from the 'Insured detail' screen. 27. Examine 'Save &Next' button from Insured details screen which allows consultant to move further. 28. Check the functionality of the 'Back' button on the Insured details screen. 29. Examine Insured details screen to ensure that all text boxes and labels are appropriately positioned. 30. Check to see if the 'Insured Details' screen is compatible with different screen resolutions. 31. Examine the Radio button functionality of the Commodity of Area specifications form of Pile Plastic. 32. Check the Radio button functionality of the Storage of Area specifications form of Pile Plastic. 33. Test the Radio button functionality of the Packaging of Area specifications form of Pile Plastic. 34. Check that the radio button for Pile Stability on the Pile Plastic area specification form works. 35. Examine the Radio button functionality of the Configuration of Area specifications form of Pile Plastic. 36. Test the Storage height text box field functionality of the Area specification form of Pile Plastic. 37. Check the Ceiling height text box field functionality of the Area specification form of Pile Plastic. 38. By leaving the mandatory fields empty, check the 'Save & Next' button's operation from the Area Specification screen. 39. Test the functionality of the 'Save & Next' button on the Area Specification screen. 40. Check the functionality for 'Back' button from Area Specification screen. 41. Examine if all radio buttons, text box, and dropdowns along with its label from 'Area Specification' screen is appropriately positioned or not. 42. Check to see if the 'Area Specification' screen is compatible with different screen resolutions. 43. Test 'Suggested design' screen which displays designs based on inputs provided by consultant. 44. Check the checkbox functionality on the 'Suggested Design' screen. 45. Examine 'Additional Comment' text box from the Suggested design screen. 46. Test Toggle button of New and Existing systems of CMDA section from the suggested design page. 47. Check functionality of the Compare button of the CMDA Section from suggested design page. 48. Ensure the functionality of the Check Box of the Compare Pop-up window from CMDA design criteria 49. Test functionality of the 'Close' button from Compare Pop-up (CMDA) 50. Check Toggle button of Basic and Alternate Design Criteria for the CMSA section from suggested design page. 51. Ensure the functionality Compare button of the CMSA Section from suggested design page. 52. Test functionality of Check Box of Compare button Pop-up window from CMSA section. 53. Check functionality of the 'Close' button of Compare button Pop-up (CMSA) 54. Examine the functionality of the 'Save &Next' button on the Suggested Design screen when no check box is selected. 55. Test the functionality of the 'Back' button from the Suggested design screen. 56. Check 'Save &Next' button from Suggested design screen. 57. Ensure that all check boxes and labels from the 'Suggested Design' screen are properly positioned. 58. Examine if the 'Suggested Design' screen is compatible with different screen resolutions. 59. Check 'Skip & Preview' button on the Sprinkler Demand screen which allow consultant to proceed to preview page. 60. Test the functionality for Preview screen, when water supply analysis is skipped. 61. Ensure that all texts along with their labels from 'Preview' screen (Water Supply analysis Skipped) are appropriately positioned or not. 62. Examine if the 'Preview' (Water Supply analysis Skipped) screen is compatible with different screen resolutions. 63. Inspect the Generate Report button 64. Test 'Download' button on the Preview screen to download sprinkler design report. 65. Examine if the downloaded PDF(water supply analysis not selected) is compatible with every screen resolution. 66. Check 'Back' button from Preview screen through which consultant will navigate to sprinkler demand screen. 67. Test Area/Density radio button from Sprinkler Demand screen. 68. Examine K/Pressure radio button from Sprinkler demand screen. 69. Check functionality of 'Flow' field from Demand section. 70. Test the functionality of 'Pressure' text box under Demand section. 71. Examine 'Elevation' text field from Sprinkler Head section. 72. Check the operation of the 'Hose' Allowance field. 73. When mandatory fields are left blank, check the functionality of the 'Save &Next' button on the Sprinkler demand screen. 74. Inspect Back button from Sprinkler demand screen. 75. Examine 'Save &Next' button from Sprinkler demand screen. 76. Ensure that all text boxes, radio buttons and labels on the 'Sprinkler Demand' screen are properly positioned. 77. Examine if the 'Sprinkler Demand' screen is compatible with different screen resolutions. 78. Test 'Water-Source' dropdown from Water supply the screen. 79. Examine the behavior of the application when the consultant picks the 'Hydrant flow test' option from the Water source dropdown. 80. Check the behavior of the application when the consultant picks the 'Pump flow test' option from the Water source dropdown. 81. Test the behavior of the application when the consultant picks the 'Hydrant flow + Pump flow test' option from the Water source dropdown. 82. Check 'Clear' button to erase existing data 83. Examine 'Date' field which allows consultant to select water supply date. 84. Test 'Save &Next' button functionality from 'Water Supply' screen when any of input fields are kept blank. 85. Check Back button functionality from 'Water Supply' screen. 86. Test 'Save &Next' button functionality from 'Water Supply' screen. 87. Examine whether all text boxes, radio buttons and dropdown boxes, as well as their labels, are properly positioned on the 'Water Supply' screen. 88. Check if the 'Water Supply' screen is compatible with different screen resolutions. 89. Inspect Graph screen. 90. Test the functionality of the Back button on the Graph screen. 91. Check the functionality of the 'Save &Next' button on the Graph screen. 92. Ensure that the 'Graph' screen is compatible with different screen resolutions. 93. Test the 'Required Density' dropdown list functionality from Performance Estimation. 94. Check 'Save & Next' button from Performance Estimation screen which display performance point and Required point value for provided input . 95. When no value is selected from the dropdown list, Check the functionality of the Preview button from Performance Estimation screen. 96. Check that all text boxes, dropdown boxes and buttons, as well as their labels, from the 'Performance Estimation' screen are properly positioned. 97. Examine that the 'Performance Estimation' screen is compatible with different screen resolutions. 98. Inspect Back button from Performance Estimation screen. 99. Test 'Save & Preview' button functionality from Performance Estimation screen when Water supply analysis is performed. 100. Examine 'preview' screen which contains sprinkler design as well as water supply analysis 101. Check 'Generate Report' button functionality when Water Supply Analysis is Performed. 102. Test 'Download' button on the Preview screen to download sprinkler design and water supply analysis report 103. Examine the Back button from Preview screen which contains sprinkler design and Water supply analysis 104. Ensure all icons, texts along with their labels from 'Preview' screen which contains water supply analysis, are appropriately positioned or not. 105. Examine that the 'Preview' screen which contains sprinkler designs along with water supply analysis, is compatible with different screen resolutions. 106. Ensure all icons, graph, headers along with their labels from downloaded PDF (water supply analysis is Performed), are appropriately positioned or not. "391"The admin/consultant will be able to evaluate Roll Paper designs, generate reports, and able to perform water supply analysis in this module","1. Ensure that Roll Paper tab takes the consultant to the Roll Paper dashboard. 2. Examine dashboard of Roll Paper. 3. Check to see if data cards are functional (Total Reports, Completed Reports, and Pending Reports). 4. Check the 'Action' column functionality from the dashboard which allows consultant to edit, view and delete the report. 5. Check the functionality of the view (eye icon) button. 6. Check the functionality of the edit (icon) button. 7. Check the functionality of the 'Save details' button which allows consultant to make changes in existing report. 8. Check the functionality for delete (icon) button. 9. Examine the functionality of search box to find a desired report. 10. Check the functionality of show entry dropdown. 11. Examine the functionality of the 'Pagination' buttons of Roll Paper report table. 12. Check the all data cards, filters, and buttons along with their labels from Roll Paper dashboard are appropriately positioned or not. 13. Check that the Roll Paper Dashboard is compatible with different screen resolutions. 14. Test '+ Create Report' button to create new Roll Paper design report 15. Check the functionality of the 'Policy number' field from insured details screen. 16. Inspect 'Customer number' field from insured details screen. 17. Check the functionality of the 'Insured name' field 18. Check the report 'Date' functionality. 19. Check the 'Consultant Name' field from insured details screen. 20. Examine 'Occupancy' dropdown from insured details screen 21. Check the 'Business Unit' dropdown list functionality. 22. Check functionality the 'Location Address' field. 23. Check the 'Location Description' field 24. Validate 'Consultant Name' field. 25. Check the 'Report Name' field. 26. Check the functionality of the 'Save&Next' button from 'Insured detail' screen by leaving the mandatory fields blank. 27. Validate 'Save &Next' button from Insured details screen which allows consultant to move further. 28. Check the functionality of the 'Back' button on the Insured details screen. 29. Examine Insured details screen to ensure that all text boxes and labels are appropriately positioned. 30. Check to see if the 'Insured Details' screen is compatible with different screen resolutions. 31. Verify radio button functionality for 'Paper' from Area Specification screen. 32. Examine radio button functionality for 'Banding' 33. Check radio button functionality for 'Storage Array' from Area Specification screen. 34. Check radio button functionality for 'Configuration' from Area Specification screen. 35. Examine 'Storage height' field 36. Verify functionality for 'Ceiling height' 37. By leaving the mandatory fields empty, test the functioning of 'Submit' button from Area Specification screen. 38. Check the functionality of the 'Save&Next' button on the Area Specification screen. 39. Check the functionality for 'Back' button from Area Specification screen. 40. Check to see if 'Area Specification' screen is appropriately positioned or not. 41. Check to see if the 'Area Specification' screen is compatible with different screen resolutions. 42. Validate 'Suggested design' screen which displays designs based on inputs provided by consultant. 43. Check the checkbox functionality on the 'Suggested Design' screen. 44. Ensure functionality of 'Additional Comment' text box 45. Check the functionality of the 'Back' button from the Suggested design screen. 46. Validate 'Save & Next' button from Suggested design screen. 47. Check that all check boxes and labels from the 'Suggested Design' screen are properly positioned. 48. Check to see if the 'Suggested Design' screen is compatible with different screen resolutions. 49. Validate 'Skip & Preview' button on the Sprinkler Demand screen which allow consultant to proceed to preview page. 50. Check the functionality for Preview screen, where water supply analysis is skipped. 51. Check that all texts along with their labels from 'Preview' screen (Water Supply analysis Skipped) are appropriately positioned or not. 52. Check to see if the 'Preview' (Water Supply analysis Skipped) screen is compatible with different screen resolutions. 53. Test the functioning of 'Generate Report' button 54. Ensure the functioning of 'Download' button on the Preview screen to download sprinkler design report. 55. Check all icons, graph, headers along with their labels from downloaded PDF (water supply analysis skipped), are appropriately positioned or not. 56. Validate 'Back' button from Preview screen through which consultant will navigate to sprinkler demand screen. 57. Validate Area/Density radio button from Sprinkler Demand screen. 58. Validate K/Pressure radio button from Sprinkler demand screen. 59. Verify functionality of 'Flow' field from Demand section. 60. Check the functionality of 'Pressure' text box under Demand section. 61. Check 'Elevation' text field from Sprinkler Head section. 62. Check the operation of the 'Hose' Allowance field. 63. When mandatory fields are left blank, check the functionality of the 'Save & Next' button on the Sprinkler demand screen. 64. Check the functioning of Back button from Sprinkler demand screen. 65. Test 'Save &Next' button from Sprinkler demand screen. 66. Check that all text boxes, radio buttons and labels on the 'Sprinkler Demand' screen are properly positioned. 67. Check to see if the 'Sprinkler Demand' screen is compatible with different screen resolutions. 68. Check 'Water-Source' dropdown from Water supply the screen. 69. Examine behavior of application when the consultant picks the 'Hydrant flow test' option from the Water source dropdown. 70. Check the behavior of the application when the consultant picks the 'Pump flow test' option from the Water source dropdown. 71. Check the behavior of the application when the consultant picks the 'Hydrant flow + Pump flow test' option from the Water source dropdown. 72. Test the functioning 'Reset' button to erase existing data 73. Examine 'Date' field which allows consultant to select water supply date. 74. Test the functioning of 'Save & Next' button functionality from 'Water Supply' screen when any of input fields are kept blank. 75. Check the functionality of Back button from 'Water Supply' screen. 76. Check 'Save & Next' button functionality from 'Water Supply' screen. 77. Check whether all text boxes, radio buttons and dropdown boxes, as well as their labels, are properly positioned on the 'Water Supply' screen. 78. Check to determine if the 'Water Supply' screen is compatible with different screen resolutions. 79. Examine Graph screen which displays demand graph based on inputs provided by consultant. 80. Check the functionality of the Back button on the Graph screen. 81. Check the functionality of the 'Save & Next' button from Graph screen. 82. Check to see if the 'Graph' screen is compatible with different screen resolutions. 83. Check the 'Required Density' dropdown list functionality from Performance Estimation. 84. Ensure the functioning of 'Save & Next' button from Performance Estimation screen which display performance point and Required point value for provided input. 85. When no value is selected from the dropdown list, Check the functionality of the Preview button from Performance Estimation screen. 86. Check that all text box, dropdown box and buttons along with their labels, from the 'Performance Estimation' screen are properly positioned. 87. Check to see if the 'Performance Estimation' screen is compatible with different screen resolutions. 88. Check the functioning of 'Back' button from Performance Estimation screen. 89. Check 'Save & Preview' button functionality from Performance Estimation screen when Water supply analysis is performed. 90. Check 'preview' screen which contains sprinkler design as well as water supply analysis 91. Check 'Generate Report' button functionality when Water Supply Analysis is Performed. 92. Check the functioning of 'Download' button on the Preview screen to download sprinkler design and water supply analysis report 93. Check the functioning of Back button from Preview screen which contains sprinkler design and Water supply analysis 94. Ensure that all icons, texts along with their labels from 'Preview' screen which contains water supply analysis, are appropriately positioned or not. 95. Check to see if the 'Preview' screen which contains sprinkler designs along with water supply analysis, is compatible with different screen resolutions. 96. Check all icons, graph, headers along with their labels from downloaded PDF (water supply analysis is Performed), are appropriately positioned or not. "392The admin/consultant will be able to search generated reports.,"1. Examine the functionality of 'Historical Report' tab. 2. Ensure that the 'Historical Report' dashboard screen is accessible. 3. Examine the Historical Report dashboard's 'Search' box field's functionality. 4. Check the functionality of'Pagination' button from theHistorical ReportDashboard screen. 5. Inspect the Historical Report's 'Show Entries' drop-down. 6. Check to verify that text boxes, images, icons, and filters from the Historical Report Dashboard screen are appropriate position. 7. Examine the 'Dashboard' from theHistorical Report screenis compatible with different screen resolutions. "393The admin/consultant will be able to view generated reports. The admin/consultant will be able to view all the reports generated by all consultants in the system.,1. Check the View icon from action column which will allow the consultant to preview the existing report. 394The admin/consultant will be able to edit reports generated by them.,1. Check the Edit icon from action column which will allow the consultant to edit the existing report. 395The admin/consultant will be able to delete reports.,1. Check the Delete icon from action column which will allow the consultant to delete the desired report. 396The admin/consultant will be able to search the commodity details.,"1. Examine the functionality of 'Commodity Search' tab. 2. Check the functionality of the commodity dashboard and its columns. 3. Check the functionality of the Search Box from commodity search. 4. Examine the 'Pagination' functionality from the commodity search dashboard. 5. Inspect Commodity Search's 'Show Entries' drop-down. 6. Check to see if all text boxes, images, icons, and filters from Commodity searchDashboardare positioned correctly. 7. Examine the 'Dashboard' of Commodity Searchto see if it is compatible with different screen resolutions. "397"The admin will be able to add the commodity, and its classification.",1. Check the '+add' buttonfunctionality to add thenew commodity details. 2. Check the functionality of new pop-up that appears after the user clickson+add button. 398The admin will be able to edit the commodity and its classification.,1. Check the '+Edit' icon functionality to edit the desired commodity details. 2. Examine the functionality of edit pop-up that appears after the user clicksonEdit icon. 399The admin will be able to delete the commodity.,1. Check the Delete icon functionality to delete the desired commodity details. 400 Application will display the set adequacy point,"1. Check fortheAdequacyStandards module's functionality. 2. Examine the Adequacy Standards Dashboard and the Adequacy Point Value. 3. Examine whether the 'Adequacy Standards' screen is compatible with various screen resolutions. 4. Check forwhether all cards, sliders, and buttons, as well as their labels, are properly positioned on the 'Adequacy Standards' screen. "401Admin will be able to set the adequacy point using adequacy standard module.,1. Inspect the functionality ofslider. 2. Check for the functionality of theAdequacyPoint. 3. Check that the Save Button is functional. 402 Admin will have overall view of consultants and admin.,"1. Check forthe 'Consultant Management' tab's functionality. 2. Check for the consultant management dashboard along with it columns. 3. Ensure thesearch box functionality from the consultant managementdashboard. 4. Check for'Pagination' functionality from the Consultant Management Dashboard. 5. Inspect the consultant management's 'Show Entries' drop-down. 6. Check to see if all text boxes, images, icons, and filters from the Dashboard for ConsultantManagementare positioned correctly. 7. Examine the 'Dashboard' For Consultant Management to check thecompatibilitywith various screen resolutions. "403 Admin will be able to add consultant.,1. Check for'+Add' button's functionality to add a new consultant details. 2. Check the functionality of the new pop-up that appears after the adminuser clicks on+Add button. 404 Admin will be able to update consultant.,1. Check for'Edit ' icon functionality to edit the consultant details. 2. Check the functionality of the pop-up that appears after the adminuser clicks onEdit icon. 405Admin will be able to delete consultant.,1. Check forthe Delete icon functionalityfrom theaction column of consultant management table. 406Employee user can raise the ticket for new IT service's or assets,"1. Confirm that by clicking on the Service Request module, the list of submodules appears on the sidebar "407"Users can raise service requests for new assets OR maintenance requests for allocated assets, and also they can see the requested history in tabular format with status","1. Evaluate that by clicking on the Raise Request, the user navigates to the Raise Request page 2. Click and check the functionality of breadcrumbs present on the page 3. Confirm that, the user can raise the New Request by filling the necessary fields 4. Validate the functioning of Submit button without filling mandatory fields 5. Make sure that the user can raise the Maintenance Request by filling the necessary fields 6. Ensure the functioning of error message by selecting the category and sub-category which is not allocated to the user 7. Examine the Submit button's functionality without entering the fields that are required. 8. Check the Requested History table, all the raised request history display in the tabular list format 9. Ensure that selected number of entries from the dropdown must be appear only 10. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries appear only 11. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 12. Validate that by clicking on pagination buttons admin user is navigating to respective page 13. Ensure that by clicking on the Request ID the pop up with Asset Details appears on the screen 14. Test that by selecting the category, the application list in subcategory and roles list is appears on the screen 15. Check the functioning of Submit button by keeping the field empty 16. Verify that the user can raise the application access request successfully "408" In this, admin can check the all-user's filled timesheet and according to that admin can approve or reject their timesheet. Also, from admin flow admin can check the request of the leaves and can Approve or Reject the request.","1. Check Approval Timesheet card is available on the admin home screen to check the employee's timesheet request. 2. Evaluate the Approve leave card on the admin home screen, from which the admin can approve or reject the leave request. 3. Confirm that the Fill Timesheet card has been shown on the admin home screen to access the timesheet management system screen. 4. Check Apply Leave Card is displayed on the admin homepage. To access the Apply Leave screen. "409" Admin dashboard should be a feature of the application that enables the admin to upload and review the daily attendance report of the staff, keep track of any employees who are missing their IDs, and post their timesheets.","1. Verify Column Chart functionality is available on dashboard and shows the 'Current Week' timesheet's status. 2. Check 'Upload File' functionality present on Admin's dashboard. 3. Examine whether admin can view yearly timesheet status using column chart dropdown functionality. 4. Check Using the custom option in the Column chart functionality, an administrator can view an employee's timesheet status for the selected date range. 5. Check attendance entry of last five working days is listed on dashboard. 6. Check 'Column Chart' dropdown functionality. 7. Check whether the count displays when user hover over the timesheet's status. 8. Using 'Upload File' functionality, check admin can upload the attendance file. "410 Timesheet record module that enables users to log their daily work activities should be included in the application. Project details also provide access to allocated project information.,"1. Verify timesheet record screen is displayed after clicking on 'Timesheet Record' module. 2. Check list of filled timesheet is displayed on Timesheet Record Screen. 3. Verify Show Entries field's functionality present on Timesheet Record Screen. 4. To search any record present under Timesheet Record Page, check 'Search' field functionality. 5. Check functionality of Previous and Next button. "411"Daily timesheet, as well as the timesheet for the preceding five working days with project details and in-out time details, should be saved and submitted by an employee or admin.","1. Check 'Fill Timesheet' pop-up displays as the user clicks on fill timesheet button. 2. Check calendar displays once the user click on Date field. 3. Verify projects which are assign to employee are listed under 'Select Project' dropdown. 4. Verify 'Description' field fuctionality, so employee can add task description. 5. Check by clicking on task name dropdown, task name displays on screen. 6. Verify that 'Effort Hours' dropdown displays as the dropdown has clicked. 7. Check functionality of Effort minute dropdown. 8. To reset the selected data, examine 'Reset' button functionality. 9. Make sure on clicking on 'Add To List' button, timesheet data get added into the list. 10. Check 'Cancel' button functionality. 11. Check using 'Submit' functionality, user can submit the filled timesheet. 12. Check the application's response when any mandatory field remains unselected and 'Add To List' button is clicked. 13. Examine the application's response when the user visits 'Fill Timesheet' window and clicks on the cross mark. 14. Verify response of Fill timesheet window if the date field is not selected. 15. To verify if user forget to select Project name and clicks on 'Add To list' button by filling other information. 16. Check timesheet can be added to list if 'Task name' not selected. 17. Determine an entry of timesheet can be added if Effort min and Effort hours not selected. 18. Analyze the behaviour of fill timesheet functioning, if timesheet added to the list is deleted and submit button is clicked. 19. To verify that user can fill the timesheet using repeated task for same day. 20. To verify user can fill the timesheet for more than 12 hours. "412Start and finish dates of all allocated tasks must be displayed to the user.,1. Examine that the list of all projects assigned to employee is display in 'Project Details' field functionality. 413Both the admin and the employee should have the accessibility to edit their saved timesheet.,1. Verify 'Edit Timesheet' pop-up displays on screen when user click on 'Edit Timesheet' functionality. 414Any extra or unnecessary timesheets of employee or admin can be deleted using this functionality.,1. Verify user can delete the filled timesheet using 'Delete Timesheet' functionality. 415Timesheet provided by an employee should include an interface where an admin can approve or reject the timesheet.,"1. To view response of application when user click on 'Approve Timesheet' module 2. Check timesheet submitted by employees is displayed on 'Approve Timesheet' screen. 3. Verify on selecting 'Month and Year' dropdown, admin can view a employees monthly recieved timesheet for approval. 4. To Approve/Reject the employee's received timesheet, verify 'Reject and Approve' button functionality. 5. Check 'Show Entries' field functionality. 6. Check 'Search' field functionality. 7. Make sure, using 'Previous and Next' button user can view previous and next page of received timesheet. "416Admin should have the authority to view the employee's timesheet details using a view function. Filters can be used to see timesheet information for a specific date.,"1. Validate Action's Eye icon functionality, so admin can Reject/ Approve the employee's timesheets. "417 Application should contain a task master screen where details of task will be displayed. Admin canadd new task by utilizing Add task function.,"1. Validate whether admin redirects to the Task Master screen when 'Task Master' module is clicked 2. Check the 'Add Task' field functionality to see admin can assign a new task to employee. 3. To display more entries of the inserted Task Name, validate working of 'Show Entries' dropdown. 4. To search any record present under Task Name table, check 'Search' field functionality is present on page. 5. Using Previous and Next button user can able to view pages of added task names. 6. To arrange the list of employee records in ascending or descending order, check the sort functionality. "418Edit Task Function allows authorised users to change and amend task details.,1. Check 'Edit Task Name' pop-up display when user clicks on 'Edit Task Name' functionality. 2. To verify whether user can add duplicate task name using 'Edit' functionality. 419Delete Task function allows authorized users to remove tasks that are no longer required or have been mistakenly created.,"1. Ensure that after clicking the Delete icon, an admin can delete the added task name. "420 Timesheet records from the past and related data are accessible to authorised individuals for examination.,"1. Check employee history sub-modules displays after user clicks on Employee History module. 2. Verify the View Employee History tab's functionality.All of the features on this page should be displayed after clicking this tab. 3. Make sure admin can view employee's monthly timesheet history using 'Month' functionality. 4. For a specified time period, use the 'From' and 'To' date features on the 'View Employee History page to view and download an employee's filled timesheet. These values should be mandatory. 5. Make sure the 'Show Entries' option is selected if you want to see additional entries. 6. Check 'Select Employee Name' dropdown functionality to select employee name. 7. Check the pagination so that you can view pages of an employee's history of completed timesheets by clicking Previous and Next. 8. Using 'Excel Export' button, Make sure user can download the employee's filled timesheet history file. 9. Check Search field's functionality. 10. Check Show button's functionality. 11. To arrange the list of employee records in ascending or descending order, use the sort functionality. 12. Check the response of the application when mandatory fields remain unselected and the show button is clicked. "421Unfilled Timesheet Record Module keeps track of employees' missing or unfilled timesheet records and notifies individuals who haven't turned in their timesheet by the deadline.,"1. Check Unfilled Timesheet Record screen displays when user clicks on Unfilled Timesheet Record module. 2. Check From and To Date functionality, so admin can view employee's unfilled timesheet history for a particular date range. 3. Check functionality of Show button. 4. Using Excel export functionality, make sure admin can download the employee's unfilled timesheet record. 5. Check Search field's functionality. 6. Check show Entries field's functionality. 7. Check that the Previous and Next Buttons on the Unfilled Timesheet Record Page are working. 8. To arrange the list of employee records in ascending or descending order, use the sort functionality. "422Consolidated Unfilled Timesheet Record Module provides a consolidated view of unfilled timesheets for all employees and enables admin to discover employees whose timesheets are missing or incomplete.,"1. Check by clicking on consolidated unfilled timesheet record sub-module, user redirects to the consolidated unfilled timesheet record. 2. Check on click on 'Display' button, consolidated timesheet record displays on screen. 3. Check 'Search' field's functionality. 4. To view more entries, check functionality of 'Show Entries' field's functionality. 5. Check functionality of 'Previous' and 'Next' buttons present on screen. 6. Using 'Excel Export' button, Make sure user can download the employee's Consolidated unfilled timesheet Report. 7. To arrange the list of employee records in ascending or descending order, use the sort functionality. "423Admin should get thorough reports based on consolidated timesheet data using the Consolidated Timesheet Report Module.,"1. Validate whether 'Timesheet Report' submodule displays when user click on it. 2. To verify consolidated timesheet report screen displays when 'Consolidated Timesheet Report' submodule is clicked. 3. Make sure using 'Display' button, Admin can view information of employee's monthly attendance. 4. Using 'Excel Export' button, Make sure user can download the employee's Consolidated timesheet Report. 5. Check Show Entries field's functionality. 6. To search record present under 'Consolidated Timesheet Report', check 'Search' field's functionality. 7. Check the 'Upload File' button to see if an admin can manually upload a file for generating a report. 8. Check functionality of 'Previous' and 'Next' buttons present on 'Consolidated Timesheet Report' screen. 9. To arrange the list of employee records in ascending or descending order, use the sort functionality. "424Admin shall be authorised to generate the thorough reports using information provided by the individual employees for their respective projects.,"1. Check whether project timesheet report screen displays when user clicks on 'Project Timesheet Report' module. 2. Check 'Financial Year' field's functionality present on 'Project Timesheet Report' screen. 3. Check functionality of 'Start Date' and 'Next Date' field's functionality. 4. Check 'Customer Name' field functionality. 5. Validate project names displays when user clicks on 'Select Project Name' dropdown. 6. To verify employee name displays when 'Select Employee Name' dropdown is clicked. 7. To download Project Timesheet Report's excel sheet, check 'Excel export' functionality present on screen. 8. Check 'Show entries' field's functionality present on 'Project Timesheet Report' page. 9. To search any record present under Project Timesheet report table, check 'Search' field functionality is present on page. 10. Check 'Previous' and 'Next' button functionality present on 'Project Timesheet Report' page. 11. To arrange the list of employee records in ascending or descending order, use the sort functionality. 12. Using the 'Select Location' field, check whether the admin can view or download the project timesheet report for the chosen location. "425" Employees In/Out Reports, according to the Excel export report capabilities shall be available for download.","1. Make sure 'Timesheet In/Out Report's ' submodule displays when user click on it. 2. Examine excel export screen is shown to user when 'Excel Export' sub-module is clicked. 3. Verify whether employee names are displayed on screen when 'Select Employee Name' dropdown is clicked. 4. Examine the 'From Date' and 'To Date' fields on the Timesheet In-Out report screen for functionality. 5. Using Export Excel' functionality, make sure that admin can download employee's Timesheet In/Out Report. 6. Examine the 'Search' field's capability, which displays information based on searches. 7. Check the 'Show Entries' functionality if you want to see additional entries. 8. Test the 'Previous' and 'Next' button functionality on the Excel Report Page to view Records. 9. To arrange the list of employee records in ascending or descending order, use the sort functionality. 10. Check 'Show' button's functionality. 11. To verify the response of the application, when mandatory fields remain unselected and the show button is clicked. 12. Check the search functionality of the 'Select Employee Name' dropdown. "426 Timesheet's history can be viewed by the employee using the View History module. The user can use the search feature to locate a certain timesheet record.,"1. To verify user can navigate to view history screen after clicking on 'View History' module. 2. Check View History page contains information about all filled timesheets in tabular form. 3. To view more entries of filled timesheet, make sure 'Show Entries' functionality is present on screen. 4. Using 'Search' field functionality, check user can able to search the entry present in list of view history page. 5. Check user redirects to the correct page when clicked on Previous and Next button. "427Submitted timesheet's details can be seen by an admin or employee using the View Timesheet functionality.,1. Check View Timesheet' icon functionality. 428Login page should allow user to access the OCR web-application with valid credentials.,"1. Check when user enter the application URL into the browser. 2. Check the outcome when userenter a URL into the browser's URL fields. 3. Checkif the userclick on the Login button with the valid username and valid Password . 4. Examine functionality of Login button when both Username and Password fields are left empty. 5. Determine if the username fieldis left empty and the Password field is filled in, click the Login button to display the results. 6. Examinethe login functioning when the user inputs their username but leaves the password fieldempty. 7. Check If the userclick the Login button using an invalid Username and Password. "429"After user login, the system shall display the list of existing customers & it's details such as name of the customer, contact person, license type, activation & expiry date & number of users. It should enable users to search for a customer.",1. Make sure that user are able to view Dashboard and its all functionalities . 2. Examine the customer's table details in the dashboard page. 3. Determine the edit icon feature for customer dashboard to update a specific customer details from the list. 4. Check the dashboard page search functionality for customer. 5. Check show entries functionality on dashboard screen where user can choose number from show entries dropdown. 6. Check for pagination- Previous and next button functionality for user. 7. Ensure the admin role functionality for the customer dashboard. 430The system shall provide a 'Add Customer' page where Admin can create a new customer by filling in customer's contact and license details. The newly created customer shall be displayed on the Dashboard.,1. Check the add customer button functionality to add a specfic customer . 431"The system shall provide a 'Edit Customer' page where users can update customer's contact & license details such as Contact Person Name, Contact Address, License Type & Expiry Date. The modified details of customer shall be displayed on the Dashboard.",1. Check the Edit Icon functionality to update the customer information. 2. Examine the save button's functionality to ensure that the modified customer's details was saved. 3. Check the reset button functionality into update customer page. 432"The user shall remove an existing customer using 'Delete Customer' functionality. The system shall display a confirmation pop up where user should choose to abort or continue the operation. Upon user confirmation, the selected customer shall be removed ...",1. Check the functionality of delete customer information 433"The Project Homepage shall display the list of existing projects & it's details such as name of the Customer, Project name & Project Manager. It should also enable users to search for a Project.","1. Ensure that the user is able to see the project home page 2. Ensure user can click on Project tab from side menu bar 3. Check show entries functionality on project homepage screen where user can choose number from show entries dropdown. 4. Check to make sure that the project dashboard page has search functionality for users. 5. Check pagination functionality for the next, previous button. 6. Examine the submitted project table details "434"The system shall provide a 'Add Project' page where users can create a new Project by filling in Project details such as Project name, Document Type & Project Manager. The newly created Project shall be displayed on the Project Homepage.",1. Ensure that the user canadd a project for a customer. 435The system shall provide a 'Edit Project' page where users can update Name of the Project & Project Manager. The modified details of Project shall be displayed on the Project Homepage.,"1. Ensure that user can edit a customer project in terms of following fields Project Name & Project manager. 2. On clicking on 'Project tab', click on the 'Edit' icon of Action field, keep the form details blank and hit the 'Submit' button. 3. On clicking on the Project tab, click on the Edit icon, fill in all mandatory fields with the required data, and click on the Submit button. "436"The user should be able to remove an existing Project using the 'Delete Project' functionality. The system shall display a confirmation pop-up where the user should choose to abort or continue the operation. Upon user confirmation, the selecte...",1. Check user can Delete project for customer 437"The User Homepage shall display the list of existing projects & it's details such as name of the Customer, User ID, Name of the User, it's Role & User status. It should also provide an option to search for a user.",1. Check no. of users on Customer home page for a customer 2. Check user tab from side bar. 3. Check the user can view all features on the user's home page. 438"The system shall provide a 'Add User' page to create a new user by filling in user details, its role & contact details. The newly created user shall be displayed on the User Homepage.",1. Check the Add user option in terms of visibilablity & clickable 2. Check Add User functionality for user module. 439"The system shall provide a 'Edit User' page where users can update Name of the User, Reporting Manager, Employee ID, Email ID, Contact Number & Status. The modified details of User shall be displayed on the User Homepage.","1. Check Edit Icon for user module :- User Name, Reporting To, Employee id , Email id & Contact Number. "440"The Customer Admin should be able to remove an existing User using the 'Delete User' functionality. The system shall display a confirmation pop-up where the user should choose to abort or continue the operation. Upon confirmation, the selected...",1. Check the Delete Icon functionality 441" The Assign Project Homepage shall display the list of all assigned projects & it's details such as name of the user, start & end date of assignment. It should also provide an option to search for a project.","1. Users can easily access the 'Assign Project' module from the side menu bar. 2. Clicking on the Assign Project tab displays the homepage of the Assign Project module. 3. Examine the assigned projecttable details 4. Users have the option to select the number of entries to display in the list, providing flexibility in customizing the view according to their preferences. 5. The project homepage includes a search feature that allows users to easily search and find specific projects based on their desired criteria. 6. Users can click on the pagination buttons, such as Previous and Next, on the Assign Project homepage to navigate and display different pages, enabling seamless browsing and access to desired content. "442" The Assign Project page shall allow Customer Admins to assign an existing project to the user by selecting the Project name, username, activation date & expiry date for assignment.","1. Check that when the user clicks on the Assign Project button, the user will navigate to the Assign Project page. 2. Ensure that the assigned project is properly saved in the system 3. By clicking the reset button, users can easily undo any changes made and restore the form to its initial state "443The update operation shall allow user to update the expiry date of the assigned project for any users.,1. The Edit Icon functionality allows users to update the assigned project information easily by clicking on the edit icon associated with each project entry. 444The 'Delete Assigned Project' functionality should allow the user to remove the allocation of a project to a user permanently. The system shall display a confirmation pop-up where the user should choose to abort or continue the operation. Upon...,1. The Delete Icon functionality on the assigned project screen enables users to delete a specific project entry by clicking on the delete icon associated with it. 445 The Vendor Homepage shall display the list of existing vendors. It should also enable users to search for a Vendor among the existing ones.,1. Clicking “Vendor” enables the user to see Vendor Details. 2. Check for pagination- Previous and next button 446"The system shall provide a 'Add Vendor' page where users can create a new Vendor by filling in details such as Vendor name, Process & Sub-process. The newly created Vendor shall be displayed on the Vendor Homepage.","1. Examine the vendor add feature, allowing users to add vendor information "447 The system shall provide an 'Edit Vendor' page where users can update the sub-process for a vendor. The modified details shall be displayed on the Vendor Homepage.,"1. Check the Edit Icon functionality for update vendor information. 2. On clicking onVendor tab , click on the Edit icon of the Action field,keep the given form details blank and hits submit. "448"The user should be able to remove an existing vendor using the 'Delete Vendor' functionality. The system shall display a confirmation pop-up where the user should choose to abort or continue the operation. Upon confirmation, the selected Vendo...","1. Check the vendor delete feature, which enables users to remove vendor information "449The Document Homepage shall display the list of all existing documents. It should also provide an option to the user to search for a document type.,"1. Make sure that users can view the document homepage and its all functionalities 2. Ensure that the Document tab is in the side menu bar. 3. User should have permission to view the Document table details 4. Users have the option to select the number of entries to display in the list, providing flexibility in customizing the view according to their preferences. 5. The document homepage includes a search feature that allows users to easily search and find specific document based on their desired criteria. 6. User tries to navigate on one page to another page by clicking on Next button and Previous Button "450The system shall provide a 'Add Document' page where users can create a new Document by filling in name of the document & adding fields for extraction. The newly created Document shall be displayed on the Document Homepage.,1. Check the add document button functionality to add any document . 451The system shall provide an 'Edit Document' page where users shall add new fields or remove existing fields for a document.,1. Check the Edit Icon functionality for update document type. 452"The user should be able to remove an existing Document using the 'Delete Document' functionality. The system shall display a confirmation pop-up where the user should choose to abort or continue the operation. Upon user confirmation, the selec...",1. Make sure that user can 'Delete' an uploaded document type permanently. 453 Project Selection screen shall allow user to select the name of the projects to view its templates on the Template Homepage.,1. View Project selection page functionalities when the user clicks on templete. 2. Make sure the customer and project name dropdown is working. 454 The Template Homepage shall display the list of all templates & it's details such as name of the vendor & type of document. It should also provide an option to search for a template.,1. View Add Templete dashboard and their specification. 2. Examine the customer's detail table in the template dashboard. 3. The Template homepage includes a search feature that allows users to search easily and find specific template details based on their desired criteria. 4. Check show entries functionality 5. Check for pagination- Previous and next button 455" The screen shall allow the user to create a new template by filling in details such as Vendor, Approach for extraction, etc. & upload the training document. It shall allow the user to mark required field values on the document to train the template. It ...",1. Validate the add button functionality after clicking on the Add Template button should be available. 2. Examine the Upload file functionality that users are able to select files using choose file feature. 3. Identify the buttons that allow users to add templates with the create button and navigate back a page with the back button. 456Label Data screen shall allow user to mark required field values on the document & assign label to it for all uploaded documents.,"1. Make sure that the uploaded documents are present in (left) pane 2. Ensure that the user can select an uploaded document from the left pane 3. Ensure that the indicator indicates red color when tagging is pending on the document. Once tagging is completed successfully it turns green. 4. Ensure that the user can click on Run Layout button. 5. Ensure that the user can draw a boundary box to tag a field value. 6. Ensure that the user can select the value from the documents 7. Check the field label textbox below the value tagged on the document 8. The user can either drag and drop documents from their local system or use the traditional file browsing method to upload documents. 9. Make sure that the user can select document 10. The user has to add minimum 5 documents to train the template otherwise a notification is displayed 11. To ensure that the selected document is displayed on the screen 12. Ensure that the user can enter label in field label textbox 13. The user can select the field type from the following options: Field, Checkbox, Signature. 14. Make sure that the selected field label contain field numbering 15. Analyze, once the field type is defined in the previous step, the field label along with value is displayed in the Fields (right) pane 16. By clicking on 'More Options' in the fields (right) pane, the user can customize the settings or options according to their specific requirements. 17. Ensure that the user can select sub-options of the subtype. 18. The user can select No Data from the More Options in the field(right) pane. This option allows the user to indicate that field value for the selected field is not available in the document. 19. The user should be able to select the 'Rename' option from the field pane to modify or change the label or name of a particular field 20. Ensure that the user can delete the field label from the field (right) pane 21. Ensure that the user can remove the field value by clicking on the 'Remove field value' icon 22. Check for pagination- previous and next buttons by clicking on the respective buttons. 23. Check user can rotate the documents by clicking on rotate button on the label data page 24. Check user can zoom in the documents by clicking on zoom-in icon 25. Make sure that the user can zoom out the documents by clicking on zoom-out icon on label data page. 26. Ensure that the 'Train' button is enabled when all the fields on all the training documents are tagged, allowing the user to train the tagged information. "457The template summary screen shall display the fields trained in a template & it's accuracy score in percentage.,1. Check the template summary page features. 2. Examine the summary details in table 3. Make sure the back button functionality where the user can go back to the previous page. 4. Check show entries functionality 5. Check for pagination- Previous and next button. 458 The test Template screen shall allow the user to upload documents to test the trained template. It shall display the results annotated on the document. The user should also be able to download the results into Excel or CSV format.,1. Check the test Template button functionality on the right side of the screen and its specifications. 2. Validate the Zoom In and Zoom out functionality that allows users to zoom out or into the document 3. Determine the rotate functionality where the user can rotate the document in clockwise direction by 90 degrees. 4. Check the pagination functionality for the previous and next buttons. 459The Edit Template screen shall allow the user to modify DPI & add new or remove existing fields. It shall allow the user to re-mark the required field values on the document to re-train the template. It should also cater to testing the trained template ...,"1. Ensure that the user is able to modify the existing train template using the edit functionality. 2. Check the result download functionality in right pane of the page where the user can able to download the extracted result in a selected format like Excel, CSV, or JSON. "460"The 'Delete Template' functionality should allow the user to remove an existing template permanently. The system shall display a confirmation pop-up where the user should choose to abort or continue the operation. Upon confirmation, the user&a...",1. Check the functionality of the delete icon where the user can remove the existing template from the list and a valid popup message should be displayed on the screen. 461" Upload document functionality shall allow users to upload batch documents, folders & single documents & preview the results on the 'Preview' screen. It should also provide an option for the user to download the outputs in Excel or CSV format.",1. Validate the document drag & drop zone functionality to the user select the document. 2. Determined the drag-and-drop document zone where the user can select multiple files to upload the document. 462"Admin user can see the list of submodules and with the help of that admin can raise the Incident Request for himself and also see the list of raised incident tickets, also he can share the screenshots, additional comments as well",1. Make sure that by clicking on the Self Service module the sub-modules list appears on the sidebar 463"With the help of this module admin can raise the incident ticket by adding only the description of issue, also he can select the urgency and attach the screenshot of the issue","1. Evaluate that the admin user can see the incident record form by hitting on Create New Incident submodule 2. Make sure that the Caller, Number and Opened fields are read only 3. Check and make sure that the Closed field is not clickable and empty 4. Validate the functioning of the Submit button by filling the necessary data 5. Ensure the performance of Submit button without filling in mandatory fields, the error message appears on the screen 6. Examine the working of the Reset button, by clicking on it, the incident record page gets reset "464" Admin can see the list of self created incident in the tabular format with Search and Sort functionality, also he can provide the additional information and update the ticket","1. Confirm that by pressing on the All submodule, the list of all created incidents appears on the page 2. Check the operating purpose of breadcrumbs, user can navigate to desired page with single click 3. Examine by entering valid data then regarding entries of incidents should appear on the page 4. Ensure the performance of Show Entries by selecting the number then same or if not available then less than selected number of entries get visible 5. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 6. Make sure by clicking on paginations user is navigating to respective pages 7. By clicking on Incident Number confirm the process of Update button, user can update the state and urgency, upload the attachments and also post the additional comments 8. By pressing on Incident number confirm the functioning of Reset button that user can reset the updated data 9. By clicking on Incident Number Ensure the performance of Back button, user should navigate to the back page 10. Evaluate that user can resolve the self created incidents by selecting the state Resolved 11. Test the functionality of Reopen button without posting the additional comments 12. Verify and validate by posting the additional comments and clicking on Reopen button the incident ticket reopens 13. Make sure by clicking on Close button, the incident will be closed "465"It is the process by which a lender/banker appraises the technical feasibility, economic viability and bankability including creditworthiness of the prospective borrower. In short, it reflects Employees hard work and the outcome enhances their morale.","1. Ensure that the user can easily navigate from the View Appraisal Letter screen to the Home screen of the Payroll Management System using the Home navigation functionality. 2. Make sure that when the user navigates to the view appraisal letter screen, they can see the data table containing appraisal details if the appraisal is done by the admin. 3. Examine the dropdown menu with options available provided for the Show Entries capability to display many entries on a single page. 4. Check to see if the search feature displays the right results if the user enters any text in the field. 5. Ensure that the Next pagination feature may be used by the user to move to the next page and view more entries. 6. Ensure that the Previous pagination feature is available to get back to the previous page and view earlier entries. 7. Examine that the View Appraisal Letter page's corresponding section, fields, and buttons are displayed with the correct alignments, spellings, font sizes, and font families. 8. Make sure that the View functionality shows the review of the appraisal letter that has been uploaded by the admin for the respective user. 9. Ensure that Appraisal Letter will be downloaded in PDF format once the user clicks the download button. 10. Ensure that the Preview Appraisal Letter is protected with a password and can only be accessed using a valid password. 11. Examine whether the downloaded Appraisal letter is protected with a password, and ensure that users can access it using a valid password. "466" The user can view and download the Form 16. Employees are required to obtain Form 16 from their employers to accurately report their income, deductions, and tax payments when filing their income tax returns. Form 16 is a document issued by employers in ...","1. Make sure the user can navigate to the Payroll Management System's Home screen using the Home navigation functionality from the Form 16 screen. 2. Examine that once the user navigates to the Form 16 screen where firstly they see Form 16 for the current year. 3. Make sure that to select the year of Form 16 the dropdown functionality is available to the user on the screen of Form 16. 4. Ensure that Form 16 is displayed for the selected year once the user clicks the Go button, and if Form 16 is not present for that year, then the pop-up message is displayed. 5. Confirm that the user will visible the Download button when they click the Go button after choosing the year and month and if Form 16is present for that month. 6. Ensure that Form 16will be downloaded in PDF format once the user clicks the download button. 7. Examine that the Form 16 screen's corresponding section, fields, and buttons are displayed with the correct alignments, spellings, font sizes, and font families. "467 Admin will login using the valid credentials. Admin needs to enter the correct ID and Password to log into the application.,"1. Confirm that the login page works properly with the correct Username and Password. 2. Examine the Eye icon's capabilities in the password field. 3. Use an inaccurate username and password to test the login page. 4. Use an incorrect username and correct password to test the login page. 5. With an authentic Username and a faulty Password, check the login page. 6. The login button should be verified with an empty username and password field. "468" When the user clicks on the Business Requirement module, the list of the requirements will appear in the projectname they have selected in the Select Project dropdown. Users can select different projects from the dropdown Test Scenario will have the...","1. Ensure that the 'Business Requirement' module is successfully opened and accessible for further actions and operations. 2. Ensure that the user can select the specific project from the Select Project dropdown field and as per the selection of the project the data is accurately reflected in the field. 3. Check that there are no blank values present in the dropdown list of the Select Project field. 4. Check that the project dropdown list contains all the required values with correct spelling. 5. Make sure the dropdown menu for select project is precisely aligned. 6. Ensure the user can only see the client name which is presented in the header on the BR module page. 7. Ensure the functionality of the Status field on the BR module page and the Project Status is displayed in the three categories. If it is in the Active list, it is displayed in green. 8. Check the project ID is appropriately shown on the BR module page. 9. Make sure the tester name dropdown is clickable and all assigned tester list is displayed in the tester name field on the BR module page. 10. Ensure that the end date of the project is displayed in the format of DD-MM-YYYY on the BR module page. 11. Ensure that the start date of the project is displayed in the format of DD-MM-YYYY on the BR module page. 12. Make sure the count of bugs for the selected project is accurately displayed as per the assigned bugs in the bug module and the user can only view it on the header. 13. Check the search functionality by entering the valid keyword in the search box. 14. Assess the operational functionality of the dropdown feature in the Show entries field. 15. Evaluate the functionality of the next icon's from the pagination. 16. Ensure the operational performance of the previous icon from the pagination in terms of its functionality. 17. Ensure the sorting arrow functionality in the Br Id, Business requirement, and Business requirement Description fields. 18. Check the data table of the business requirement module. 19. Confirm the alignment of the entire data table in the 'Business Requirement' module. 20. Check that the search box handles invalid search queries gracefully. 21. Ensure that the selected filter value is displayed in the filter. 22. Check the show entries dropdown field to ensure that it correctly incorporates the highlight functionality. 23. Check that the sorting option works in both 'Ascending' and 'Descending' order. 24. In the Business Requirement module, Ensure that all fields as per requirements are present. "469Business Requirement module with 'Add Business Requirement ' functionality.,"1. Ensure that, upon clicking on the Add Business Requirement option, a pop-up window opens successfully. 2. Ensure the correctness and proper functioning of the BR_ID field. 3. Examine that the Business Requirement text field is functioning correctly 4. Examine that the Business Requirement description text field is functioning correctly. 5. Check the save button functionalities on the 'Add Business Requirement' popup window. 6. Ensure the reset button functionalities on the Add Business Requirement popup window. 7. Check the data table 'Business requirement' module to ensure that all entered data by the user is reflected in the data table. 8. Examine the functionality of the delete button which is located in the action field in the 'Business requirement' module. "470"The business Requirement module will be available for Tester, Business Analyst, and Admin in edit mode There will be an edit option in the action column in the Business Requirement module.",1. Evaluate the performance of the edit button functionality within the action column. 2. Ensure the 'Update' button functionality. 471" Access of delete in Business Requirement module will be for Business Analyst, Tester, and Admin. There will be a Delete option in the action column in the Business Requirement module.",1. Examine the 'Delete' functionality from the action column of the 'Business Requirement' module. 2. Check the alignment and size of the 'Delete' icon from the action column. 472" For the Tester, Business Analyst, Developer, Administrator, and Project Manager, the Business Requirement Module will be in the expand icon.",1. Examine the expand view functionality of the action field. 2. Check the alignment of the expanded table of the selected row. 3. Examine the entire table view of the Business Requirement page. 4. Examine the alignment of the entire table to ensure accuracy. 5. Ensure that all added BR is displayed in table format with accurate data. 473"The summary module will operate in view mode, allowing testers, business analysts, project managers, developers, and administrators to access and review data from previous entries.","1. Ensure that the page for the 'Bug Summary' module is currently open, confirming its accessibility. 2. Test the proper functioning of the dropdown feature in the Select Project field. 3. Ensure that the select project dropdown list does not contain any empty values by checking for the presence of blanks. 4. Check that all the necessary values with accurate spelling are present in the project dropdown list by thoroughly checking and confirming their inclusion. 5. Ensure that the provided alignment of a select project dropdown list accurately corresponds to the required specifications. 6. Check the client functionality of the 'Bug Summary' module page. 7. Ensure the proper functionality of the start date field on the 'Bug Summary'module page. 8. Assess the functionality of the end date field on the'Bug Summary'module page. 9. Check the functionality of the show entries field with the dropdown feature. 10. Confirm the functionality of the dropdown menu in the show entries field. 11. Ensure the functionality of the next page icon, verifying that it accurately navigates to the subsequent page without any errors or glitches. 12. Ensure the functionality of the previous page icon. 13. Confirm the accuracy of the 'Req Id' column by cross-referencing and confirming its contents against the data stored in the data table. 14. Examine the contents of the 'Test Scenario' column within the data table to ensure its accuracy and alignment with the expected data. 15. Examine the 'Test case ID' column within the data table to ensure its accuracy and consistency. 16. Check the 'Defect Area' column in the data table to ensure its accuracy and consistency. 17. Confirm the integrity and accuracy of the 'Developer' column within the datatable. 18. Examine the contents of the 'Tester' column within the datatable to ensure its accuracy and consistency. 19. Examine and cross-reference the 'Closed' column within the data table to ensure its accuracy and consistency. 20. Check the contents of the 'open' column within the datatable for accuracy and consistency. 21. Ensure the 'Reopen' column in the datatable for confirmation and accuracy. 22. Confirm the accuracy of the 'Total' column in the datatable. 23. Evaluate the search functionality of the search box. 24. Ensure that the search results are relevant to the search query. 25. Test the show entries field dropdown functionality with the required values. 26. Check the show entries dropdown field to ensure that it correctly incorporates the highlight functionality. 27. Ensure that all required fields are present on the 'Bug Summary' module. "474" When the user clicks on the Test Plan module, the list of the test plans will appear in the projectname they have selected in the Select Project dropdown. This module typically has Fields such as Introduction, In scope, Out scope, Quality Objective...","1. Check the Navigation and Display of Test Plans upon Clicking the Test Plan Module. 2. Make sure the dropdown menu for select project is precisely aligned. 3. Ensure the user can only see the client name which is presented in the header. 4. Assess the operational effectiveness of the project name field on the Test Plan module page. 5. Make sure the tester name dropdown is clickable and all assigned tester list is displayed. 6. Confirm that the Test Plan page is currently open with a click on the 'Test Plan' module. 7. Check to see if the select project dropdown is clickable and assigned project list is displayed in the dropdown. 8. Check the Project Status is displayed in the three categories. If it is in the Active list, it is displayed in green. 9. Make sure the count of bugs for the selected project is accurately displayed as per the assigned bugs in the bug module and the user can only view it on the header. 10. Examine by clicking on the Test Plan Status dropdown the list of the statuses is displayed and allows the user to choose one. 11. Check the project ID is appropriately shown on the Test Plan module page. 12. Ensure that the end date of the project is displayed in the format of DD-MM-YYYY on the Test Plan module page. 13. Ensure that the start date of the project is displayed in the format of DD-MM-YYYY on the Test Plan module page. 14. Check the search functionality by entering the valid keyword in the search box. 15. Make sure that the test plan appears in the Test Plan Module in a table format along with its version once it has been saved. 16. Check the alignment of the entire data table in the 'Test Plan' module. 17. Make sure that added test plan, shows up in a table with its version, making it easy to see. 18. Examine the search functionality when the user copies and pastes the parameter and clicks on search. 19. Ensure that the search results are relevant to the search query and that the correct results are displayed. 20. Verify the search functionality by entering the invalid keyword in the search box and ensure no matching records are displayed message is displayed. "475"The test plan can be added by the Administrator, Project Manager, Tester, and Business Analyst. Users can save and add test plans by clicking on the 'Add Test Plan' button available above the action column.","1. Confirm that a pop-up window opens after clicking on the Add Test Plan option. 2. Make sure the Introduction section allows the user to write an introduction, scope, quality objective, roles, and responsibilities of the project to the test plan and that any alphanumeric data may be entered. 3. Examine in the 'Test Methodology' area, the user can include an overview, test level, issue triage, and test completeness of the project. 4. Confirm the 'Test Deliverables' field allows the user to add test deliverables of the project and that any alphanumeric data may be entered. 5. Ensure that in the 'Resource and Environment Needs field user can add testing tools and test environment. 6. Ensure that after clicking on the Save button the test plan is successfully saved. 7. Check that when the user clicks on the Reset button all the entered data in the test plan fields get clear. 8. Make user can easily add a Terms and Acronyms of the project in the Terms and Acronyms field. "476"Editing and updating the test plan will be possible for the Administrator, Project Manager, Tester, and Business Analyst. Users can save and edit their test plans by clicking the edit icon in the action column.",1. Check the functionality of the edit button in the action field to ensure that it works as intended. 2. Ensure that the user can edit all the fields present in a test plan successfully. 3. Examine that the edited test plan is successfully saved after clicking on the Update button and the updated test plan is displayed in the table. 4. While editing a test plan check that when the user clicks on the reset button all the entered data in fields gets clear. 477" The Administrator, Project Manager, Tester, and Business Analyst will have access to delete the test plan. Users can delete the test plan by clicking the delete icon which has been given in the action column.",1. Check the functionality of the delete button in the action field. 2. Ensure that the confirmation message on the popup or alert is shown as the user clicks on the delete button. 3. Make sure the record will not be deleted as the user clicks on the NO on the confirmation popup. 4. Ensure that the delete functionality works as the user clicks on the YES button on the confirmation popup. 478"Users can make the test plans more readable by clicking the view icon in the action column. The test plan will be viewable by the Administrator, Project Manager, Tester, Developer, and Business Analyst.",1. Examine whether the user can view the added test plan by clicking the view icon. 2. Check the alignment of a test plan for the 'View pdf'. 3. Make sure the user can download a test plan by using the Download button functionality. 4. Check the functionality of the close button in the view pdf page. 479All of the candidate's information is shown in the seeker's section. The user will have the ability to change the candidate's information.(Inactive),"1. The user can add the candidate to the application by clicking the Add Candidate button. (Inactive) 2. If the user needs to re-enter all information into the Add Candidate form, they can use the Reset button to clear everything from the form.(Inactive) 3. Users can utilize the Select recruiter dropdown to sort the data in the table based on the recruiter's name.(Inactive) 4. Ensure that to find the details from the table, the user can search the value in the search bar.(Inactive) 5. Using the Show Entries dropdown, the user can expand the details with the selected count into a table.(Inactive) 6. Users can rapidly access all of the information about a specific candidate by clicking on the Eye icon.(Inactive) 7. If the user needs to change any details about the candidate, using the edit icon in the action column, they can update the information.(Inactive) 8. Check the Excel option to obtain all of the data in tabular format.(Inactive) 9. Check that the count on the bottom left side displays how many records are presented in the table with the overall count.(Inactive) 10. Check the PAGINATION button capability at the bottom right side of the Seeker table to display the candidate's PREVIOUS and NEXT page information in the Seekers table.(Inactive) "480 The dropped part contains information about candidates who were removed from the tracker's area. The user will have the authority to return the applicant to the dropped area of seekers.(Inactive),"1. A user can sort the data in the table by selecting a recruiter from the Select recruiter menu.(Inactive) 2. The user can easily download all of the data displayed in the dropped section by clicking the Excel button.(Inactive) 3. The payment To find a specific record of data, users can type a value into the search bar. (Inactive) 4. The user can expand the details on the table to inspect the details by using the show entries dropdown. (Inactive) 5. The Seeker icon allows the user to move a candidate record from the dropped area to the seeker section. (Inactive) 6. To verify the entry count presented in the table, it is displayed in the bottom left corner of the screen with the total number of entries. (Inactive) 7. The user can view the Next and Previous page details on the screen by using the Pagination buttons. (Inactive) "481The Super Admin and Admin can view a previously created policy document in the policy management dashboard.,1. To ensure that both Super Admin and Admin are able to view a previously created policy document in the policy management dashboard. 2. Make sure alignment of table and viewed policy data is properly aligned. 482The Super Admin and Admin can edit a previously created policy document in the policy management dashboard.,"1. In the policy management systemdashboard, ensure that both the Super Admin and Admin can edit a previously created policy document. "483"If any policies are under review status, the Super admin will approve the policy using the Approve action in the policy management dashboard.",1. To make sure that the Super Admin can successfully approve a policy which is having Under Review status through the policy management systemdashboard's Approve action. 484"If any policies are under review status, the Super admin will reject the policy using the Reject action in the policy management dashboard.",1. To check that the Super Admin can successfully reject a policy which is having Under Review status through the policy management systemdashboard's Reject action. 485"If the Admin wants to publish the policy, they should have the Super Admin approval. If the Super Admin approves of the policy, the admin can publish the policy using the Publish Action in the policy management dashboard.",1. To make sure that an Admin can successfully publish a policy in the policy management dashboard after the Super Admin has approved it. 486"Policy sections act as additional sub-sectional modules that will let the user to add desired sections to a policy which contains details related to any topic, if needed.",1. To ensure that the Super Admin and Admin can successfully add a new section to a policy in the policy management dashboard. 487"In terms and conditions, the Admin/Super Admin can specify the terms and conditions, as per specific policy.",1. Make sure that the Admin and Super Admin can successfully specify the terms and conditions for a specific policy in the policy management dashboard. 488"In conclusion, Admin/ Super Admin can add policies conclusions, as per specific policy.",1. To ensure that the users can successfully add a conclusion to a policy in the Policy Management System application. 489"In Policy preview, Admin/ Super Admin can provide an overview of all the policy related information required to create a policy.",1. To ensure that users can successfully preview a policy in the Policy Management System application. 490 Super Admin/Admin can save the document as a draft.,"1. To examine 'Save Draft' button, policy details should save as draft and status of policy should be as 'In draft' . 2. To examine 'Save Draft' button, user will click on save draft button without entering policy name. "491"Once the document is created by the admin, the admin clicks on Send for Review, the document is sent for review to the Super Admin to get approval.",1. Ensure that all mandatory fields are validated before sending the policy for review. 2. Ensure that the created policies has been sent successfully to the super admin by clicking Send For Review button.. 492"If the Super Admin creates the policy, they would be able to directly publish the policy using the Publish button. If Super Admin reviews the policy, he can publish the policy by clicking on Publish button.","1. To check that the Super Admin can create, review, and directly publish a policy using the Publish button in the Policy Management System application. "493"Once the policy is published, the admin can download the document in Word format. Note: The Super Admin can download the word document of already created policy by performing click operation on 'View' icon which is in Action column.",1. Check that policy has been successfully downloaded in System's browser by clicking on download icon. 494The user should be able to click the logout button to the end session securely and prevent unauthorized access to the user account.,1. Ensure that the user's profile photo is accurately and prominently displayed next to their corresponding name. 2. Ensure that users can easily log out from the application by clicking the Logout option available in the username dropdown menu. 495" “Payslip Master” module is developed to add monthly payslip sheet for employees. Functionalities like download and edit, and monthly salary report added. In “Payslip Master” module has two tabs i.e., “Upload Payslip” and...","1. Examine the Payslip Master Dashboard, which has Upload Payslip , Search Payslip, and Generate Intern Salary Report functionality. 2. Validate the admin can upload the excel by selecting 'Month' and 'Year'. 3. Examine the Excel file will upload for the selected month and year even if the excel file name has different name. 4. Make sure the downloaded payslip name are matched with the selected month and year. "496"The system must support the functionality of assigning multiple projects to different roles and providing links to access the projects in different environments, including Development (Dev), User Acceptance Testing (UAT), and Production (Prod) using thi...","1. Check that the Application Roles page is displayed, showing the list of existing application roles. 2. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed by single click 3. Make sure that the number of entries displayed on the page corresponds to the selected option from the Show Entries dropdown 4. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries appear only 5. Verify the functionality of the Search textbox by entering invalid data in that, the error message appears on the screen 6. Validate that by clicking on pagination buttons admin user is navigating to the respective page "497The administrator should have the authority to adjust the applications that are associated with each role. This functionality provides flexibility and control for the administrator to manage the access privileges of different roles within the system by ...,"1. Check the Edit icon's functionality by clicking on it; a pop-up window with a list of applications appears 2. Evaluate the functionality of the Search textbox by entering valid data in that, the regarding entries appear only 3. Check the functioning of the Update button by selecting the application checkboxes 4. Test the functionality of the Back button, admin must navigate to the back page with a single click 5. Make sure that the list of assigned application to the role opens by clicking on the application's Plus icon 6. Check the No Application Present Message for Unassigned Application 7. Ensure that the admin can edit the assigned application, having the capability to add or remove the applications, verify the Edit icon's functioning for the same 8. Ensure that the modified applications are accurately reflected and associated with the role. "498" The administrator with the ability to view the list of added URLs for all platforms, including development (Dev), user acceptance testing (UAT), and production (PROD) with the action column","1. Ensure that by clicking on the Application URLs button, admin can see the Application URLs page 2. Make sure that the number of entries displayed on the page corresponds to the selected option from the Show Entries dropdown 3. Evaluate the functionality of Search textbox by entering valid data in that, the regarding entries appear only 4. Validate that by clicking on pagination buttons admin user is navigating to respective page 5. Validate the behavior of the system when URLs are not provided for applications. "499"The administrator has the authority to add the URLs and update them as needed. The administrator should have the capability to modify and update URLs associated with various resources, such as applications, platforms, or services. This functionality emp...","1. Examine that when the Edit icon is clicked, a pop-up window with URL fields appears on the page 2. Check the operating purpose of the Update button, by adding the URL data 3. Test the functionality of the Back button, admin navigates to the back page with a single click 4. Examine that when the Edit icon is clicked, a pop-up window with added URL fields displays on the page 5. Check the operating purpose of the Update button, by updating the URL data "500" Devotees can login into the system with login credentials.Login feature for devotees should be able to log into the system using their login credentials or devotees who are already registered. After login, Palkhi registration featurecapturing the ne...","1. Make sure the Login page contains the required fields: Mobile No., Date of Birth, and Password. 2. Ensure that the user can be able to enter their mobile no. into the Mobile number field. 3. Confirm that the user is able to enter the valid 10-digit mobile number. 4. Make sure the 'Enter Your Date of Birth' field opens a calendar for choosing a date. 5. Check the Enter Your Date of Birth field on the Login page accepts only valid dates within a specific range. Unable to update future date. 6. Make sure the user is able to enter the Password into the Password field. 7. Make sure that the Password field on the Login page has a length limit is at least 8 characters. 8. Make sure that password field accepts only @, ., _, 9. special characters. 10. Ensure that user can be able to login after entering the valid login data. 11. Make sure that user can be able to login after entering the invalid Mobile no. & valid password. 12. Make sure that user can be able to login after entering the valid Mobile no. & invalid password. 13. Ensure that user can be able to login after entering the invalid Mobile no. & invalid password. 14. Make sure that user can be able to login after entering the valid Mobile no. with default password. 15. Make sure that after successfully login Palkhi registration option displays. 16. Check whether the user is able to enter the name into 'Name field' in Palkhi registration form. 17. Check the application's response when the user enters an invalid name format (Numbers, Special characters). 18. Confirm that the user is able to enter the valid 10-digit mobile number. 19. Check that the field does not accept mobile numbers with fewer than 10-digits. 20. Check that the field does not accept mobile numbers with more than 10-digits. 21. Check whether the user is able to enter the sickness into 'Sickness field' in Palkhi registration form. 22. Make sure the selected value from the 'Identity proof' dropdown is correctly displayed in the corresponding field. 23. Check whether the 'Payment Option' dropdown is clickable in the Palkhi registration form. 24. Make sure the selected value from the Payment option dropdown is correctly displayed in the corresponding field. 25. Check whether the 'Dindi' dropdown is clickable. 26. Make sure the selected value from the 'Dindi' dropdown is correctly displayed in the corresponding field. 27. Check whether the 'Vehicle type' dropdown field is clickable. 28. Make sure the selected value from the 'Vehicle type' dropdown field is correctly displayed in the corresponding field. 29. Make sure the 'Seva Samiti' dropdown field is clickable & correctly displaying the selected value in field. 30. Check that the user can successfully select the 'Vaccination option' from Dose 1 and Dose 2. 31. Ensure the Amount field deisplay default amount value. 32. Make sure the functionality of Pay to proceed option it navigate to Payment gateway. "501 The application should provide a registration feature for new devotees. Once opening the application new Devotee can register to the system.,1. Make sure that the user can be able to click on new devotee registration feature. 2. Confirm the user can be able to enter the Mobile number into field. 3. Ensure the length of Mobile number field is 10 digits. 4. Make sure the ' Date of Birth' field opens a calendar for choosing a date. 5. Check that the Date of Birth field on the Login page accepts only valid dates within a specific range. 6. Make sure that the red * asterisk symbol is displayed for the mandatory fields. 7. Check the validation error message displayed when click on next without enter the mandatory fields. 8. Check the functionality of Next button. 9. Ensure that the user can be able to enter the First name. 10. Check the validation error message display as Invalid input when the user enters numeric characters in the name field. 11. Ensure that the user can be able to enter the Middle name. 12. Check the validation error message display as Invalid input when the user enters numeric characters in the name field. 13. Check that the user can be able to enter the Last name. 14. Check the validation error message display as Invalid input when the user enters numeric characters in the name field. 15. Make sure the Gender dropdown is clickable. 16. Ensure the on click Gender dropdown it displays the list of containing values. 17. Ensure that the by default selected value from Gender dropdown is shown in the field. 18. Make sure the Blood group dropdown is clickable. 19. Check on click the Blood group dropdown it displays the list of containing values. 20. Check that the by default selected value from Blood group dropdown shown in the field. 21. Check that after click on Birthdate field calendar open. 22. Check the Mobile number field is clickable & length of field is 10 digits. 23. Check the Alternate Mobile number field is clickable & length of field is 10 digits. 24. Check if the email field is accessible by clicking on the email field. 25. Check if the error messages display when the user enters an invalid email address. 26. Make sure the Occupation dropdown is clickable. 27. Ensure on click the Occupation dropdown it displays the list of containing values. 28. Check that the by default selected value from Occupation dropdown is shown in the field. 29. Check that the user can be able to enter the Address. 30. Make sure the State dropdown is clickable. 31. Ensure on click the State dropdown it displays the list of containing values. 32. Check that the selected value from state dropdown is shown in the field. 33. Make sure the City dropdown is clickable. 34. Ensure on click the city dropdown it displays the list of containing values. 35. Check that the selected value from City dropdown is shown in the field. 36. Check that the user can be able to enter the Pin code. 37. Check the validation error message display as Invalid input when the user enters characters in the Pin code field. 38. Check that the validation error message display when the user clicks on registration button without enter any mandatory field. 39. Check user is able to click on Registration & popup shows as Registration successfully done. 502The Dashboard should let the devotee access all modules and perform certain actions according to available options.,1. Check whether the mobile Palkhi application can be opened successfully and navigates to the Dashboard. 2. Ensure that the dashboard contains all the required modules as per the specified requirements. 503 The Side Manu Bar should let the devotee access all modules from the hamburger and perform certain actions according to available options.,1. Check whether the home page contains a side bar positioned on the left side with an icon displayed at the top of the left side. 2. Ensure that the sidebar contains all the menu items as per the specified requirements. 3. Ensure that each menu item in the sidebar is clickable & it redirecting to the corresponding section. 4. Observe whether the application's language changes after click on Marathi/English mode from Sidebar menu. 504 Devotees can be able to view the details of the committee available in this module.,"1. Make sure that the Palkhi Samiti module contain information about the Palkhi Samiti (पालखी समिती). This includes details such as the committee's purpose, responsibilities, members, contact information. 2. Check the Palkhi Samiti module contain the contact details of all Samiti members with member's name, designation, phone number in table format. "505Link of Timetable for upcoming Palkhi and the rules.The timetable should include the schedule and route details of the Palkhi process. It should also include the rules and guidelines that devotees need to follow during the Palkhi.,1. Check whether the devotee can open the Palkhi Velapatrak (पालखी वेळापत्रक) module. 2. Check whether the devotee can able to click on श्री साईबाबा पालखी सोहळ्याचे वेळापत्रक & view upcoming Palkhi events date with respective location. 3. Check whether the devotee can able to click on श्री साईबाबा पालखी सोहळ्याचे नियम & view page details. 506 Devotees can be able to view Year wise Palkhi images.,1. Ensure that the devotee can open the Gallery(गॅलरी) module. 2. Check that the devotee can view all the year wise categorized Palkhi images in the Gallery(गॅलरी) module. 507All Aarti and bhajan available in the application.Devotees should be able to access and view the Aarti and Bhajan through the application.,1. Examine that the devotee can be able to open & read the content of Aarti/bhajan(आरती/ भजन) module. 508 Anyone can Donate their donation by filling in their details and using online payment methods.,1. Ensure that after click on Donation module redirect to saibabapalkhipune.org. 2. Check that devotee can be able to add details correctly into input fields. 3. Check that the by selecting online payment method completed the payments securely. 509 Users will see the Photos of all the social work available on this page.,1. Check that devotee can be able to open the Social Work(सामाजिक कार्य) module. 2. Check that devotee can be able to view all the social work images undertaken by the Palkhi Samiti. 510" If the Devotee needs any help, they can contact the committee through available options on this page.","1. Check that devotee can be able to open the Contact Us (संपर्क करा) module. 2. Ensure the provided address & contact details are correct. 3. Check that the after click on website it redirects to Palkhi page into browser. 4. Check that the after click on Facebook, YouTube, what's app & Instagram application it redirects to Palkhi page. "511Devotees can be able to check all details and images of शिर्डी पालखी भवन.,1. Check that devotee can be able to open the Shirdi Palkhi Bhavan (शिर्डी पालखी भवन). 2. Ensure the provided information is correct on Shirdi Palkhi Bhavan (शिर्डी पालखी भवन) module. 3. Check the provided images regarding Shirdi Palkhi Bhavan (शिर्डी पालखी भवन). 512"Application will have List of all the candidates name on admin side and allow the admin to view, edit the details of candidates.","1. Ensure that both Active and Inactive tabs are clickable and display the list of respective employee names. 2. Check the alignment of List Of Employees page. 3. To see outcome, click on Add Employee button fill required data and click Save the button. 4. Ensure that new employee cannot be added unless all the mandatory field data is provided. "513Admin have the authority to generate Appointment letter by filling in the details of payroll and generate ID will be created.,1. Ensure that appointment letter can be generated for an employee by clicking on the name of that employee by using the Generate Appointment Letter button. 2. Check the positioning of all the fields is proper or not. 3. Test the ability to generate the appointment letter without selecting payroll type. 4. To see the response click 'Cancel' button in the generate appointment letter pop up 514" Admin have the authority to Create Resume of Employees. Resume includes all the details Skills and Expertise, Experience, Employee History, Personal Info etc.","1. Make sure that user can create resume of an employee after clicking his name and then Create Resume button. 2. Check whether the positioning of the Create Resume button is proper. 3. Make sure the personal, educational and experience details from My profile getting fetched into resume. 4. Check whether the Preview button is clickable. 5. Ensure the pdf or resume downloaded has properly aligned and clearly visible data. "515"Admin have the authority to download personal, Educational, Experience, Insurance etc details in PDF format.",1. Make sure that admin can download excel file with list of active employees 2. Examine whether the excel file for the list of inactive employees can be downloaded. 3. Check that the Download button is properly positioned. 4. Make sure that 'Preview' button is clearly visible in both dark and light theme. 516 Admin have the authority to confirm and Save the details of the Employee so that all the details from user side so that user won’t be able to edit profile.,1. Make sure that the Edit Profile button is properly positioned 2. Check whether the 'Edit Profile' button is clickable or not. 3. Examine that clicking edit profile button for single employee will not impact for other verified employees. 4. Ensure that Confirm and Save button is visible to admin after clicking edit profile button. 517 Admin have the authority to make User profile editable. After making it editable admin can lock the profile by clicking on confirm and save button.,1. Make sure that the 'Confirm and Save' button is properly positioned 2. Check whether the 'Confirm and Save' button is clickable or not. 3. Examine that clicking confirm and save button for single employee will not impact for other verified employees. 4. Ensure that Confirm and Save button become invisible once after the profile is verified. 5. Ensure that on clicking edit profile button admin is able to edit employee profile details. 518"Admin have the authority to edit details of employee i.e., date of designation, joining and resignation.",1. Make sure that admin is able to edit the employee's details using edit functionality. 2. Check the functionality of 'Cancel' button. 3. Make sure that admin has the authority to 'On' and 'Off' the offboarding process. 4. Check the visibility of the toggle button for offboarding process in both themes. 519 Admin have the authority to export list of Active and inactive Employees in excel format.,1. Click the Excel Export button and check whether the proper excel file of active employees can be downloaded. 2. Check whether the proper excel file of inactive employees can be downloaded. 3. Check the positioning of Excel Export button. 4. Make sure that Excel Export button is visible in Light as well as Dark theme. 520" All the details of candidate i.e., personal details, educational and experience details will be entered by user and admin into the My Profile module. These details can be updated further.",1. Make sure that all the tabs on My Profile page are aligned well and clearly visible to the user. 2. Examine that calendar gets open after clicking on calendar icon and only a valid date can be selected for Date of birth. 3. Check that all the dropdown lists get opened and one of the options from the list can be selected. 4. Ensure that all the Name fields accept alphabets only. 5. To see outcome by entering alphabet or special characters into Mobile Number and Aadhar Number fields. 6. Examine that IFSC code and PAN number field accepts alphanumeric values only up to specific limits. 7. Check the alignment of Next button and check that button is clickable. 8. user's ability to upload new files or change the uploaded file using Upload functionality should be tested. 9. Check whether user is able to add the information in experience details field. 10. Examine Next button functionality by keeping one of the mandatory fields blank. 11. Make sure that Previous page button is clickable for all of the pages except Personal Details page. 12. Ensure that user can confirm and save the filled data after clicking on Confirm and Save button. 13. Examine user's ability to upload the profile picture by selecting a file from local system. 14. Examine user's ability to see the profile picture that is uploaded. 15. Check that the Download button is properly positioned. 16. Check that user is able to download the data in the pdf format. 17. Check the ability of the user to add and save educational details. 521 User can reset the password to login the application using this module. It will be supported on both sides admin as well as user side.,1. user's ability to change the password by entering valid password in New Password and Confirm Password needs to be tested. 2. Ensure that user will not be able to change the password keeping one of the password fields blank. 3. Examine user's ability to change password by entering only number or special characters into the fields. 4. Make sure that user can change password only after satisfying the criteria of the password. 5. Check the ability of module to support different screen sizes. 6. Check the buttons are properly aligned and spellings are correct. 522Allows the users to fill Form 11 used for Provident fund declaration. It will be available for admin as well as user.,"1. See the outcome by clicking on dropdown arrow and selecting one of the options. 2. Make sure that radio buttons can be turned On and Off. 3. Make sure that Father's Name field does not accept numeric data or special characters. 4. Check that Associate Name, Date Of Birth, Blood Group and Marital Status fields are auto filled and correct as per personal details. 5. Ensure that email ID is acceptable into Email ID field only after entering combination of alphanumeric data and special characters. 6. Examine that 'Universal Account Number', “Scheme Certificate number”, “PPO number”, “Aadhar card number” fields accept only numeric data. 7. Ensure that “Previous PF account number”, “PAN card number” and “IFSC Code” fields accept only alphanumeric characters. 8. Examine Download pdf functionality after submitting Form11. 9. Check the buttons are properly aligned and spellings are correct. 10. Check the ability to support different screen resolutions. "523 User can fill the Form XIV for contract labor declaration.,"1. Ensure that “Contractor’s name”, “Establishment name”, “Name of work”, “Workman’s name”, “Designation” and “Remarks” fields accept only alphabets. 2. Make sure that “Contractor’s Address', 'Establishment Address', 'Location of work”, “Employment tenure” fields accept all numbers, alphabets, and special characters”. 3. user's ability to enter only numbers into “Wage rate”, Workman’s Serial number” fields to be tested. 4. Check that 'Wage Period' field accepts alphanumeric data. 5. Check that the buttons are properly aligned and spellings are correct. 6. Make sure that the page support different screen resolution. "524 Users can fill EPF EX form for exemption from employee Provident fund scheme.,1. Ensure that Name of the user is auto filled in Member's Name field after opening Form EPF EX and after submitting this form user can download the form as well 2. Check whether the positioning of Submit and Reset button is proper. 3. Check the page for proper breadcrumbs. 4. Check whether the buttons are properly aligned and spellings are correct. 5. Examine the ability of the page to support different screen resolutions. 525 User can add nominee for their PF by filling Form2.,"1. Make sure that 'First Name' is auto populated and “Father / husband/mother’s full name”, “Name of the nominee”, “Nominee relationship with member”, “If nominee is minor, name of the guardian who may receive the amount during th... 2. Examine “Account number”, “Total amount/share of accumulation in PF to be paid to each nominee”, “Age” fields accept only numbers. 3. Ensure “Address Permanent/ Temporary”, “Address of the family member”, “Address of the nominee” fields accept alphanumeric data and special characters. 4. Make sure that date can be selected from the calendar, and it should be displayed in the date box in DD-MM-YYYY format. "526 While resigning the company user can fill this form.,"1. Make sure that 'Employee Name', 'Employee ID', 'Supervisor/Manager Name', 'Supervisor/Manager ID' fields are auto populated while the user opens Exit Form. 2. Ensure that calendar gets open after clicking the calendar icon and date can be selected. 3. Check that 'Employee Title/Position', 'Employee Department', 'Reason For Termination' fields accepts only alphabets. 4. Click on Exit Form 2 and check that all the radio buttons are working properly and getting turn On and Off after clicking on button. 5. Examine user can reset the details and submit updated details. 6. Check if user kept mandatory field empty and click on submit button. "527Admin can view the list of employees and their family members who are enrolled for Insurance policy provided by the company.,1. Check whether names of all the employees who have filled their insurance form appears in the table. 2. Ensure that the name of family member is getting added into the table 3. Examine the functionality of show entry tab. 4. Make sure that the data from the table can be filtered using 'Search' bar. 528 Admin will have authority to download excel file with the names of employee and their family member to add insurance coverage.,1. Observe the pagination on the pages 2. Check whether the excel file can be downloaded by clicking the 'Excel Export' button. 3. Ensure that Excel Export button is visible in both theme of screen. 4. Examine whether the excel file contain all the data properly. 529"Details regarding users Offer Letter, Access card, Vaccination details, Work location, Vehicle details, Salary Details and Lunch Facility Details can be viewed here.",1. Make sure that user can raise the request to avail lunch facility using 'Start' button 2. Ensure that the 'Start' button is visible in both light and dark theme. 3. Check the buttons are properly aligned and spellings are correct. 4. Check whether page supports different screen resolutions. 530" Details regarding Employees Vaccination details, Offer Letter Dates, Id Card, Access Card, Asset Dates, Work Location and Vehicle details will be displayed and can be edited here.",1. Examine user's ability to fill the data into respective fields to update the Employee Other Details. 2. Check whether the data getting added to only one employee at a time 3. Make sure that Id card Recovery Amount field become visible if the Id Card status is Lost. 4. Make sure that Access card Recovery Amount field become visible if the Access Card status is Lost. 5. Make sure that Visiting card Recovery Amount field become visible if the Visiting Card status is Lost. 6. Make sure that if Status of ID is changed from Lost to Submitted Recovery amount field should be removed. 531"Downloads list of Employees having details like vehicle, Offer letter, ID card etc details",1. Ensure that Excel Export button is visible in both theme of screen. 2. Check whether the 'Export Excel' button is properly positioned or not. 3. Examine whether the 'Excel Export' button is clickable or not. 4. Examine whether the excel file contain all the data properly. 532"Admin can update the status for lunch for Employees i.e., Lunch start date, Lunch End date after receiving the request from the candidates.",1. Check the ability of admin to approve the employee's lunch facility request. 2. Ensure that admin have the authority to stop the lunch facility of any employee as per requirement. 3. Check all the tabs are properly positioned on 'Lunch Detail' screen. 4. Ensure that the 'Lunch details' screen supports different screen resolutions. 533 Excel file with lunch details of the employees can be downloaded by the user.,1. Ensure that Excel Export button is visible in both theme of screen. 2. Examine whether the excel file contain all the data properly. 534Admin can add Bank details of Employees and display all the Bank details here. This will then reflect on employee side as well.,"1. Make sure that user is able to see account details that are already added, and the details could be edited. 2. Ensure that user can add account details to new employee. 3. Ensure that all the tabs are aligned properly on the page. 4. Check the spellings and breadcrumbs are proper. 5. Examine the functionality of show entry tab. 6. Make sure that the data from the table can be filtered using search bar. "535 Admin can download excel file for the salary account details of the employees.,1. Examine whether the excel file contain all the data properly. 2. Check whether the 'Export Excel' button is properly positioned or not. 536List of employees to be onboarded will be provided here. Admin can create a resume for shortlisted and pending candidates.,1. Ensure that user can create resume of particular employee from the list by clicking on the name of that employee. 2. Examine the ability of the user to go back to the List Of Employees page by clicking the 'Back to Home Page' 3. Check that Excel Export button is properly positioned. 4. Ensure that excel file with list of onboarding employees can be downloaded using Excel export. 5. Check that number of entries to be shown in table can be selected. 6. Check the search box functionality. 7. Use dropdown filter and check that data from the table can be filtered according to the onboarding phase of employees 537 Admin can send mail to the company Employees collectively from the list of employees using own credentials.,"1. To see the outcome, enter valid required data in respective fields and send mail to collective employees by clicking Send button. 2. Check the outcome by keeping one of the required fields blank and clicking Send button. 3. Make sure that without selecting employee names user will not be able to send mail. 4. Ensure that user cannot send the mail using Send button if the 'From Mail' field is blank. 5. To see the outcome, fill data in all the field except Password field and the Send button is clicked. 6. Check that user is not able to send the mail if Mail Subject or Mail Body field is kept blank and the Send button is clicked. 7. Make sure that mail can be sent only after user adds signature to that mail and then clicks on Send button. 8. Check the positioning of the buttons and table on 'Send Mail' screen. "538The feedback for NOC of the offboarding candidates will be provided by the Project Manager from this tab.,1. Ensure that user is able to search the name of employee from the list and fill the data only for Report Manager NOC field rest fields are in read only mode for report manager. 2. Examine the ability to edit the data only for Report Manager NOC field rest fields are in read only mode for report manager. 3. Check that the buttons are properly aligned and spellings are correct. 4. Check the response of the page for different screen resolutions. 5. Check whether the user has the access to edit other NOC's. 6. Check whether the NOC field to be respective authority is shown at the top. 539The feedback for NOC of the offboarding candidates will be provided by the HR from this tab.,1. Ensure that user is able to search the name of employee from the list and fill the data only for HR NOC field rest fields are in read only mode for HR user. 2. Check whether the user has the access to edit other NOC's. 3. Check that the buttons are properly aligned and spellings are correct. 4. Response of the page for different screen resolutions need to be checked. 5. Check whether the NOC field to be respective authority is shown at the top. 6. Check whether the status shown in the table for offboarding approval is proper. 540Admin user can view the list of offboarding candidates and edit the feedback given by the Project Manager and HR.,1. Make sure that admin user is able to search the name of employee from the list and fill the data either for Report Manager NOC field or for HR NOC field. 2. Examine ability to edit and save the data either for Report Manager NOC field or for HR NOC field. 3. Check whether the buttons are properly aligned and spellings are correct. 4. Examine the page supports different screen resolutions or not. 5. Check whether the user has the access to edit other NOC's. 6. Check whether the NOC field to be respective authority is shown at the top. 541 NOC for the offboarding candidates for Facilities provided will be given from this tab.,1. Check the alignment of the table of candidate names. 2. Ensure that search box is properly positioned. 3. Examine whether user can fill and save NOC for one of the candidates from the offboarding list. 4. Examine whether user can edit and save NOC for one of the candidates from the offboarding list. 5. Check whether the user has the access to edit other NOC's. 6. Check whether the NOC field to be respective authority is shown at the top. 542 NOC for the offboarding candidates for IT assets will be given from this tab.,1. Check the alignment of the Offboarding candidate list table is properly aligned. 2. Check whether the search box is properly positioned. 3. Check all the breadcrumbs are proper. 4. Ensure that the NOC for selected candidate can filled and saved by IT Asset admin. 5. Examine whether user can edit and save NOC for one of the candidates from the offboarding list. 6. Check whether the user has the access to edit other NOC's. 7. Check whether the status shown in the table for offboarding approval is proper. 543Employee user can fill and submit the offboarding form.,1. Check whether the status shown in the table for offboarding approval is proper. 2. Check all the breadcrumbs are proper. 3. Examine whether the Offboard Form tab appears on employee side when the Resignation date is set for that employee. 4. Check the positioning of the 'Offboarding Form' tab and the text boxes in the form as well. 5. Examine user's ability to fill the details in each field of Offboarding form and submit the form. 6. Check whether the user can navigate to next page keeping one of the fields in the form empty. 544" Admins have the authority to create Templates i.e., Appointment Letter, Appraisal Letter, Address proof letter etc.",1. Check the positioning of each button on 'Template' page. 2. Observe the response of the page for different screen resolutions 3. Make sure that admin can create new template using Create Template button. 4. Make sure that blank template cannot be saved by the admin. 5. Ensure that the previously created template can be edited after clicking the pencil icon. 6. To see the response click the delete icon in the action column. 7. Check whether clicking the eye icon allows the user to see the particular template. 545 Different types of letter can be created and saved by the admin. Admin will have authority to edit or delete the letter. Also the letter can be downloaded,"1. Examine whether generate letter button allows the admin to generate letter. 2. Ensure that all the features of the formatting toolbar are working properly. 3. Check whether correct data of employee is getting fetched when the name of employee and template is selected to generate letter. 4. Make sure that the letter can be edited after fetching the details. 5. Check that all the fields , data of letter generation module is on proper place and in proper alignment. "546 Allows Admin to download letter in PDF format. There is a toggle button which displays Letter head preview.,"1. Ensure that after clicking on the download button, the letter will be downloaded. 2. Check whether the page supports different screen resolutions. 3. Check that the buttons are properly aligned and spellings are correct. 4. Check whether the toggle button allows the admin to add or remove the letterhead to the letter. 5. Make sure that pdf file of letter can be downloaded after clicking the download button. "547"Admin have the authority to generate letter of the Employees that is needed by the HRs i.e., relieving letter, Experience Letter, Loan Application Letter etc. Admin can view generated letter.",1. Examine whether generate letter button allows the HR to generate letter. 2. Ensure that all the features of the formatting toolbar are working properly. 3. Check whether correct data of employee is getting fetched when the name of employee and template is selected to generate letter. 4. Examine whether the data in the letter can be edited after fetching the data. 5. Analyze that data appear on HR letter data table and fields appear on module is as per specification. 548 Allows Admin to download letter in PDF format. There is a toggle button which displays Letter head preview.,"1. Ensure that after clicking on the download button, the letter will be downloaded. 2. Check that the page supports different screen resolutions. 3. Check that the buttons are properly aligned and spellings are correct. 4. Make sure that toggle button allows the HR to add or remove the letterhead to the letter. 5. See the response after clicking the download button. "549"After logging in successfully, the employee will be taken to the page for the employee dashboard and will then be able to use the TMS program (web app).","1. Verify the results once the employee has typed the application URL into the browser. 2. Check whether the user is able to login with valid Username and Password. 3. Check whether user is able to access TMS Module. 4. Check the response when User ID field is filled and password field is left empty and the Login button is clicked. 5. To view the outcomes, click the Login button when the User Id field is left empty, and the Password field is filled in. 6. Check whether the user is able to login with invalid Username and invalid Password. "550" If a user forgets their current password, the admin or employee will be allowed to change it.","1. Verify whether the forget password link is available on login screen. 2. Make sure the user can enter a valid ID in the User Id field. 3. Check 'New Password' field accept alpha-numerical-special character. 4. Check whether the user enters the new password and retype/confirm the password. Both should match until the new password should not be set 5. Check that after clicking on Eye icon, entered password is visible to user. 6. Verify the Enter OTP field, which only accepts OTP provided via personal mail. 7. Verify whether success message shows or not once 'Change Password' button has clicked. 8. To verify user can changed the password using same OTP. 9. Check user can change password entering different OTP. 10. If multiple OTP has been send, check 'Enter OTP' field allow user to change the password using only last sent OTP. 11. Examine the response when a user ID is entered and the 'Back' button is clicked. 12. Check on click of the 'Next' button of verfication screen, when User id is entered. 13. Check user navigates to the verification screen, when 'Forget Password' link has been clicked. 14. Verify the response of the 'Verification' screen when user clicks on the 'Next' button without entering the user ID. "551 Temporary Id Card module enables admin to record an employee's attendance when their id card is missing.,"1. Verify temporary id card pop-up displays when user click on 'Temporary Id Card' button. 2. Check the calendar is displays once the user click on date field. 3. Verify user can select the employee name using 'Select Employee Name' dropdown. 4. Check the 'Temporary Id card' functionality to assign temporary ID cards to the employee. 5. Determine a click on Add to list button, selected employee data gets added into the list. 6. To reset the preselected employees information, check 'Reset' button functionality. 7. Check user can delete the added temporary id card entry. 8. Verify on clicking on Submit button, attendance entry displays on respective employee's dashboard. 9. Check that when the user clicks on cancel button temporary id card pop-up gets closed. 10. Examine the response, when any mandatory field remains unselected and 'Add to List' button is clicked. "552 To allow admin to mark attendance of the employees who worked on the holiday.,1. Examine the attendance cannot be filled on the last working day of a week if the next day is holiday. 2. Make sure the attendance of last working day in a week will be fill automatically to the upcoming working day. 3. Validate the current day attendance will fill on next day automatically. 553" Employees should have access to the current-week status of their timesheet records. The working hours, in-time and out-time for the current month should be displayed.","1. Examine column chart functionality display the timesheet status of employee, if the attendance is present on dashboard or timesheet has been filled 2. Check Column Chart dropdown displays once the user clicked on it. 3. Determine Column Chart dropdown functionality so employee can view monthly/yearly timesheet status. 4. Check functionality of custom option of Column Chart dropdown. "554"Admin should have access to view a list of sub-modules, including Incident Category, Incident Sub-Category, Assignment Group, and Assign To modules, within the Configuration module.",1. Ensure the functionality of displaying the list of existing sub-modules by clicking on the Configuration module 555 Admin/user will see their respective dashboards after logging in to the application.,1. Check all the tabs on 'Login' dashboard is properly aligned. 2. Enter valid User ID and password into their respective boxes then click on Login button and check for Login . 3. User enters incorrect User ID and password and then clicks on Login button. 4. Check for Login with valid User ID and invalid password then clicking on Login button. 5. Check that users enter invalid User ID and valid password then clicks on Login button. 6. Verify that click on Login button keeping all fields blank and try to Login. 556"The user can effortlessly drag and relocate an entire row containing the BR-ID, Req-ID, requirement, and requirement description within the data table of the 'Business requirement' module, allowing for repositioning anywhere within the table.",1. Ensure that a user can successfully drag and drop a business requirement from one location to another within the business requirement. 2. Make sure the 'BR_ID' displays sequentially after dragging and dropping the business requirement and clicking the update button. 3. Check that the sequential order is reflected in all related modules after the business requirement has been dragged and dropped. 557"The system should provide the admin with the ability to manage incident categories. The admin should be able to add, edit, and delete categories for incidents. Additionally, the admin should have access to a tabular view of the category list with search...","1. Check the behavior of the Submit button when the user attempts to submit a entry without entering any data in the required field. 2. Verifies the functionality of the system to submit an incident category by entering the required data in the corresponding field 3. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with a single click 4. Test the functionality of the Show Entries, Search, and pagination features in a data table. 5. Make sure the functionality of the system to allow the admin to modify an added incident category by clicking on the edit icon. 6. Ensure the functionality of the system to allow the admin to delete an added incident category by clicking on the delete icon. 7. Ensure the functioning of the Submit button by adding the duplicate entry of the category 8. Evaluate functionality to alert Users when trying to remove a Incident category that is still in use "558" The system should provide the admin with the ability to manage incident categories. The admin should be able to add, edit, view, and delete sub categories for incidents. Additionally, the admin should have access to a tabular view of the sub category li...","1. Check the behavior of the Submit button when the user attempts to submit a entry without entering any data in the required field. 2. Verifies the functionality of the system to submit an incident sub-category by selecting the category and entering the required data in the corresponding field 3. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with single click 4. Test the functionality of the Show Entries, Search, and pagination features in a data table. 5. Make sure the functionality of the system allows the admin to modify an added incident sub-category by clicking on the edit icon. 6. Ensure the functionality of the system allows the admin to delete an added incident sub-category by clicking on the delete icon. 7. Ensure the functioning of the Submit button by adding the duplicate entry of the sub-category 8. Evaluate functionality to alert Users when trying to remove a Incident sub-category that is still in use "559"The system should provide the admin with the ability to manage assignment groups. The admin should be able to add different assignment groups, view them in a tabular format with search and sort functionality, as well as have access to view, edit, or del...","1. Check the behavior of the Submit button when the user attempts to submit a entry without entering any data in the required field. 2. Verifies the functionality of the system to submit an assignment group by entering the required data in the corresponding field 3. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with single click 4. Test the functionality of the Show Entries, Search, and pagination features in a data table. 5. Make sure the functionality of the system allows the admin to modify an added assignment group by clicking on the edit icon. 6. Ensure the functionality of the system allows the admin to delete an added assignment group by clicking on the delete icon. 7. Ensure the functioning of the Submit button by adding the duplicate entry of the assignment group "560"The system should provide the admin with the ability to manage the assignment of people to groups. The admin should be able to view the assigned persons in a tabular format list with search and sort functionality, as well as have the ability to edit or ...","1. Check the behavior of the Submit button when the user attempts to submit a entry without entering any data in the required field. 2. Verifies the functionality of the system to add a member by selecting the assignment group and assigning them to a specific task or role 3. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with single click 4. Test the functionality of the Show Entries, Search, and pagination features in a data table. 5. Make sure the functionality of the system allows the admin to modify an added member to the assignment group by clicking on the edit icon. 6. Ensure the functionality of the system allows the admin to remove an added member by clicking on the delete icon. "561" The system should provide the admin with the ability to view a list of both active and inactive employee IT account details in the organization. Additionally, admin should be able to view and edit employee details.","1. Ensure that the navigation functionality works as intended and that the page loads correctly, displaying relevant content related to IT accounts. 2. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with single click 3. Verify that the functionality of the Show entries dropdown works accurately and displays the correct number of entries per page according to the user's selection. 4. Make sure that the search feature works correctly, filtering the entries based on the provided input. 5. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 6. Test the edit functionality works correctly, and ensure that the admin can edit the IT accounts details of the particular employee 7. Test the Functioning of the Cancel button, the admin can navigate to the back page with single click 8. Ensure that the view icon working as intended, admin can see the IT accounts details of the particular employee 9. Check the functionality of the Inactive tab, the list of inactive employee's IT account details appear and display 10. Verify that the functionality of the Show entries dropdown works accurately and displays the correct number of entries per page according to the user's selection. 11. Make sure that the search feature works correctly, filtering the entries based on the provided input. 12. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences 13. Test the edit functionality works correctly, and ensure that the admin can edit the IT accounts details of the particular employee 14. Ensure that the view icon working as intended, admin can see the IT accounts details of the particular employee 15. Test the functioning of Active-Inactive tabs, the related lists appearing on the screen and display the entries in the data table "562"In the information gathering stage of a web application penetration test, pertinent information about the target application is gathered. It includes inert methods like browsing old web pages, DNS enumeration, and open-source intelligence (OSINT). Activ...",1. Verify if any sensitive information related to the application is not publicly available by searching for the application name in search engines. 2. Verify the last cached/previous version of the targeted application in Internet Archive using Way back Machine 3. Verify the Server field in the server response header reveals information about the server version and type. 4. Check for other headers that may provide about the server version and type. 5. Check if the robots.txt file contains any disallowed paths or directories. 6. Verify the HTML source code of application for tags and their content. 7. Check if the sitemap.xml file for potential information leakage. 8. Verify if there are any comments in the HTML source code of the webpage for information leakage. 9. Verify the redirect bodies within the webpages for information leakage. 10. Look for any front-end debug files that may reveal sensitive information. 11. Verify the technologies/frameworks used in application by using Wappalyzer. 12. Checking for the framework/components & their versions used in application from Error messages. 563 Web application penetration testing's Configuration and Deployment Management Testing phase focuses on analyzing the web application's configuration and deployment procedures to guarantee their security and dependability. Testing configuration...,1. Verify the application enforces secure communication protocols (HTTPS) by checking the usage of SSL/TLS certificates. 2. Verify that HTTP and HTTPS is properly configured within the application. 3. Verify the identification of unnecessary services or ports that may be accessible by conducting a port scan. 564 The Authentication Testing phase in web application penetration testing focuses on assessing the security and reliability of the authentication mechanisms implemented in the web application. This phase involves activities such as testing the strength of...,"1. Verify the sensitive information (Username, Password) is transmitted through the security channel of the used HTTPS. 2. Verify the account lockout mechanism by using the incorrect password for number of times on the login page. 3. Verify the unlock mechanisms in the application. 4. Verify by Force browsing by directly requesting a different page where unauthorized users attempt to access restricted resources directly by manipulating URLs. 5. Verify the Parameter modification functionality by modifying the parameters to gain access to the protected areas without providing valid credentials. 6. Verify whether the application stores sensitive information on the client-side, such as in browser cookies or local storage. 7. Check the browser history issue or back refresh attack by clicking the Back button after logging out. "565"Evaluation of the web application's authorisation systems is the main goal of this phase. On the basis of their responsibilities and privileges, it involves evaluating whether users are given the proper access permissions. The aim is to locate any ...",1. Verify the presence of injection points by browsing the TMS module and testing URLs to path traversal vulnerabilities. 2. Verifying injection points related to role/privilege manipulation. For check the vertical access is possible by force browsing. 3. Verifying injection points related to role/privilege manipulation. For check the Horizontal access is possible by force browsing. 4. Validating for the points where object references may occur (Unique Identifier) and attempting to access control measures and if they're vulnerable to IDOR. 566" Administration and security of user sessions within the web application are being evaluated throughout this testing. After logout or a predetermined amount of inactivity, it aims to ensure that session tokens are safely produced, saved, and invalidated....","1. Validating the Session Tokens for the Same User. 2. Validating the Session Tokens for the Different User. 3. Check that the proper security configuration is set for cookies (HTTP Only and Secure flag, Samesite=Strict) 4. Check whether the application renews the cookie after successful user authentication. 5. Verify the session timeout functionality and ensure that session tokens are unusable after the timeout period. 6. Verify whether the JWTs expose sensitive information. 7. Verify whether the JWTs can be tampered with or modified. "567" Input validation techniques of the web application are tested during this phase. Input-based attacks like SQL injection, cross-site scripting (XSS), command injection, and other input-based attacks are among the user input-related vulnerabilities it see...","1. Identifying any variables within the application that are directly reflected in the responses returned to the client. 2. Identifying any input variables stored by the application and reflected on the client-side. 3. Checking for SQL injection points, the severity of the injection, and the level of access that can be achieved through it. 4. Verify all the LDAP injection points in web application. 5. Verifying and assessing the command injection points with special characters. 6. Verify the XML injection points in the application. 7. Verify template injection vulnerability points by checking for the templating engine and exploiting. 8. Check for Server-Side Request Forgery vulnerability. "568" During this testing, the web application will be examined to see how it responds to several problem scenarios, including invalid input, server issues, and exceptions. The intention is to spot any data leaks, sensitive information-containing error messag...",1. Validating existing error output (i.e.: Random files/folders (400 series) and analyze the different output returned. 2. Check if the application reveals detailed error messages containing sensitive data or system information. 3. Verify the prevention of server and application stack trace leakage by manipulating inputs to trigger exceptions. 569"Business Logic testing stage focuses on evaluating the business logic of the web application to make sure it functions properly and securely. It entails assessing the application's business rules, data validation, processes, and access control syst...",1. Validate that all checks are occurring on the back end and can't be bypassed & test to break the format of the expected data and the application behavior. 2. Check for user-level access to modify or read. That data in application which have not access to user for read or modify. 3. Verify that the unwelcomed file types are rejected and handled safely and check for Content-type or file extension. 4. Test to upload the malicious files to the application and determine whether it is accepted and processed. 570"APIs (Application Programming Interfaces) of the web application are tested during this phase to ensure its security and dependability. It entails assessing the APIs' authentication and authorisation procedures as well as input verification, error ...","1. Check for API via Passive Recon with Google Hacking and Shodan. 2. Check for API via Active Recon Baseline Scanning with Nmap 3. Check against the password Brute-Force and Password Spraying attacks using a common password wordlist, or custom list. 4. Check complex access control policies with different hierarchies, groups, and roles. "571" Admin should be able to view gross CTC graph of employees, using filter monthly and yearly.","1. Examine the dropdown feature are present, which contains 'By Employee', 'By Year', and 'By Month' options. 2. Make sure the Gross CTC is displayed by employee, year, and month of employees by using the search feature. 3. Ensure that the search functionality allows the admin to look up the Gross CTC for many employees. 4. Evaluate the Goss CTC of employee will appear 'by Year' and 'by Month'. 5. Confirm the back button will redirect admin to the Appraisal dashboard screen. 6. Ensure the alignment is proper for the 'Graphical representation' page as well as for the dropdown present on it. "572"The candidate's details will be reflected in the card form. The candidate's image, name, designation, recruiter name, interviewer name, in-time, out-of-time, and feedback form will all be included in the data.","1. To enroll in job openings, applicants need to scan the QR code first. 2. When the candidate enters the candidate's Aadhar number, the system determines whether the candidate is a new or revisit applicant. 3. If the candidate returns, his or her data will be automatically reflected in the form; he or she can change the information and submit the form. 4. If the candidate is visiting for the first time, he or she must fill out the form completely before submitting it. 5. In the Job Seekers tab, the user can view the candidates for today. 6. The user can find a certain applicant or any recruiter's candidate by using the Search bar. 7. If the user wants to look at the prior candidate's list, the calendar will display the specific date list. 8. The candidate's details can be modified by selecting the edit symbol for that candidate. 9. The view icon is available on each candidate card and can be used to view a specific contender's details. 10. The Add Candidate button allows users to directly add any candidate to the Job Seekers tab. 11. Examine the response when the add button is clicked without entering any values into the form. 12. The user can remove any values they have entered on the form by clicking the reset button on it. 13. Ensure that if the user wants to filter the candidate information between Today, Yesterday, the current week, the current month, and all. 14. Examine the excel icon functionality by clicking on it for selected date candidate excel is downloaded or not. "573" Version of the policy is tracked in this module by the Super Admin and the admin. Details of the change, Modified by, reviewed by, Status of the policy and the date for the version.",1. Ensure that the Policy Version tab is not visible while creating new policy. 2. Check the proper alignment of Policy Version page. 3. Examine whether the new row gets added to the Policy Version table every time after updating the policy. 4. Examine whether admin can see the Policy Version table for all the policies that were previously added. 5. Make sure that the super admin can see the Policy Version table for all the policies that were previously added. 6. Check the functionality of pencil icon(Edit) and edit the revision history for the policy. 7. Check the ability to reset the data in policy version table data after clicking on reset button. 8. Ensure the proper alignment of Revision History window. 9. Examine the ability to update revision history by keeping the fields in window blank. 574 The interviewer will have access to a feedback form and will grade the candidate based on their performance during the interview.,"1. Ensure that the response is positive when the user enters valid credentials and clicks on the login button. 2. Check that the count entries in the tabular format are reflected in the show entries dropdown. 3. Using the Search bar check whether the entries are reflected on the screen analogous to the values entered in the search bar. 4. Ensure that the Pagination button navigates the user to the Next or Previous page. 5. Check the number of entries displayed on the screen is reflected in the bottom left corner out of the total entries. 6. Make sure that user can add feedback values in the feedback form of the particular candidate and using the submit button the form is submitted. 7. Ensure that when the user clicks on the Cancel button, the user navigates to the dashboard, and the entered values are not saved. 8. Ensure that, for the revisit candidate, the user is able to view the feedback value submitted by the previous interviewer. 9. The user will be able to add new feedback values in reference to prior feedback values. 10. Using the search bar, the user can easily find any details of the candidate feedback in tabular format. 11. Using the show entries dropdown, the user can verify any entries that haven't been displayed on the screen at that time. 12. Check the count of which entries are displayed on the screen in tabular format and also the out-of-total count in the bottom left corner. 13. Check the PAGINATION button at the bottom right of the history table to display the previous and next page information of the candidate feedback history in the table. 14. The feedback icon allows the user to view the interview feedback provided by the interviewer. "575"By performing these information gathering tasks, security testers gain valuable insights into the target web application and its infrastructure, enabling them to plan and execute subsequent testing activities effectively to identify and mitigate potenti...",1. Determine the application components frontend code using different browsers and tools. 2. Examine the entry points/attack vectors within the application by directory brute forcing and intercepting requests. 576"Configuration and Deployment Management Testing ensures that the network infrastructure, application platform, and associated configurations are appropriately set up, hardened against potential vulnerabilities, and comply with security best practices. B...",1. Testing Amazon S3 Bucket Misconfiguration to examine the access control configuration for the storage resources. 577"Security tester ensures that user identities, roles, and access controls are properly managed. It aims to prevent unauthorized access, protect user identities, and maintain the integrity of the authentication and authorization mechanisms.",1. Examine the user roles by analyzing the application. 578 Authentication Testing focuses on evaluating the security and effectiveness of the authentication mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could potentially lead to unauthorized access or compr...,1. Review of the application allows access without authorization by storing sensitive information on the client side. 2. Review and assess new user accounts and if they are created with any defaults or identifiable patterns. 3. Enumerate the applications for default credentials and validate if they still exist. 579 Authorization Testing focuses on evaluating the effectiveness and security of the authorization mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could lead to unauthorized access or privilege escalatio...,1. Identify relatable injection points to fuzz or otherwise attempt to bypass security measures. 2. Identify attack surfaces to check the access control measures if vulnerable to IDOR or not. 3. Identify attack surfaces that pertain to path traversal to identify the extent of path traversal using bypassing techniques. 4. Ensure that authentication is applied across all requests that require it to avoid unintentional open/public resources. 580"Session Management Testing focuses on evaluating the security and effectiveness of session management mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could lead to unauthorized access, session hijacki...",1. Analyze the response by forcing cookies to authenticate the user to check cookie is refreshed or not. 581"Input Validation Testing focuses on ensuring that user input is properly validated and sanitized, mitigating the risk of various types of attacks and protecting the application and its users' data. It aims to identify vulnerabilities and weaknesses that...",1. Testing for stored xss script injected and reflected on client-side successfully 2. Test for Host header to check by supplying another domain (i.e. attacker.com) into the Host header field. 3. Test for X-Forwarded Host Header Bypass to successfully supply the value to the X-Forwarded-Host header. 582Security tester focuses on Error Handling to evaluating the application's response to various error conditions and ensuring that sensitive information or system details are not disclosed to potential attackers. It aims to identify vulnerabilities and we...,1. Determine error responses of the web server or application are not disclosing sensitive information 583" Weak Cryptography validation focuses on evaluating the cryptographic mechanisms employed by a web application. It aims to identify vulnerabilities and weaknesses in encryption, transport layer security, handling of sensitive information, and maintains c...","1. Ensure that the TLS security is not bypassable and is properly implemented across the application by reviewing server configuration 2. Checking for session tokens send over secure channel, by forcing HTTP request. "584"Business Logic Testing focuses on evaluating the correct implementation and security of the application's business logic. It aims to identify vulnerabilities and weaknesses in the application's logic flow, data validation, process timing, and other busi...",1. Check if the website verifies the file extension of the file before uploading it to resource the folder. 2. Check if other uploaded files can be accessed directly by specified URL. 3. Check if the uploaded file can include code or script injection. 585"Client-side Testing focuses on evaluating the security of the client-side components of a web application, including JavaScript, HTML, CSS, and browser-related features. It aims to identify vulnerabilities and weaknesses that could be exploited by attac...",1. Testing for DOM-Based Cross-Site Scripting Vulnerability 2. Testing for HTML Injection vulnerability 3. Testing Cross-Origin Resource Sharing Vulnerability 4. Testing for Clickjacking vulnerability 586" API Testing involves evaluating the security and functionality of Application Programming Interfaces (APIs) used in web applications or software systems. It focuses on identifying vulnerabilities, misconfigurations, and flaws in API implementations.","1. Checking rate limit by performing a brute force attack on the same user account to exploit weak or predictable tokens. 2. Examine the limit/throttle time for a single API client/user can execute a single operation (e.g. validate an OTP, or request password recovery without visiting the one-time URL). "587"Application will have Designing Standards screen accessible by admin only, that displays list of standard tables segregated by design type","1. Examine functionality for 'Designing Standards' tab 2. Validate Designing standards screen 3. Check to see that all Text link, headers, and icons from Designing standards screen are appropriately positioned. 4. Check to see if Occupancy screen is compatible with different screen resolutions. "588"The admin will be able to update the standards for certain fields for the new design criteria of Occupancy, through this module.","1. Examine the functioning of 'New Design Criteria' text button from Occupancy card 2. check 'New Design Criteria' screen (Occupancy) 3. Test the functionality of edit (icon) button from 'Action' column from 'New Design Criteria' table (Occupancy) 4. Verify functioning of 'Back' button from 'New Design Criteria' screen (Occupancy) 5. Check that all columns, headers, breadcrumbs and icons from New Design Criteria-(Occupancy) screen are appropriately positioned. 6. Check to see if the New Design Criteria-(Occupancy) screen is compatible with different screen resolutions. "589" The admin will be able to update the standard for certain fields for the existing design criteria of Occupancy, through this module.","1. Test the functionality for 'Existing Design Criteria' text button from Occupancy card 2. Evaluate 'Existing Design Criteria' screen (Occupancy) 3. Examine the functionality for edit (icon) button from 'Action' column from 'Existing Design Criteria' table (Occupancy) 4. Test the functioning of 'Back' button from 'Existing Design Criteria' screen 5. Ensure that all columns, headers, breadcrumbs and icons from Existing Design Criteria-(Occupancy) screen are appropriately positioned. 6. Check to see if the Existing Design Criteria-(Occupancy) screen is compatible with different screen resolutions. "590" The admin will be able to update the standard for certain fields for the occupancy details of Occupancy, through this module.","1. test the functionality for 'Occupancy Details (Annexure4)' text button from Occupancy card 2. Evaluate 'Occupancy Details (Annexure4)' screen 3. Test the functionality for edit (icon) button from 'Action' column 4. Examine functionality for 'Add' button from 'Occupancy Details (Annexure4)' screen 5. Ensure the functioning of 'Back' button from 'Occupancy Details (Annexure4)' screen 6. Ensure that columns, headers, breadcrumbs and icons from 'Occupancy Details (Annexure4)' screen are appropriately positioned 7. Check to see if the 'Occupancy Details (Annexure4)' screen is compatible with different screen resolutions. "591" The admin will be able to update the standards for certain fields for Miscellaneous Storage, through this module.","1. Check the functioning of 'New Design Criteria' text button from Miscellaneous card 2. Evaluate 'New Design Criteria' screen (Miscellaneous) 3. Examine functionality for edit (icon) button from 'Action' column from 'New Design Criteria' table. 4. Test the functioning 'Back' button from 'New Design Criteria' screen (Miscellaneous) 5. Ensure that all columns, headers, breadcrumbs, navigation tabs and icons from 'New Design Criteria' (Miscellaneous) screen are appropriately positioned or not. 6. Check to see if the 'New Design Criteria' (Miscellaneous) screen is compatible with different screen resolutions. "592"The admin will be able to update the standards for certain fields of rack storage CMDA system for the new system criteria of Single, double row rack where storage height is greater than 12 ft to less than equal to 25 ft., through this module.","1. Check the functionality for 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' text button under tag New System Criteria' from 'Rack Storage-CMDA system' card 2. Examine 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen (Storage height 'including 15ft') 3. Evaluate 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen (Storage height '16 to 18ft') 4. Validate 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen (Storage height '19 to 20ft') 5. Check 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen (Storage height '21 to 22ft') 6. Test 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen (Storage height '23 to 25ft') 7. Check the functioning of edit (icon) button from 'Action' column from 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' table 8. Test 'Back' button functionality from 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen 9. Check to see if all columns, headers, breadcrumbs, navigation tabs, and icons from 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' (Rack Storage-CMDA) screen are appropriately positioned or not. 10. Ensure that 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen is compatible with different screen resolutions. "593"Through this module, the admin will be able to update the standard for certain fields of rack storage CMDA system for the multi row rack where rack dept is less than equal to 16 ft.","1. Check functioning for 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' text button under tag 'New System Criteria' from 'Rack Storage-CMDA system' card 2. Examine functionality for 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (including 15 ft) 3. Test 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (storage height 16ft to 18ft) screen 4. Check functionality for 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (storage height 19ft to 20ft) screen 5. Validate functionality for 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (storage height 21ft to 22ft) screen 6. Examine the functionality of 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (storage height 23ft to 25ft) screen 7. Check functionality for edit (icon) button from 'Action' column from 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' table 8. Examine 'Back' button functionality from 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' screen (Rack Storage-CMDA) 9. Ensure that, all columns, headers, breadcrumbs, navigation tabs, and icons from 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (Rack Storage-CMDA) screen are appropriately positioned 10. Check to see if the 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' screen is compatible with different screen resolutions. "594" The admin will be able to update the standard for certain fields of rack storage CMDA system for the multi row rack where rack dept is greater than 16 ft., through this module.","1. Verify functionality for 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' text button under tag 'New System Criteria' from 'Rack Storage-CMDA system' card 2. Examine functionality for 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' (Including 15ft) screen 3. Check the functioning for 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' (16 to 25ft) screen 4. Verify functionality for edit (icon) button from 'Action' column from 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' table 5. Check 'Back' button functionality from 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' screen (Rack Storage-CMDA) 6. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' (Rack Storage-CMDA) screen are appropriately positioned 7. Check to see if the 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' screen is compatible with different screen resolutions. "595" The admin will be able to update the standard for certain fields of rack plastic CMDA system for the new system criteria where packaging type is exposed, through this module.","1. Check functionality for 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' text button under tag 'New System Criteria' from 'Rack Storage-CMDA system' card. 2. Examine functionality for 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' screen (Rack Plastic-CMDA) 3. Test the functioning of edit (icon) button from 'Action' column from 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' (Rack Plastic-CMDA) table 4. Check 'Back' button functionality from 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' screen (Rack Plastic-CMDA) 5. Ensure that all columns, headers, breadcrumbs, and icons from 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' (Rack Plastic-CMDA) screen are appropriately positioned 6. Check to see if the 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' (Rack Plastic-CMDA) screen is compatible with different screen resolutions. "596"The admin will be able to update the standard for certain fields of rack plastic CMDA system for the new system criteria where packaging is exposed, through this module.","1. Check functionality for 'Rack Plastic - CMDA Group A Plastic Exposed' text button under tag 'New System Criteria' from 'Rack Storage-CMDA system' card 2. Examine 'Rack Plastic - CMDA Group A Plastic Exposed' screen (Rack Plastic-CMDA) 3. Test the functionality for edit (icon) button from 'Action' column from 'Rack Plastic - CMDA Group A Plastic Exposed' (Rack Plastic-CMDA) table 4. Check 'Back' button functionality from 'Rack Plastic - CMDA Group A Plastic Exposed' screen (Rack Plastic-CMDA) 5. Ensure that all columns, headers, breadcrumbs, and icons from 'Rack Plastic - CMDA Group A Plastic Exposed' (Rack Plastic-CMDA) screen are appropriately positioned 6. Check to see if the 'Rack Plastic - CMDA Group A Plastic Exposed' (Rack Plastic-CMDA) screen is compatible with different screen resolutions. "597" The admin will be able to update the standard for certain fields of rack storage CMDA system for the density adjustment factor of existing system criteria, through this module.","1. Verify functionality for 'CMDA Density adjustment Based on Storage height for Existing System Criteria' text button under tag 'CMDA- Adjustment Factor' from 'Rack Storage- CMDA System' card 2. Examine 'CMDA Density adjustment Based on Storage height for Existing System Criteria' screen (Rack Storage- Existing-CMDA) 3. Test the functioning of edit (icon) button from 'Action' column from 'CMDA Density adjustment Based on Storage height for Existing System Criteria' (Rack Storage- Existing-CMDA) table 4. Test 'Back' button functionality from 'CMDA Density adjustment Based on Storage height for Existing System Criteria' screen (Rack Storage- Existing-CMDA) 5. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'CMDA Density adjustment Based on Storage height for Existing System Criteria' (Rack Storage- Existing-CMDA) screen are appropriately positioned 6. Check to see if the 'CMDA Density adjustment Based on Storage height for Existing System Criteria' screen is compatible with different screen resolutions. "598"The admin will be able to update the standard for certain fields for rack storage CMDA system for the existing system criteria of single, double row rack, where storage height is greater than 12 ft and less than equal to 25 ft., through this module.","1. Check functionality for 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' text button under tag 'Existing System Criteria - Multi-Row Rack Storage' from 'Rack Storage-CMDA system' card 2. Test the working of edit (icon) button from 'Action' column from 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' (13ft to 20ft) table 3. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen are appropriately positioned or not. 4. Check to see if the 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen is compatible with different screen resolutions. 5. Check 'Back' button functionality from 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen (Rack Storage-CMDA) 6. Examine 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen (Rack Storage-CMDA) 7. Examine 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen (21ft to 22ft) 8. Check 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen (23ft to 25ft) "599"The admin will be able to update the standard for certain fields for rack storage CMDA system of multi row rack where rack dept is less than equal to 16ft., through this module.","1. Test the functionality of 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' text button under tag 'Existing System Criteria - Multi-Row Rack Storage' from 'Rack Storage-CMDA system' card 2. Examine 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen (Up to 15ft) 3. Check 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen (16ft to 20ft) 4. Validate 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen (21ft to 25ft) 5. Test the working of edit (icon) button from 'Action' column from 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' (Up to 15ft) table 6. Examine 'Back' button functionality from 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen (Rack Storage-CMDA) 7. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen are appropriately positioned 8. Check to see if the 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen is compatible with different screen resolutions. "600" The admin will be able to update the standard for certain fields for rack storage CMDA system of multi row rack where rack dept is greater than 16 ft., through this module.","1. Check the working of 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' text button under tag 'Existing System Criteria - Multi-Row Rack Storage' from 'Rack Storage-CMDA system' card 2. Validate 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen (Up to 15ft) 3. Check 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen (16ft to 20ft) 4. Examine 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen (21ft to 25ft) 5. Check the working of edit (icon) button from 'Action' column from 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' (Up to 15ft) table 6. Check 'Back' button functionality from 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen (Rack Storage-CMDA) 7. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen are appropriately positioned. 8. Check to see if the 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen is compatible with different screen resolutions. "601The admin will be able to update the standard for certain fields for rack storage CMSA system through this module.,"1. Check the working of 'CMSA Rack Storage' text button under tag 'CMSA System' from 'Rack Storage-CMSA system' card 2. Examine 'CMSA Rack Storage' screen (Class I) 3. Check 'CMSA Rack Storage' screen (Class II) 4. Validate 'CMSA Rack Storage' screen (Class III) 5. Evaluate 'CMSA Rack Storage' screen (Class IV) 6. Examine the functionality for edit (icon) button from 'Action' column from 'CMSA Rack Storage' table 7. Test 'Back' button functionality from 'CMSA Rack Storage' screen (Rack Storage-CMSA) 8. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'CMSA Rack Storage' screen are appropriately positioned or not. 9. Check to see if the 'CMSA Rack Storage' screen is compatible with different screen resolutions. "602