requirement_desc
stringlengths 35
257
| test_cases
stringlengths 39
16.2k
|
|---|---|
Admin can edit the existing service by adding or removing the description. | 1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of services. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the service details and exit the edit mode. |
Admin can remove service by selecting this action. | 1. To validate the functionality of the Delete button for services, allowing the deletion of existing services from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. |
Admin can add the new domain by selecting this button. | 1. To ensure that the admin has access to various domains and can make changes to existing domain or add new domain within the system or availability of functionalities to do the same 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown 3. Check whether the displayed data is filtered based on the entered text, showing only the relevant information. 4. To verify the functionality of the Add Domain button, ensuring that it displays a popup with the necessary fields to add a new Domain 5. Onclick the 'Add Domain' button should trigger the display of a pop-up window which contain a form with fields for specifying the name, description, and other required details of the domain to be added. 6. Ensure on clicking the Upload Icon button allows the user to select an icon file from their local system. 7. To verify the functionality of the 'Add' button in the Add Domain for when all required details are entered without uploading icon. 8. To verify the functionality of the 'Add' button in the Add Domain form, ensuring that it successfully adds the domain to the system when all required details are entered. 9. To ensure the functionality of the Cancel button in the Add Domain pop-up, ensuring that it cancels the process of adding a new domain and closes the pop-up without saving any changes. 10. Examine the Domain name listed in the Domain Name column are clickable. 11. Verify the Next pagination button. 12. Verify the Previous pagination button. |
Admin can able to see the different domains with detailed information. | 1. Verify that clicking on the View button displays the detailed information or overview of the domain. 2. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. |
Admin can edit the existing domain by updating the description of the domain. | 1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of domains. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the domain details and exit the edit mode. |
Admin can delete a domain by selecting this action. | 1. To validate the functionality of the Delete button for domains, allowing the deletion of existing domain from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. |
Only the admin can add the new project by adding all the required information. | 1. To ensure that the admin has access to various projects and can make changes to existing services or add new project within the system or availability of functionalities to do the same 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown 3. To verify the search functionality that filters displayed data based on the entered text, presenting only relevant information 4. To verify the functionality of the Add Project button, ensuring that it displays a popup with the necessary fields to add a new project. 5. To evaluate the functionality of the Add button in the Add Projects feature when all the required fields are specified or entered. 6. To analyze the behavior of the Add button in the Add Projects feature when the user intentionally leaves certain required fields blank or omits entering any data 7. Verify the Cancel button functionality of the Add Projects. |
Admin can see the different projects with detailed information. | 1. Verify that clicking on the View button displays the detailed information or overview of the project. 2. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. |
Admin can edit the existing project by updating the information of the project. | 1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of project. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the project details and exit the edit mode. |
Admin can delete a project by selecting this action if the organization is no longer working on the project. | 1. To validate the functionality of the Delete button for projects, allowing the deletion of existing project from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. |
User can view the projects based on the categories from the modules they are in. | 1. To ensure that the projects listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each project 2. Verify the Next pagination button. 3. Verify the Previous pagination button. |
Only the admin can add the new tool by adding all the required information. | 1. To ensure that the admin has access to various tools and can make changes to existing tool or add new tool within the system or availability of functionalities to do the same. 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown 3. To verify the search functionality that filters displayed data based on the entered text, presenting only relevant information 4. To verify the functionality of the Add Tool button, ensuring that it displays a popup with the necessary fields to add a new tool 5. Verify the Add Tools pop-up window. 6. Ensure on clicking the Upload Icon button allows the user to select an icon file from their local system. 7. To verify the functionality of the 'Add' button in the Add Tool for when all required details are entered without uploading icon 8. To evaluate the functionality of the 'Add' button in the Add Tool form, ensuring successful addition of the tool to the system when all the required details are entered 9. To ensure the functionality of the Cancel button in the Add Tool pop-up, ensuring that it cancels the process of adding a new tool and closes the pop-up without saving any changes 10. To confirm whether the Tools name listed in the Tools Name column are clickable. 11. Verify the Next pagination button. 12. Verify the Previous pagination button. |
Admin can see the different tools with detailed information. | 1. Verify that clicking on the View button displays the detailed information or overview of the tool. 2. Make sure the functionality of the Back button in the View action, closes the view mode and returns the user to the previous page or section. |
Admin can edit the existing tool by updating the information such as the version or description of the tool. | 1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of tools. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the tool details and exit the edit mode. |
Admin can delete a tool by selecting this action. | 1. To validate the functionality of the Delete button for tools, allowing the deletion of existing tool from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. |
Only the admin can add the new technology by adding the required information. | 1. To ensure that the admin has access to various technologies and can make changes to existing technology or add new technology within the system or availability of functionalities to do the same. 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown. 3. Check whether the displayed data is filtered based on the entered text, showing only the relevant information. 4. To verify the functionality of the Add Technology button, ensuring that it displays a popup with the necessary fields to add a new technology. 5. Onclick the 'Add Technology' button should trigger the display of a pop-up window which contain a form with fields for specifying the name, description, and other required details of the technology to be added 6. Ensure on clicking the Upload Icon button allows the user to select an icon file from their local system. 7. To verify the functionality of the 'Add' button in the Add Technology for when all required details are entered without uploading icon. 8. To verify the functionality of the 'Add' button in the Add Technology form, ensuring that it successfully adds the technology to the system when all required details are entered. 9. To ensure the functionality of the Cancel button in the Add Technology pop-up, ensuring that it cancels the process of adding a new technology and closes the pop-up without saving any changes. 10. Confirm whether the Technology name listed in the Technology Name column are clickable. 11. Verify the Next pagination button. 12. Verify the Previous pagination button. |
Admin can see the different technologies with detailed information. | 1. Verify that clicking on the View button displays the detailed information or overview of the technology. 2. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. |
Admin can view the list of clients. | 1. To ensure that the admin has access to various clients and can make changes to existing technology or add new client within the system or availability of functionalities to do the same. 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown. 3. Check whether the displayed data is filtered based on the entered text, showing only the relevant information. 4. Confirm whether the Client name listed in the Client Name column are clickable. 5. Verify the Next pagination button. 6. Verify the Previous pagination button. 7. Verify that clicking on the View button displays the detailed information or overview of the client. 8. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. 9. To verify the functionality of the Add Client button, ensuring that it displays a popup with the necessary fields to add a new client. 10. Onclick the 'Add Client' button should trigger the display of a pop-up window which contain a form with fields for specifying the pseudo name, description, and dropdown for client name to be selected 11. To verify the functionality of the 'Add' button in the Add Client for when any of data for mandatory field is missing. 12. To verify the functionality of the 'Add' button in the Add Client form, ensuring that it successfully adds the client to the system when all required details are entered. 13. To ensure the functionality of the Cancel button in the Add Client pop-up, ensuring that it cancels the process of adding a new client and closes the pop-up without saving any changes. |
Admin can edit the client’s description and save it. | 1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of client. 2. Examine the ability to modify client details such as pseudo name and description 3. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the client details and exit the edit mode. 4. Examine the Update button functionality of the Edit action which on click saves the edited details for client. |
Only the admin can add the new SPOC name with details. | 1. To ensure that the admin has access to various SPOC and can make changes to existing SPOC or add new SPOC within the system or availability of functionalities to do the same 2. Selecting a specific number from the dropdown should update the page or view to display the corresponding number of entries using 'Show' dropdown 3. To verify the search functionality that filters displayed data based on the entered text, presenting only relevant information 4. To verify the functionality of the Add SPOC button, ensuring that it displays a popup with the necessary fields to add a new SPOC. 5. To validate the functionality of the Name dropdown field in the Add SPOC form, which allows users to select a name to be added as a (SPOC) in our system 6. To validate the functionality of the Designation dropdown field in the Add SPOC form, which allows users to select a designation for (SPOC) in our system 7. To check the behavior of the Add button in the Add SPOC pop up when incomplete data is entered, to ensure that it functions as expected 8. Confirm the behavior of the Add button in the Add SPOC pop up when all the required data is provided, to ensure that it functions correctly 9. To ensure the functionality of the Cancel button in the Add SPOC pop-up, ensuring that it cancels the process of adding a new SPOC and closes the pop-up without saving any changes. 10. Verify the Next pagination button. 11. Verify the Previous pagination button. 12. Confirm whether the SPOC name listed in the SPOC Name column are clickable 13. Examine the Next pagination button functionality of the selected SPOC. 14. Ensure the functionality of Previous pagination button of the selected SPOC. |
Admin can view the SPOC person details. | 1. Verify that clicking on the View button displays the detailed information or overview of the SPOC. 2. To verify the functionality of the Back button in the View action, ensuring that it closes the view mode and returns the user to the previous page or section. |
Admin can edit the SPOC name and the details. | 1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of SPOC. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the SPOC details and exit the edit mode. |
Admin can delete a SPOC name by selecting this icon. | 1. To validate the functionality of the Delete button for SPOC, allowing the deletion of existing SPOC from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. |
The business requirement for a Stationery login page may vary depending on the specific needs and goals of the company. However, some common business requirements could apply to a Stationery login page- 1) User Authentication. 2) User Access controls. ... | 1. Check login functionality with a valid username and valid password. 2. Check login functionality using an invalid username and a valid password. 3. Check login functionality using an invalid username and a valid password. 4. Check login functionality with valid username and invalid password. 5. Examine the login functionality by keeping the username and password fields left blanks. |
Admin features submodules such as 1) Stationery, where admin can view the stationery issued and available quantity in the cards, pending requests of the user, Reject and Approve buttons, and Notification icon to see who has requested the stationery in t... | 1. Examine the Admins dashboard functionality, which allows the admin to see the submodules on the dashboard page. 2. Examine the notification icon functionality, which shows whether the request has been approved or pending. 3. Examine the functioning of cards that displays the issued and available quantity of stationery and housekeeping items available in the organization. 4. Examine the dashboard's scrolling button for browsing through stationery objects from the left or right side. 5. Examine the functionality of the Approved button in actions where the admin can approve the stationery request raised by user. 6. Check the functionality of Reject button in Actions where Admin can reject the request raised by the user. 7. Examine the Users dashboard functionality, which includes submodules such as cards and issued item data in table form. 8. Examine the functionality of the notification icon, in which the admin may see the request raised by the user and when a new request occurs, a red dot appears on the notification icon. 9. Determine the profile dropdown functionality on dashboard for logout and switch to user profile. 10. Check to see if the stationery tab is clickable and user redirected to the total stationery page. 11. Examine to see if the housekeeping tab is clickable and navigates you to the total housekeeping page. |
The admin has two submodules under the Stationery Module: stationery and housekeeping. 1) In the Stationery module, the admin can purchase stationery for the organization, add stationery, and view issued stationery in the Graph form. Admin can also down... | 1. Examine the functionality of the 'Stationery module' on admin side by which they can purchase or add stationery in the application. 2. Check that the 'Purchase stationery' button is clickable and enter the required information on the purchase stationery page. 3. Make sure that 'Admin' is able to select the 'Stationery Name' from the dropdown list. 4. Test the 'Quantity' field, where admin inputs figures such as 100, 200, etc. 5. Make sure that admin is able to select the 'Purchase date' from the calendar window. 6. Examine the functionality of the Add stationery button and fill out the essential information on the Add New Stationery page. 7. Examine the description field in the add new stationery page, where the admin enters descriptive information about the stationery he is adding. 8. Check the performance of the Export button in order to generate a monthly report of the stationery module by selecting year and month. 9. Examine the functionality of the year dropdown, from which the admin can select the year. 10. Examine the functionality of the month dropdown, from which the admin can choose the month. 11. Examine the 'Stationery module' feature on the User dashboard, where user raise the request for stationery. 12. Ensure that user can raise the request and check that the raised request is displayed on table of 'Stationery' module. 13. Check that the 'stationery name' field dropdown is clickable, and that the user selects the stationery from the list that appears. 14. Examine the 'Required quantity' field, where the user enters quantities such as 100, 200, etc. 15. Ensure that the user can provide the necessary information on the 'Stationery Request' form. The user then click'sthe 'Add to List' button after entering the information. 16. Examine the Edit functionality of the action's column, where the admin can modify the request as needed. 17. Examine the Delete functionality of the action's column, where admin can delete the request that was added to the list. 18. Examine the functionality of the'submit' button, and see if it is clickable after adding a stationery request to the table. 19. Examine the 'Stationery tab' on the Stationery module, which is only accessible to admin. 20. Examine the 'Housekeeping tab' on the Stationery module, which is only accessible to admin. |
Any stationery and housekeeping products that have been purchased and uploaded will have their individual invoice images displayed in the invoice module. | 1. Examine the functionality when an admin clicks on the Invoice module, the Stationery and Housekeeping tab is displayed to the admin. 2. Observe that all fields that are present on the invoice page are properly aligned. |
Admin users will be able to view products history that have been bought and issued, including how many products have been allocated to employees and how many products have been bought in past days. | 1. After clicking on the history tab/module, ensure that the Issued and Purchase history option is displayed on the page. |
User will view the different services with detailed information. | 1. Examine whether the various services are displayed in card format on the services module screen 2. To ensure that the services listed in card format on the webpage are clickable. 3. To ensure that the services listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each service. 4. To confirm that clicking on the Back button properly redirects the user back to the service module screen. |
Admin can upload for financial year and view from 16 pdf, employee can view and download the form 16. | 1. Evaluate the 'Form 16' functionality on the Home module. 2. Confirm the Financial Year dropdown functionality. 3. Determine the 'Go' button functionality for the Financial Year when Form 16 is unavailable. 4. Examine the 'OK' button functionality of the error pop-up. 5. Make sure the 'Go' button functionality for the Financial Year when Form 16 is available. 6. Confirm the 'Download' button functionality. 7. Examine the columns present on the Form 16 dashboard. 8. Evaluate the workability of the Financial Year dropdown menu. 9. Examine the search bar functionality with appropriate search inputs. 10. Ensure the working of show entries dropdown. 11. Test the pagination of the Dashboard tab screen. 12. Determine the functioning of the upload button on the dashboard tab screen. 13. Evaluate the functionality of the 'Upload' button when an admin tries to Upload a file in inappropriate conditions. |
FNF settlement is known as the full and final settlement. It is a process of calculating different payable dues to an employee who is resigning, retired, or terminated, from an organization. Admin should be able to upload files for employees in FNF sub ... | 1. Ensure 'FNF Report' screen contains all the data as per alignment, size, and style. 2. Examine all the columns present on the FNF Report dashboard screen. 3. Evaluate the working of the Choose File button present under the action column. 4. Confirm that the download function works as expected and the file only downloads in PDF format. 5. Ensure that the Action column's upload feature works as per expectations. 6. Confirm the 'view' icon's functionality. 7. Examine the search bar functionality from the 'FNF Report screen' with appropriate search inputs. 8. Ensure the working of show entries dropdown is present on the 'FNF Report' screen. 9. Test the pagination of the 'FNF Report' home screen. 10. Evaluate for navigating on the previous screen admin can use the breadcrumbs present on the 'FNF Report' screen. 11. Confirm only employees who have 'Date Of Departure' displays in the 'FNF Report' screen. |
Admin user can view team KRA, team self-appraisal and appraise details in chart form. | 1. Ensure that the admin is navigated to the admin dashboard after successful login 2. Ensure that on clicking the Dashboard module, Select Year Dropdown must be auto selected for current date and according to date dashboard data must be changed. 3. Make sure that report must be displayed after filling the details in the Select year dropdown, Appraisal type Dropdown, and hits Go button. |
User can be able to view any appraisal done by manager and download appraisal report. | 1. Ensure that the employee user is navigated to the admin dashboard after successful login 2. User unable to view dashboard, since they do not possess access to it 3. On clicking the Dashboard module, Select Year Dropdown will be auto-selected for current date ,according to date dashboard data must be changed. 4. On clicking the Select year dropdown, select Appraisal type Dropdown, and hits Go button |
Manager can view team KRA, team self-appraisal and appraise details in chart form. | 1. Ensure that the manager is navigated to the manager dashboard after successful login 2. Determine whether the manager cannot view the dashboard because they cannot access it. 3. On clicking the Dashboard module, Select Year Dropdown must be auto-selected for current date,according to date dashboard data must be changed. 4. On clicking the Select year dropdown, select Appraisal type Dropdown, and hits Go button |
This tab should Allow the admin user to appraise any employee.Should be accessible to admin only. Admin can appraise and view previous appraisal.Screen should have 2 dashboards - Approve KRA's & Appraise | 1. On clicking on theAppraise module, Employee list must be shown in Approve KRA'S tab with KRA approve status and Employeelist must be shown in Appraise tab with appraise status. 2. Check user is able to navigate to next page, make sure the next indicator (>>) is active and make sure it is disabled for last page 3. Check user is able to navigate on previous page, make sure the previous indicator (<<) is active and make sure it is disabled for first page. 4. For the employee table, make sure the search box is functional. 5. Check KRA's status of employee table for approve KRA tab. 6. Check the functionality of submitted button which is present in the KRA's status. 7. Ensure that the approved KRA form of the employee must be displayed after clicking on the approved button KRA's status. 8. On clicking on the Appraise tab in the appraise module, the Employee list must be shown in the Appraise tab with appraise status. 9. Check user is able to navigate to next page, make sure the next indicator (>>) is active and make sure it is disabled for last page. 10. Check user is able to navigate on previous page, make sure the previous indicator (<<) is active and make sure it is disabled for first page. 11. For the employee table, make sure the search box is functional. 12. Check appraise status of employee table for appraise tab. 13. Check the functionality of appraise button which is present in the appraise status. 14. Check the functionality of complete button which is present in the appraise status. |
KRA Key responsibility area tab should be accessible by Employee as well as Admin.Where,User can fill KRA for internship, annual, and Project end. and Admin can view and approve the KRA. | 1. Examine the KRA's module and its associated functionalities. 2. Examine for innovation in KRA information fields. 3. Evaluate the execution form fields of KRA information. 4. Validate the KRA information areas on the team form. 5. Check the win form sections for KRA information. 6. Examine admin can be able to upload the excel file of employee's KRA's 7. Confirm the sample export file is downloading while clicks on the sample export file button. |
User should be able to do self-appraisal. | 1. Determine the self-appraisal module for the approved employee. 2. Examine the Self Appraisal module and its associated functionalities. 3. Check the KRA information for Self appraisal tab 4. Examine innovation form fields of self-appraisal information 5. Examine the execute form fields of self-appraisal information 6. Check the 'win' form fields of self-appraisal information 7. Ensure the team form fields of self-appraisal information 8. Examine the overall assessment form fields of self-appraisal information |
Admin user should be able to add rating criteria used for appraisal purpose. | 1. Make sure that by clicking on the rating, self-rating table must appear. 2. Examine that user must be able to add the rating while clicks the add button by entering the ratings in the rating field. 3. Examine that user must be able to edit the rating by hitting the edit icon button which is available in the action column. 4. Examine that user must be able to delete the rating by hitting the delete icon button which is available in the action column. 5. Make sure that number of entries are less than 10 in the self-rating table the previous indicator (<<) and next indicator (>>) are disabled. 6. Ensure search box functionality for the rating table. |
Admin user should be able to add soft skill criteria used for appraisal purpose. | 1. Ensure that the soft skill table appears while clicking the soft skill sub-tab of the admin module. 2. Examine that user can add the skill by hitting the add button by entering the skills in the skill field. 3. Examine that user can edit the skill by hitting the edit button which is available in the action column. 4. Examine that user can delete the skill by hitting the delete button which is available in the action column. 5. Make sure that number of entries are less than 10 in the soft skill table the previous indicator (<<) and next indicator (>>) are disabled. 6. Ensure search box functionality for skill table |
Admin should be able to view total working days and Leaves count.Accessible to Admin only. | 1. Ensure that the user is able to view the employee performance page after clicking on the employee performance module. 2. Make sure that the Year Dropdown must be auto-selected for the current date, and the admin can select the year from the dropdown list. 3. Examine that admin can select the employee's name from the dropdown list. |
User can able to see the different domains with detailed information. | 1. Examine whether the various domains are displayed in card format on the domain module screen 2. To ensure that the domains listed in card format on the webpage are clickable. 3. To ensure that the domain listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each domain 4. Examine whether the user is redirected to a new page or a detailed view of the selected service within the specific domain 5. To confirm that the projects listed under specific domains are easily accessible. 6. To ensure that the clients listed under specific domains are easily accessible, allowing users to navigate to specific client detailed page. 7. Make sure that the tools listed under specific domains are easily accessible. 8. Examine whether the Technology listed under specific domains are accessible. 9. To confirm that clicking on the Back button properly redirects the user back to the domain module screen. |
Users can see the different tools with detailed information once the admin is added. | 1. Examine whether the various tools are displayed in card format on the tools module screen 2. To ensure that the tools listed in card format on the webpage are clickable 3. To ensure that the tools listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each tools 4. Verify the Next pagination button. 5. Verify the Previous pagination button. 6. Examine whether the user is redirected to a new page or a detailed view of the selected service within the specific tool 7. To confirm that the clients listed under specific tools are easily accessible 8. To ensure that the projects listed under specific tool are easily accessible, allowing users to navigate to specific project detailed page 9. Make sure that the technology listed under specific tools are easily accessible 10. Examine whether the domains listed under specific tool are accessible 11. To confirm that clicking on the Back button properly redirects the user back to the tool module screen |
Admin can edit the existing tool by updating the information such as the version or description of the tool. | 1. To ensure the proper functionality of the Edit action button, allowing users to modify the details of technology. 2. To confirm the functionality of the Cancel button in the Edit action, allowing users to discard any changes made to the technology details and exit the edit mode. |
Admin can delete a tool by selecting this action. | 1. To validate the functionality of the Delete button for technology, allowing the deletion of existing technology from the system. 2. To ensure that the Cancel button in the Delete action allows users to cancel the deletion process and close the delete confirmation popup. |
User can see the different technologies with detailed information. | 1. Verify the Technologies module functionality. 2. To ensure that the technologies listed in card format on the webpage are clickable. 3. To ensure that the technologies listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each technology. 4. Verify the Next pagination button. 5. Verify the Previous pagination button. 6. Examine whether the user is redirected to a new page or a detailed view of the selected service within the specific technology 7. To confirm that the clients listed under specific technology are easily accessible 8. To ensure that the projects listed under specific technology are easily accessible, allowing users to navigate to specific project detailed page 9. Make sure that the tools listed under specific technology are easily accessible 10. Examine whether the domains listed under specific technology are accessible 11. To confirm that clicking on the Back button properly redirects the user back to the technology module screen. |
By performing these information gathering tasks, security testers gain valuable insights into the target web application and its infrastructure, enabling them to plan and execute subsequent testing activities effectively to identify and mitigate potenti... | 1. To check the effectiveness of search engine queries in retrieving specific information related to the target. 2. Enumerate the sub-domains by using various other search engines (Bing,DuckDuckGo,Shodan) 3. To perform banner grabbing and analyze the response headers of the web server. 4. To check the behavior of the web server by sending incorrect or malformed requests intentionally. 5. To perform web server fingerprinting using specialized tools and analyze the server type and version based on the responses.(e.g., nmap, Netcraft, Nikto, skipfish, Netcat). 6. To review web server metafiles (e.g., configuration files, log files) for valuable information, server configuration details, potential vulnerabilities, and exposed sensitive data. 7. Check by identifying further paths or resources to include in discovery/analysis using tools(Google Webmaster, curl, wget, Burp Suite, ZAP) 8. To analyze the HTML source code of a web page to gain insights into its structure, functionality, and potential vulnerabilities. 9. Verify the parameters and request headers for GET & POST requests using a proxy tool. 10. Verify the application framework and components been used by the application (WhatWeb, Wappalyzer) 11. Enumerate for the specific files & folders using tools (dirbuster with Burp) 12. Determine the application framework identified from file extensions eg. php,aspx,jsp. 13. N/A 14. N/A 15. Check the the HTTP headers sent and received by the application for some headers, such as cookies, refer, or user-agent, may contain user-controlled or external data that can be manipulated for attacks. 16. N/A |
Configuration and Deployment Management Testing ensures that the network infrastructure, application platform, and associated configurations are appropriately set up, hardened against potential vulnerabilities, and comply with security best practices. B... | 1. To perform brute-force or dictionary attacks against common admin interface URLs or paths. 2. To check for the HTTP verbs that are supported by the web server using tools (Nmap) 3. Examine for access control bypass vulnerability by arbitrary redirect methods 4. Review for the cross-site tracing potentialities using the TRACE method to steal legitimate users’ credentials 5. Checking for HTTP Method overriding by emulating the missing HTTP verbs passing some custom header in the requests 6. Review for HSTS by examine the server response and validity by intercepting proxy 7. N/A 8. N/A 9. N/A 10. N/A 11. N/A 12. N/A 13. N/A 14. Ensure that defaults and known configuration files have been removed and the logging mechanisms set in place for the production environment. 15. N/A 16. Review the Content-Security-Policy header or meta element to identify misconfigurations. |
Security tester ensures that user identities, roles, and access controls are properly managed. It aims to prevent unauthorized access, protect user identities, and maintain the integrity of the authentication and authorization mechanisms. | 1. Check for identifiable roles used by the application through documentation and fuzzing. 2. Asure how administrator provision other administrators or just users 3. N/A 4. N/A 5. Enumerate users where possible through response analysis. |
Authentication Testing focuses on evaluating the security and effectiveness of the authentication mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could potentially lead to unauthorized access or compr... | 1. Test the server to forcefully downgrade to HTTP to exchange credentials without encryption. 2. To analyze the HTTPOnly and Secure attributes for the cookies in response 3. Check by fuzzing the username if they are created with any defaults or identifiable patterns. 4. To ensure authentication bypass by direct page request/forced browsing to check access control across the application 5. Make sure authentication bypass by parameter modification using proxy repeater/interceptor 6. To make sure for authorization bypass by Session ID prediction test 7. Verify for back refresh vulnerability for the application flaw to monitor browser history 8. For analyzing any leaking of any sensitive data into the browser cache stored in the local files 9. N/A 10. N/A 11. N/A 12. N/A 13. N/A 14. N/A 15. N/A |
Authorization Testing focuses on evaluating the effectiveness and security of the authorization mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could lead to unauthorized access or privilege escalatio... | 1. Examine the application for injection points that pertain to path traversal by a systematic evaluation of each input vector 2. Check for input validation bypassing by enumerate all the GER/POST URLs, file upload and forms that accept content from the user. 3. Review for access to administrative pages/functionality when a non-administrative user tries access resources 4. Check for lateral movement attacks, to access resources across users with the same role or privilege 5. Check for vertical privilege escalation to access functions and resources that are role restricted above user level 6. Check if a value of a parameter is used directly to retrieve a database record 7. Revise for OAuth Authorization Server Weaknesses 8. Examine for OAuth Client Weaknesses |
Session Management Testing focuses on evaluating the security and effectiveness of session management mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could lead to unauthorized access, session hijacki... | 1. Ensure the session token by examine the structure and contents for information leakage 2. Determine the session ID randomness and predictability and encryption/encoding by analyzing sequences generated by server 3. Check for the cookie attributes like Secure and HTTPOnly are configured 4. Test for HTST by analyzing the authentication mechanism and its flow. 5. To exploit for the HTTP-based token stored in the client browser and capture the session 6. To check the logout functionality for a user to manually terminate the session 7. Examine for server-side state validation and session timeout due to inactivity 8. N/A 9. N/A 10. N/A 11. N/A 12. N/A |
Input Validation Testing focuses on ensuring that user input is properly validated and sanitized, mitigating the risk of various types of attacks and protecting the application and its users' data. It aims to identify vulnerabilities and weaknesses... | 1. Check the input vectors such as HTTP parameters in POST requests, pre-defined radio, selection values and input fields 2. Ensure the XSS by bypassing the filter via HTTP parameter pollution 3. Examine the SQL vulnerability by inject script in input vectors the interact with DB 4. Examine various SQL injections such as time-based, error-based, union, and out-of-band or vulnerabilities 5. To check the SQL filter bypass techniques (Whitespace, NULL byte, URL encoding, character encoding, Hex encoding) for vulnerabilities 6. Examine for server-side code execution on the web server by code injection 7. Determine code injection by NULL byte, path and dot injection to exploit LFI vulnerabilities 8. To check code execution on the client-side which can lead to other attacks such as cross site scripting (XSS) 9. Check for OS command injection vulnerability by using special characters( | ; & 10. > < ' ! ) in URL 11. Ensure if the chain of communication is vulnerable to smuggling use different methods in a HTTP request 12. Check by using X-Forwarded Host Header to bypass application security 13. Test for web cache poisoning, the ability to poison the caching proxy run by the application itself 14. Testing for Oracle 15. Testing for MySQL 16. Testing for SQL Server 17. Testing PostgreSQL 18. Testing for MS Access 19. Testing for NoSQL Injection 20. Testing for ORM Injection 21. Testing for Client-side 22. Testing for File Inclusion |
Security tester focuses onError Handling to evaluating the application's response to various error conditions and ensuring that sensitive information or system details are not disclosed to potential attackers. It aims to identify vulnerabilities ... | 1. Reviewing the error message to bring out more information or error details from web service 2. N/A |
Weak Cryptography validation focuses on evaluating the cryptographic mechanisms employed by a web application. It aims to identify vulnerabilities and weaknesses in encryption, transport layer security, handling of sensitive information, and maintains c... | 1. Examine the server configuration with protocol versions that can have cryptographic weakness 2. Ensure for active resources (such as CSS) that are loaded into secure pages via insecure channel 3. Check form-based authentication performed over HTTP and asserting HTTP traffic 4. N/A 5. N/A |
Business Logic Testing focuses on evaluating the correct implementation and security of the application's business logic. It aims to identify vulnerabilities and weaknesses in the application's logic flow, data validation, process timing, and ... | 1. Ensure the target functionality, check if for a logical limit set on the functions and if it is properly validated. 2. Ensure the unwelcomed file types are rejected and handled safely. 3. N/A 4. N/A 5. N/A 6. N/A 7. N/A 8. N/A 9. N/A 10. N/A 11. N/A |
Client-side Testing focuses on evaluating the security of the client-side components of a web application, including JavaScript, HTML, CSS, and browser-related features. It aims to identify vulnerabilities and weaknesses that could be exploited by attac... | 1. Check for DOM-xss vulnerability of code execution on active browser content, obtaining input through source and using it in sink 2. Ensure for HTML injection vulnerabilities via innerHTML , document.write() JavaScript method. 3. Check for X-Frame-Option header to mitigate the clickjacking vulnerability 4. N/A 5. N/A 6. N/A 7. N/A 8. N/A 9. N/A 10. N/A 11. N/A 12. N/A 13. N/A 14. N/A |
API Testing involves evaluating the security and functionality of Application Programming Interfaces (APIs) used in web applications or software systems. It focuses on identifying vulnerabilities, misconfigurations, and flaws in API implementations. | 1. Verify discovering APIs for targeted application through passive recon process 2. Verify discovering APIs by actively scanning with tools and documentation 3. N/A 4. N/A 5. N/A 6. N/A 7. N/A |
User can view the list of clients. | 1. Examine whether the various clients are displayed in card format on the client module screen. 2. To ensure that the clients listed in card format on the webpage are clickable 3. To ensure that the clients listed in card format on the webpage are clickable, allowing users to access detailed information or perform actions related to each cllient 4. Examine whether the user is redirected to a new page or a detailed view of the selected service within the specific client 5. To confirm that the projects listed under specific clients are easily accessible 6. To ensure that the tools listed under specific client are easily accessible. 7. Make sure that the technology listed under specific clients are easily accessible 8. To confirm that clicking on the Back button properly redirects the user back to the client module screen |
The information gathering phase in web application penetration testing involves collecting relevant data about the target application. It includes passive techniques like open-source intelligence (OSINT), DNS enumeration, and reviewing archived web page... | 1. Verify the identification of the LMS URL and its subdomains by using Search Engine Operators 2. Check for the revealing error message content and hidden directories or publicly exposed resources. 3. Verify the type and version of the Apache web server for known version-specific exploits 4. Check the information gathered by banner grabbing responses by malformed HTTP requests. 5. Verify webpage comments for information leakage. |
The Configuration and Deployment Management Testing phase in web application penetration testing focuses on evaluating the configuration and deployment processes of the web application to ensure secure and reliable operation. This phase includes activit... | 1. Verify the default or weak credentials on admin interfaces by attempting common usernames and passwords. 2. Verify the default or weak credentials on admin interfaces by using default credentials lists, or performing password spraying attacks. 3. Verify that if secure communication protocols (HTTPS) are enforced by verifying if the application uses SSL/TLS certificates. 4. Verify that HTTP and HTTPS is properly configured within the application. |
The Identity Management Testing phase in web application penetration testing is dedicated to evaluating the authentication, authorization, and user management features of the application. This phase aims to identify potential vulnerabilities and weaknes... | 1. Verify that user applying leave are aligned with business and security requirements. 2. Verify which accounts may provision other accounts and of what type. 3. Check whether the CORP application is vulnerable to account enumeration via the application's error messages. |
The Authentication Testing phase in web application penetration testing focuses on assessing the security and reliability of the authentication mechanisms implemented in the web application. This phase involves activities such as testing the strength of... | 1. Validate the application's user accounts with default passwords. It can be built in administrative credentials. e.g. username-admin, password-12345. 2. Verify the account lockout mechanism by using the incorrect password a number of times, before using the correct password to verify that the account locked out. 3. Verify the unlock mechanisms it involve secret questions to unlock. It link should be a unique one-time link, to stop an attacker from guessing or replaying the link and performing brute force attacks in batches. 4. Verify the Force browsing by directly requesting different page that page check the credentials of user before granting access e.g. http://abc.com/users/administrator. 5. Verify the Parameter modification functionality by modifying the parameters to gain access to the protected areas without providing valid credentials. 6. Check if the CORP application stores sensitive information on the client side browser cache issue from HTTP response headers (Cache-Control: no-cache). 7. Check if access can occur without authorization in CORP application. 8. Check the browser history issue by clicking the Back button after logging out. |
This phase focuses on evaluating the authorization mechanisms of the web application. It involves testing whether users are granted appropriate access rights based on their roles and privileges. The goal is to identify any vulnerabilities or misconfigur... | 1. Verify for injection points that pertain to path traversal. 2. Check for injection locations that are relevant to bypassing strategies. 3. Identify the extent of path traversal (dot-dot-slash attack, Local/Remote file inclusion). 4. Check if horizontal or vertical access is possible to gain administrative functions by force browsing. 5. Check if vertical access is possible to gain administrative functions by force browsing. 6. Verifying injection points related to role/privilege manipulation. 7. Validating for the points where object references may occur and attempting to access control measures and if they're vulnerable to IDOR. 8. Verifying if OAuth implementation is vulnerable or using a deprecated or custom implementation. |
This testing involves assessing the management and security of user sessions within the web application. It aims to ensure that session tokens are securely generated, stored, and invalidated after logout or a specified period of inactivity. The goal is ... | 1. Validating the session tokens, for the same user and for different users where possible to analyze and ensure randomness exists to stop session forging attacks. 2. Verify by modifying cookies that are not signed and contain information that can be manipulated. 3. Check for existing HTML tags that can cause immediate access to DOM resources such as <img> 4. Validate for proper encryption and application-level authentication standards. 5. Validate the user logout interface as a visual indication for intended uses. 6. Validating interval-based session timeout for balanced security and usability. 7. Validate for server-side session termination of the user session mitigating the cached based back-refresh attack. 8. Validate for hard session timeout, all session tokens invalidation 9. Check for enforced server-side session timeout management and expiration. 10. Verify for the JWTs expose sensitive information. 11. Verify if JWTs signature is been tampered or can be modified |
This phase focuses on testing the web application's input validation mechanisms. It aims to identify vulnerabilities related to user input, such as SQL injection, cross-site scripting (XSS), command injection, and other input-based attacks. The goa... | 1. Verify the variables that are reflected in responses and check the input they accept as well as the encoding that gets applied on return. 2. Verify the stored input variables that are reflected on the client side and verify the input they accept as well as the encoding that gets applied on return. 3. Checking SQL injection points, the severity of the injection, and the level of access that can be achieved through it. 4. Verify all the LDAP injection points in web application. 5. Checking XML injection points with XML Meta Characters 6. Checking SSI injection points (Presence of .html extension) with the characters. 7. Verify XPATH injection points by checking for XML error enumeration by supplying a single quote ('): 8. Verify IMAP/SMTP injection points (Header, Body, Footer) with special characters (i.e.: \, ‘, “, @, #, ! |) and exploit. 9. Verifying and assessing the command injection points with special characters (i.e.: |; & 10. > < ' !) 11. Checking whether injecting format string conversion specifiers into user-controlled fields causes undesired behavior from the application. 12. Verify template injection vulnerability points by checking for the templating engine and exploiting. 13. Check for SSRF injection points and test if the injection points are exploitable. |
This testing involves evaluating how the web application handles various error conditions, such as invalid input, server errors, and exceptions. The goal is to identify any information leakage, error messages that reveal sensitive information, or error ... | 1. Validating existing error output (i.e.: Random files/folders (400 series) and analyze the different output returned. 2. Check to see if error messages are logged appropriately and securely. 3. Check if the application reveals detailed error messages containing sensitive data or system information. 4. Verify how the application responds, ensuring it handles errors gracefully and securely. 5. Verify the prevention of detailed error messages that disclose sensitive information by entering invalid or malformed data. 6. Check if error messages are properly logged and monitored by causing intentional errors. 7. Verify the prevention of server and application stack trace leakage by manipulating inputs to trigger exceptions. 8. Check if stack traces or other internal information is exposed. 9. Assess the handling of unexpected or malformed input by providing unexpected or malformed input. |
This phase focuses on testing the web application's business logic to ensure that it operates correctly and securely. It involves evaluating the application's workflows, business rules, data validation, and access control mechanisms. The goal ... | 1. Check the data injection points. 2. Validate that all checks are occurring on the back end and can't be bypassed. 3. Check if you are able to break the format of the expected data and the application behavior. |
This testing involves assessing the security of the client-side components of the web application, such as JavaScript, HTML, and CSS. It aims to identify vulnerabilities, such as cross-site scripting (XSS), client-side code injection, insecure client-si... | 1. Check for DOM sinks and verify against payloads that pertain to every sink type. 2. Check for sinks and possible JavaScript injection points, ensuring that the expected functionality and behavior are achieved. 3. Check HTML injection points and assess the severity of the injected content. 4. Check injection points that handle URLs or paths. 5. Verify the locations that the system could redirect to (Open Redirect) 6. Check for CSS injection points and exploits. 7. Check sinks with weak input validation. 8. Verify endpoints that implement CORS for secure configuration. 9. Check and analyze the application's code for potential sink points and unsafe method usage. 10. Test if the CORP application is vulnerable by loading into an iframe. 11. Verify via a simple web page that includes a frame containing the target and if they are able to bypass. 12. Verify client-side stored data by the CORP application 13. Verify the code handling storage objects against the possibility of injection attacks, such as utilizing invalidated input or vulnerable libraries. |
This phase focuses on testing the security and reliability of the web application's APIs (Application Programming Interfaces). It involves evaluating the authentication and authorization mechanisms, input validation, error handling, and access cont... | 1. Check for API via Passive Recon with Google Hacking and Shodan. 2. Check for API via Active Recon Baseline Scanning with Nmap 3. Check against the password Brute-Force and Password Spraying attacks using a common password wordlist, or custom list. 4. Check for a Password Reset functionality for exploitable Multifactor Authentication Brute-Force, including Base64 Authentication. 5. Check for JSON Web Token Abuse, if it can me modified. 6. Verifying fuzzing using Burp Suite and payloads like SecList for wide and deep fuzzing tests 7. Checking for Cross-Site Scripting (XSS) 8. Checking for Cross-API Scripting (XAS) 9. Checking for SQL Injection 10. Checking by Command Injection in API 11. Check complex access control policies with different hierarchies, groups, and roles. 12. Check an unclear separation between administrative and regular functions, tend to lead to authorization flaws. |
Information Gathering involves both passive and active techniques to gather data from publicly available sources, such as search engines, social media platforms, public records, and organizational websites. It may also include more targeted approaches l... | 1. Examine that identification of the target application's URL, IP address, and subdomains by performing a DNS lookup or Search Operators 2. Make sure last cached/previous version of the targeted application in Internet Archive using Wayback Machine 3. Examine the type and version of web server that a target is running on for known version-specific exploits. 4. Determine webpage comments for information leakage. 5. Check metadata for information leakage. 6. Examine the status code 7. Examine the JavaScript files for information leakage. 8. Ensure that header of request and response analysis which covers methods of HTTP header analysis. 9. Verify where GET/POST are used including the hidden parameters and URL parameters. 10. Examine that where there are any redirects (3xx HTTP status code), 400 status codes, in particular 403 Forbidden, and 500 internal server errors during normal responses (i.e., unmodified requests). 11. Check for possible entry and injection points through custom type headers. 12. Verify for possible entry and injection points where cookies are set (Set-Cookie header), modified, or added to in response. 13. Examine the Application Architecture and technologies used in application using Wappalyzer. 14. Validate the Application Architecture and Application Components like Host, Ports, services/APIs. |
Policy Details section will help the Super Admin/ Admin to enter policy related information. | 1. Examine that admin or super admin can enter Policy name, Policy Purpose, Policy category, Policy Applicability when click on Policy details form.. |
Configuration and Deployment Management Testing refers to the assessment of the security of configuration and deployment processes within a software system. It involves identifying vulnerabilities and weaknesses that may arise due to misconfigurations, ... | 1. Determine the default or weak credentials on admin interfaces by attempting common usernames and passwords. 2. Examine the default or weak credentials on admin interfaces by using default credentials lists, or performing password brute force attacks. 3. Ensure if the application uses SSL/TLS certificates to see if secure communication protocols (HTTPS) are enforced. 4. Ensure that HTTP and HTTPS is properly configured within the application. 5. Examine the identification of unnecessary services or ports that may be accessible by conducting a port scan. |
Identity Management Testing refers to the process of assessing the effectiveness and security of an organization's identity and access management (IAM) system. IAM systems are designed to manage user identities, their authentication, authorization,... | 1. Examine the user roles used by the application, to switch or change another role. 2. Determine that the identity requirements for user registration are aligned with business and security requirements. 3. Ensure processes that pertain to user identification. 4. Determine whether the application is vulnerable to account enumeration via the application's error messages. |
Authentication testing in Penetration Testing focuses on assessing the security and effectiveness of an application or system's authentication mechanisms. The objective is to identify vulnerabilities and weaknesses that could be exploited by attack... | 1. Determine the sensitive information (credentials, Project information etc.) is transmitted through encrypted channel. It assess the privacy/security of the used channels(HTTP/HTTPS). 2. Examine the application's user accounts with default passwords. It can be built in administrative credentials. 3. Ensure the account lockout mechanism by using the incorrect password a number of times, before using the correct password to verify that the account locked out. 4. Make sure that Force browsing by directly requesting a different page that page checks the user's credentials before granting access. 5. Check that Parameter modification functionality by modifying the parameters to gain access to the protected areas without providing valid credentials. 6. Examine the ability of the application against brute Force password guessing using available password dictionaries by evaluating the length & complexity of passwords. |
Authorization testing in Penetration Testing focuses on evaluating the security and effectiveness of an application or system's authorization mechanisms. The objective is to identify vulnerabilities and weaknesses that could allow unauthorized acce... | 1. Determine the injection points that pertain to path traversal. 2. Examine for injection locations that are relevant to bypassing strategies. 3. Identify the extent of path traversal 4. Ensure if horizontal or vertical access is possible? to gain administrative functions by force browsing. 5. Check if vertical access is possible? to gain administrative functions by force browsing. 6. Determine the injection points related to role/privilege manipulation. 7. Validating for the points where object references may occur and attempting to access control measures and if they're vulnerable to IDOR. |
Considering the RBAC The Clinic Owner, HOD, and Freelancer will be able to see this ledger in order to understand the income they are receiving from scheduling appointments through the Appointment ledger for the current week, six months, twelve mon... | 1. Users will not be able to view Appointment ledger page, since they do not have access to it. 2. Users will be able to view Appointment ledger page 3. Users will be able to view Appointment ledger page, since they possess access to it. 4. Users will not be able to view Appointment ledger page 5. FDM user will be able to access the Appointment ledger modules of the clinic that they would be assigned to. 6. On clicking the Appointment ledger module user navigate on OVERVIEW tab,Select Clinic Dropdown will be auto-selected, appointment collection shown for that desired clinic along with CREDIT STATEMENT and INSIGHTS 7. On clicking the Appointment ledger module user navigate on OVERVIEW tab,Select Clinic Dropdown will be auto-selected, and no information shown 8. User should able to view APPOINTMENT COLLECTION for selected desired clinic and changed weekly into monthly or yearly by clicking on arrow icon 9. User's click on IN CLINIC PAYMENTS FOR COMPLETED APPOINTMENTS and navigate on IN-CLINIC Payments,UNPAID tab for checking TODAY'S UNPAID APPOINTMENTS(COUNT) and OLDER'S UNPAID APPINTMENTS(COUNT) 10. On clicking the IN CLINIC PAYMENTS FOR COMPLETED APPOINTMENTS module user navigate on UNPAID tab,Select Clinic Dropdown will be auto-selected, appointment status for TODAY'S UNPAID APPOINTMENTS(COUNT) and OLDER'S UNPAID APPINTMENTS(C... 11. User selects a desired clinic from the Select Clinic dropdown list. 12. User attempts to select more than one clinic from Select Clinic dropdown list. 13. User does not select any clinic from the Select Clinic dropdown list. 14. Clinic is selected by default in the Select Clinic dropdown, the profile card of the respective patients of the clinic with details are displayed. 15. On selecting the desired clinic from the Select Clinic dropdown, the profile card of the respective patients of the clinic are displayed user clicks on the profile card of the patients. 16. On selecting the desired clinic from the Select Clinic dropdown, the profile card of the respective patients of the clinic are displayed user does not click on the profile card of the patients. 17. User chooses a clinic from Select Clinic dropdown and then valid year and month from both the Select Year and Select Month dropdowns respectively. 18. User chooses an invalid year or month from the Select Year and Select Month dropdowns respectively. 19. User chooses to not select any year or month from the dropdowns. 20. User can keep track of the paid appointments, User can select particular Week appointment details by clicking on downward arrow in the week section of the PAID. 21. User don't select particular Week appointment details by clicking on downward arrow in the Week section of the PAID. 22. User don't select particular Week appointment details by clicking on downward arrow in the Week section of the PAID. 23. The user can view the patient count for the chosen clinic's Total Advance Payement Collected, Total Appointment Completed, and Total Refund Given. 24. User can switch between the Today and Last 7 Days toggles by selecting the RECENT tab, browsing from the OVERVIEW tab, and having the Choose Clinic Dropdown automatically selected. 25. On selecting the desired clinic from the Select Clinic dropdown, the profile card of the respective patients of the clinic are displayed for chosen toggle option that is Today ,patients cart are shown according to date 26. On selecting the desired clinic from the Select Clinic dropdown, the profile card of the respective patients of the clinic are displayed for chosen toggle option that is Last 7 Days ,patients cart are shown according to date 27. Without selecting any clinic from the Select Clinic dropdown, the profile card of the respective patients of the clinic are displayed for choosen toggle option that is Last 7 Days ,patients cart are shown according to date 28. Choose the chosen clinic first, or stick with the one that was automatically selected, and then choose For which time do you require a statement from the options of last month, last 3 months, last 6 months, last year, or choose custom range o... 29. Choose the chosen clinic first, or stick with the one that was automatically selected, and then choose For which time do you require a statement from the options of last month, last 3 months, last 6 months, last year, and click on Share butt... 30. Without selecting any clinic from the Select Clinic dropdown, and then choose custom range of dates that is valid start date to valid End date and tries to click on Share button 31. Without selecting any clinic from the Select Clinic dropdown, and then choose For which time do you require a statement from the one of the options from last month, last 3 months, last 6 months, last year and tries to click on Share button 32. Choose the chosen clinic first, or stick with the one that was automatically selected, and without selecting any option directly tries to hit Share button 33. User attempts to select multiple For which period do you require a statement slots in a single try and tries to click Share button. 34. User selects a invalid end date first and a valid start date later, and clicks on Share button, in the CUSTOM tab of Appointment ledger 35. User selects an invalid start date and an invalid end date, and clicks on Share button, in the CUSTOM tab of Appointment ledger. |
CTC Reconciliation for Employee Admin should be able to view active and inactive employee details in data table format, the column contains EMP name, gross CTC, variable pay, payroll status, joining date, revision date. | 1. Confirm the 'Active', and 'Inactive' tabs are present under the CTC Reconciliation tab. 2. Make sure of the Search bar working in the CTC reconciliation tab. 3. Evaluate the Show Entries Functionality 4. Examine the present columns for the 'Active' records. 5. Make sure the administrator's sole role is to view the current activeemployee of the organizationrecords in the Active tab. 6. Confirm the columns which are present on the Inactive tab screen. 7. Evaluate that the admin can't modify the data present on the Inactive tab. 8. By using the pagination feature, Evaluate admin is able to view multiple data entries. |
Using Wallet, the balance will be updated. The amount of the remaining balance will be conspicuously displayed in bold font on the screen, and the number of prescriptions will depend on the availability and Doctor can add money, view analytics, view his... | 1. Users will not be able to view hamburger Wallet tab, since they do not have access to it. 2. Users will be able to view hamburger Wallet tab 3. Users will be able to view hamburger Wallet tab, since they possess access to it. 4. Users will not be able to view hamburger Wallet tab 5. FDM user will be able to access the hamburger Wallet tab of the business that they would be assigned to. 6. On clicking the Wallet tab, the user view Hey,welcome to your wallet !, the on-boarding screen with the details and user does not click on GET STARTED button 7. On clicking the Wallet tab, the user view Hey,welcome to your wallet !, the on-boarding screen with the details keep showing to the user unless the GET STARTED button is clicked. The Onboarding screen would appear by default for the first time. 8. After clicking on GET STARTED ,user navigate on Wallet screen and does not click on DISMISS button 9. The user directly hit the dismiss button of the Free gift card and information card in the Wallet screen. 10. By default for first time user ,current balance should shown 0 with 20 free prescriptions on cart 11. for first time user ,current balance should shown 0 with no free prescriptions on cart 12. Users who have access to the wallet can add money to it by using chips or entering a numerical value and hit ADD button 13. Without adding money to the wallet, the user hits the ADD button. 14. By default the value in the amount box will be 0. If The user clicks the Enter amount link in the WALLET module's card and a Change input value pop-up box appears. The user then enters the value again in the Change input value numeric box... 15. User tries to enter alphabetic data into Change input value numeric box, and clicking the DONE button. 16. User tries to enter no data(Blank data) into Change input value numeric box, and clicking the DONE button. 17. A congratulations message is displayed by clicking +Click here to add 500 more to add more money and receive a larger free balance and user does not hits CONTINUE button 18. A congratulations message is displayed by clicking +Click here to add 500 more to add more money and receive a larger free balance and user hits CONTINUE button and able to add more money using +Click here to add 1000 more 19. User select select value recharge chip for balance with free balance amount and hits CONTINUE button 20. A congratulations message is displayed by clicking +Click here to add 500 more to add more money and receive a larger free balance and user hits CONTINUE button and able to add more money using +Click here to add 1000 more 21. User select select value recharge chip for balance with free balance amount and hits CONTINUE button 22. Without selecting any balance chips user tries to hits CONTINUE button 23. User can enter promo code received from events or concerts and hit APPLY button 24. User tries to hit APPLY button without entering any promo code 25. User tries to enter promo code which is already redeem by another user and hit APPLY button 26. User tries to enter expired promo code and hit APPLY button 27. User tries to enter wrong or incorrect promo code and hit APPLY button 28. Recharge value, transaction fees, taxes, and charges, as well as the total amount with charges, are displayed to the user as a summary and click on PROCEED TO PAY button and navigate to Success! Funds added with new balance card and BACK TO WALLET ... 29. Recharge value, transaction fees, taxes, and charges, as well as the total amount with charges, are displayed blank or null to the user as a summary and hits PROCEED TO PAY button 30. Recharge value, transaction fees, taxes, and charges, as well as the total amount with charges, are displayed wrong to the user as a summary and hits PROCEED TO PAY button 31. User tries to view particular history for that Select year dropdown and do not Select Months dropdown 32. The user attempts to view a certain history for which they choose either the Select year dropdown or the Select Months option 33. User wants to view particular history for that do not any field like Select year dropdown and Select Months dropdown 34. User wants to view particular history for that do not any field like Select year dropdown and Select Months dropdown 35. When the user clicks the arrow icon to expand or vice versa, the name of the selected month with the prescription count is displayed, and the user can examine the list of weeks for prescription based on the selected Select Year and Select Month drop... 36. Click on downward arrow icon for expanding week into day list 37. Click on upward arrow icon for closing expanded list 38. Average prescription created graph ,total prescription created count ,mean number of prescriptions/patient, total free prescription and most number of prescription created are visible to Usage History Analytics for user who can have access to the wallet 39. User able to changed graph by slide and it will reflect as LAST 6 MONTHS , LAST 12 MONTHS and at last LIFETIME and hit Back to recharge button 40. user able to changed graph by slide and it will reflect as LAST 6 MONTHS , LAST 12 MONTHS and at last LIFETIME and does not hit Back to recharge button 41. User can view INSIGHTS with same count after changing graph duration because INSITES i.e. Total prescription created count, Mean number of prescriptions/patient, total free prescription, Most number of prescription created counts will be remains... 42. User can check Current balance and current balance limit should be minimum 1 rs to maximum unlimited amount 43. In Add Money ,user click on Enter an amount button and enter minimum 1 rs to maximum unlimited amount 44. In Add Money ,user click on Enter an amount button and tries to enter 0 in Wallet 45. In addition to having proper user interface (UI), the user should be able to access the cart including the wallet add money andwithdrawpolicy and desired pop-up messages |
In view employee activity admin should be able to view in table, download or view history of payslip and form 16 with time and date of employees. | 1. Evaluate the Employee Activity History button 2. Examine the column for Document Activity History page. 3. Confirm the Search functionality present on the Employee Activity History screen. 4. Ensure the working of show entries dropdown. 5. Test the pagination of the Dashboard tab screen. |
The user will be eligible to access the application after successful login. The Employee will provide their unique identifier, such as a username and password, and will be redirected to the user dashboard page.Users will have access to modules: Home, ... | 1. Examine the outcome when the Login button is clicked while the Username and Password fields are both blank and without verifying the CAPTCHA. 2. Make sure that the image in the tile is displayed on click on the check box. 3. Check whether the tile images shown on the captcha are clickable. 4. Make sure that to skip the shown images and view more options, the skip button is present before selecting any image of them. 5. Examine that when a user fills out all mandatory fields on the Login screen of the Application and clicks the reset button, all fields are successfully reset to their default state. 6. To ensure the behavior of the system when the Login button is clicked with an empty Username field, a non-empty Password field, and without verifying the CAPTCHA. 7. Check the login functionality when the user inputs the Username, leaves the Password field blank, and does not verify the CAPTCHA. 8. Examine the login functionality of the application when an invalid Username and Password are entered, and the CAPTCHA is not verified. 9. When an invalid Username and valid Password are entered, verify the CAPTCHA and click the Login button to examine the response. 10. Check the response when an invalid Username and invalid Password are entered, verify the CAPTCHA and the Login button is clicked. 11. When a valid Username and valid Password are entered, without verifying the CAPTCHA click the Login button to examine the response. 12. Examine that once the user selects any option from the shown image, the skip button will be replaced by the Verify button. 13. If to reset the selected option make sure that the reset functionality is present whenever the CAPTCHA verifies. 14. Ensure that an audio option is present for the CAPTCHA to verify it. 15. Make sure that the Help option is present so that the user may obtain guidance on how to choose the photos from the shown selections. 16. Determine that the error message is shown in case the user selects the incorrect image and verified it. 17. Make sure an error message appears when the page timeout for the verified CAPTCHA. 18. Make sure that when a user enters the invalid password for login, a pop-up notification with the number of attempts is displayed to the user. 19. Confirm that When the user attempts more than three, a new pop-up message is displayed that states, You reached the attempt limit. Please contact the administrator. 20. When a valid Username and valid Password are entered, click the Login button once verify the CAPTCHA to examine the response. 21. Once the user has accessed the Payroll Management System's Home screen, check to see if the Home, Employee, and Investment modules are available. 22. Examine that the Login page's corresponding section, fields, and buttons are displayed with the correct alignments, spellings, font sizes, and font families. |
The user home screen often includes a home that presents a summarized view of their payroll-related data and key performance indicators. andthe user dashboard will provide an introduction to the application along with the scope and vision. It contains... | 1. Ensure that the Payslip functionality, which is clickable on the Report page of the Home module, is available for users so that they can view, download, and print their payslips. 2. Make sure that the Appraisal Letter capability, which is clickable on the Report page of the Home module, is available for users to view, and download their Appraisal Letter. 3. Examine that the Form 16 feature, which is clickable on the Report page of the Home module, is available for users to view and download their Form 16. 4. To read the announcement, make sure the Announcement section is available on the Report page of the Home modulethat cannot be clicked or editable. 5. Make sure the Document & Policy section is available on the Report page of the home modulethat cannot be clicked or editable, where the user can view the documents and policies added by admin. 6. Ensure that the corresponding sections or fields on the Report page of the Payroll Management System's Home module are displayed with correct alignments, spellings, font sizes, and font families. |
The user will have access to the payslip to view, download, and print their pay slips. A payslip will provides a detailed breakdown of an employee's earnings, deductions, and net pay for a specific pay period. | 1. Ensure that the user can easily navigate from the Payslip screen to the Home screen of the Payroll Management System using the Home navigation functionality. 2. Ensure that when the user navigates to the payslip screen, they are presented with the payslip for the current month with the correct details. 3. Ensure that the dropdown functionality is available to the user on the Payslip screen, enabling them to select the year and month for the payslip. 4. Examine that the payslip is displayed for the selected month of the year once the user clicks the Go button, and if the payslip is not present for that month of the year, then the message is displayed as No Data Available. 5. Confirm that when the user clicks the Go button after selecting the year and month, the Download and Print buttons are displayed if the payslip is available for that month. 6. Ensure that when the user clicks the download button, the payslip is downloaded in PDF format. 7. Ensure that when the user clicks the Print button, a print preview pop-up window is displayed before the payslip is printed. In this window, the user can select the printer, save the payslip as a PDF, choose the page layout, and specify the number of pa... 8. Ensure that the corresponding section, fields, and buttons on the Payslip screen are displayed with accurate alignments, spellings, font sizes, and font families. |
The employee module maintains a centralized database or directory to store employee information. It focuses on managing employee-related information and activities. This includes capturing essential information, setting up payroll profiles, defining com... | 1. To view the personal details of the user, ensure that the Employee Master tab is present under the Employee module. 2. Make sure the Bank tab is included in the Employee module to display the user's bank information. 3. Ascertain that the Address tab is present in the Employee module to display the user's address information. 4. To view the user's employment details, confirm that the Employment tab is present under the Employee module. 5. Examine that the Employee modules contain theFamily Members tab is present to view the user's family information. |
This screen displays the total number of questions added, enables a functionality for adding questions, storing images, audio file and video files and display question format table. | 1. Check if all questions are correctly displayed on the question management dashboard. 2. Examinethe template is downloaded to the specified location on the user's device. 3. Ensure that users can select an Excel file for uploading questions. 4. Check whether the valid keyword or term in the search box. 5. Check the Admin can Preview the already added valid data. 6. Check the Admin can edit and update the already added valid data. 7. Check the Admin can Delete the already added valid data. 8. To Test the working of the Previous and Next buttons are clickable. |
Admin will be able to select the image file from the local PC and upload it in the application. There is a functionality to rename as well as delete the file. | 1. Check whether the Image Fields tab is clickable or not |
Admin will be able to select the audio file from the local PC and upload it in the application. There is a functionality to rename as well as delete the file. | 1. Examine the audio fields tab is clickable or not |
Admin will be able to select the video file from the local PC and upload it in the application. There is a functionality to rename as well as delete the file. | 1. Ensure that the functioning of the Communication Test for all skills. |
Admin after clicking on Create questions icon will navigate on new screen, Clicking on Question type dropdown menu is available offering various question types to choose, such as Pick One, Pick Many, Communication, Coding, Dropdown and Drag and Drop. Th... | 1. Check whether the Create Question tab clickable or not. 2. Check the Create Question dashboard shows the question details fields. 3. Check the short name field to enter valid data. 4. Check in the Difficulty Level drop-down field to enter a valid data selection. 5. Check in the Question Type drop-down field to enter a valid data selection. 6. Check in the Skill drop-down field to enter a valid data selection. 7. Check in the Question field to enter a valid data selection. 8. Examine whether the Save functionality is clickable or not. |
The Doctor will be able to view the welcome message on the screen. There will be 2 dropdowns 1) Select single clinic, 2) Select Doctors. Also, they can view the calendar and the holiday list which has been set by the doctor previously. If doctor clicks ... | 1. Users will not be able to view Set Working Schedule sub-module in the Calendar & Appointments module, since they do not have access to it. 2. Users will not be able to view Set Working Schedule sub-module 3. ADD FIRST CLINIC: User navigates to Hybrid Schedule Setup without clicking on +ADD FIRST CLINIC , directly hits the NEXT button 4. User navigates to Hybrid Schedule Setup clicks on +ADD FIRST CLINIC and fills the form to add a Clinic, and hit NEXT button 5. User navigates to Hybrid Schedule Setup clicks on +ADD FIRST CLINIC and fills the form partially to add a Clinic. 6. User navigates to Hybrid Schedule Setup clicks on +ADD FIRST CLINIC and fills the form to add a Clinic,Clinic is added, then user attempts to add another Clinic. 7. ADD BASE OF OPERATIONS: User navigates to Hybrid Visit Schedule Setup on clicking +ADD BASE OF OPERATIONS and without addind adding a base , directly hits the NEXT button 8. User navigates to Hybrid Visit Schedule Setup clicks on +ADD BASE OF OPERATIONS and fills the form to add a base, and hit NEXT button 9. User navigates to Hybrid Visit Schedule Setup clicks on +ADD BASE OF OPERATIONS and click on Next button without filling the form. 10. User navigates to Hybrid Visit Schedule Setup clicks on +ADD BASE OF OPERATIONS and fills the form to add a base,base is added, then user attempts to add another base. 11. On clicking the Hybrid visit module,Select Base Dropdown will be auto-selected, employees checkboxes will be checked and clicks on NEXT button. 12. On clicking the Hybrid visit module,Select Base Dropdown will be auto-selected, employees checkboxes will not be checked and clicks on NEXT button. 13. On clicking the Hybrid module,Select Clinic Dropdown will be auto-selected, employees checkboxes will be checked and clicks on NEXT button. 14. On clicking the Hybrid module,Select Clinic Dropdown will be selected, employees checkboxes will not be checked and clicks on NEXT button. 15. ADD AN EMPLOYEE: User clicks on Select Base dropdown, selects base, clicks on + Add an Employee button, landing on the Registration page for adding the role of the employee. 16. EDIT HOMELOCATION ON THE MAP: The user edits Home location on map for some employees(physiotherapist) and clicks the Next button 17. The user does not edit Home location on map for some employees(physiotherapist) and clicks the Next button 18. CREATE FIRST AREA OF SERVICE: User will not select any area of service, and directly clicks finish button. 19. User will select an area of service, and directly clicks the finish button. 20. User will select multiple areas of service, and directly clicks the finish button. 21. User while selecting multiple areas of service,the areas might intersect each other and directly clicks the finish button. 22. CLINIC AND HOME VISIT APPOINTMENT DURATION: User will click on NEXT button without selecting any time slot. 23. User selects one time slot from the given slots of each Clinic and Home Visit Appointment Duration and clicks on next button. 24. User attempts to select multiple time slots in a single try in both linic and Home Visit Appointment Duration slots respectively and clicks on NEXT button. 25. ENABLE WORKING DAYS: In Enable Working Days form, User selects all the day slots, and hits finish button. (Mon-Sun) 26. In Enable Working Days form, When none of the day slots are selected user hits finish button. 27. In Enable Working Days form, user clicks on an enabled day slot , it lands on Set working hours where the user doesn't schedule working hours and directly clicks on Finish. 28. User selects either a start time or an end time, and clicks on Finish button, in the Set Working Hours page. 29. User selects a valid start time and a valid end time, and clicks on Finish button, in the Set Working Hours page. 30. User selects an invalid start time and an invalid end time, and clicks on Finish button, in the Set Working Hours page. 31. SET WORKING HOURS: HYBRID : CLINIC SPECIFIC Assuming a user has scheduled an enabled day slot in the set working hours, they can duplicate the same schedule to another enabled slot or multiple slots. 32. HYBRID : HOME SPECIFIC Assuming a user has scheduled an enabled day slot in the set working hours, they can duplicate the same schedule to another enabled slot or multiple slots. 33. Assuming a user has scheduled an enabled day slots in the set working hours, they cannot duplicate the same schedule to another disabled slot or multiple slots. 34. User attempts to set a schedule on the disabled working day slots, in the set working hours page. |
In information gathering we collects the information about the target payroll application. This includes identifying the application's infrastructure, technologies, and potential entry points. This involves searching for any sensitive information r... | 1. Verify if any sensitive information related to the payroll application is not publicly available by searching for the application name in search engines. 2. Verify the last cached/previous version of the targeted application in Internet Archive using Wayback Machine 3. Verify the Server field in the server response header reveals information about the server version and type. 4. Check for other headers that may provide about the server version and type. 5. Check if the robots.txt file contains any disallowed paths or directories. 6. Verify the HTML source code of application for tags and their content. 7. Check if the sitemap.xml file for potential information leakage. 8. Verify if there are any comments in the HTML source code of the webpage for information leakage. 9. Verify the redirect bodies within the web pages for information leakage. 10. Look for any front-end debug files that may reveal sensitive information. 11. Analyze the HTTP headers sent in requests to the payroll web application for potential vulnerabilities. 12. Verify the technologies/frameworks used in the application by using Wappalyzer. 13. Checking for the framework/components & their versions used in the application from Error messages. |
This phase focuses on evaluating the security configuration of the underlying infrastructure and deployed components of the payroll application. It involves checking for misconfigurations, open ports or services, or any other weaknesses that could be ex... | 1. Verify the payroll application enforces secure communication protocols (HTTPS) by checking the usage of SSL/TLS certificates. 2. Verify that HTTP and HTTPS is properly configured within the application. 3. Verify the identification of unnecessary services or ports that may be accessible by conducting a port scan. |
This phase involves assessing the effectiveness of identity and access management controls within the payroll application. This helps identify vulnerabilities related to user authentication and authorization or user roles. | 1. Verify the application allows users to switch or change their assigned role, potentially bypassing access restrictions. 2. Check whether the application's error messages on the login page provide attackers with the ability to enumerate valid usernames. |
Authentication testing focuses specifically on evaluating the strength of the authentication mechanisms implemented within the payroll application. It attempts to bypass or exploit authentication controls to gain unauthorized access. This includes testi... | 1. Verify the sensitive information (Username, Password) is transmitted through the security channel of the used HTTPS. 2. Verify for the admin/user accounts with default passwords on URL - http://3.18.184.127:8080/payroll/login.do. 3. Verify the account lockout mechanism by using the incorrect password for number of times on the login page. 4. Verify the unlock mechanisms in the 'Payroll application'. 5. Verify by Force browsing by directly requesting a different page where unauthorized users attempt to access restricted resources directly by manipulating URLs. 6. Verify the Parameter modification functionality by modifying the parameters to gain access to the protected areas without providing valid credentials. 7. Verify whether the application stores sensitive information on the client-side, such as in browser cookies or local storage. 8. Check the browser history issue or back refresh attack by clicking the Back button after logging out. |
This phase focuses on evaluating the effectiveness of authorization controls within the payroll application. We attempt to bypass or escalate privileges to gain unauthorized access to sensitive payroll data. This includes testing for vulnerabilities suc... | 1. Verify the presence of injection points by browsing the payroll application and testing URLs for path traversal vulnerabilities. 2. Verifying injection points related to role/privilege manipulation. For checking vertical access is possible by force browsing. 3. Verifying injection points related to role/privilege manipulation. For check the Horizontal access is possible by force browsing. (For example: Change some Employee id=2 to Employee =1) 4. Validating for the points where object references may occur (Unique Identifier) and attempting to access control measures and if they're vulnerable to IDOR. |
In this phase, checking the security of session management mechanisms implemented within the payroll application. The objective is to identify vulnerabilities such as session fixation, session hijacking, or session timeout issues etc. that could comprom... | 1. Validating the Session Tokens for the Same User. 2. Validating the Session Tokens for the Different User. 3. Check that the proper security configuration is set for cookies (HTTP Only and Secure flag, Same site=Strict) 4. Check whether the application renews the cookie after successful user authentication. 5. Verify the session timeout functionality and ensure that session tokens are unusable after the timeout period. 6. Verify whether the JWTs expose sensitive information. 7. Verify whether the JWTs can be tampered with or modified. |
This phase involves testing input validation mechanisms implemented within the payroll application. This aims to identify vulnerabilities such as cross-site scripting (XSS), SQL injection, or other types of injection attacks that could allow an attacker... | 1. Identifying any variables within the application that are directly reflected in the responses returned to the client. 2. Identifying any input variables stored by the application and reflected on the client-side. 3. Checking for SQL injection points, the severity of the injection, and the level of access that can be achieved through it. 4. Verify all the LDAP injection points in the web application. 5. Verifying and assessing the command injection points with special characters. 6. Verify the XML injection points in the application. 7. Verify template injection vulnerability points by checking for the templating engine and exploiting. 8. Check for Server-Side Request Forgery vulnerability. |
In this phase, examines how the payroll application handles various error conditions. This includes assessing error messages, error codes, and error handling routines. The goal is to identify potential information disclosure vulnerabilities or other wea... | 1. Validating existing error output (i.e.: Random files/folders (400 series) and analyzing the different output returned. 2. Check if the application reveals detailed error messages containing sensitive data or system information. 3. Verify the prevention of server and application stack trace leakage by manipulating inputs to trigger exceptions. |
This phase focuses on evaluating the implementation of cryptographic controls within the payroll application. The objective is to identify weaknesses in encryption and decryption processes that could potentially lead to data exposure or unauthorized acc... | 1. Validate the server configuration (Identify weak ciphers/protocols (ie. RC4, BEAST, CRIME, POODLE) 2. Checking the digital certificate's cryptographic strength and validity. 3. Check for sensitive information (Information used in authentication) transmitted through the various channels (e.g., Credentials, PINs, Session identifiers, Tokens, Cookies…) 4. Check for weak encryption or hashing uses and implementations. |
A sub-module to add new supplier details to the in-app supplier list. Supplier details include name, number, email, city, state, etc. Also, show the current list if present | 1. Check for the submission of valid supply information for supplier registration. 2. Evaluate functionality to alert User when trying to remove Supplier Details that are still in use |
As sub module to check the supply status and make the statute active or inactive of a supplier | 1. Check for the submission of supplier status to add new /updated exiting items 2. Evaluate functionality to alert User when trying to remove Supplier status that is still in use 3. Test the functioning of the Submit button by making a duplicate entry of the status |