requirement_desc
stringlengths
35
257
test_cases
stringlengths
39
16.2k
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.
The 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
The 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.
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.
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.
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.
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.
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.
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.
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.
The 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.
Contact 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.
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.
The 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
The 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.
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
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
The 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.
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.
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.
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...
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.
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.
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.
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.
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.
The 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.
Users 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.
The 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.
Access 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.
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.
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.
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.
Users 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.
The 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.
Access 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'.
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.
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.
The 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.
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.
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.
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.
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).
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.
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.
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.
The 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.
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.
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)
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.
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.
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.
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.
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)
The 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.
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.
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.
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.
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.
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.
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.
The 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.
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.
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.
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.
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.
Create 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.
The 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.
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.
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.
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.
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.
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.
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.
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'
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.
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.
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.
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.
Clinic 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
The 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.
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.
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.
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.