requirement_desc
stringlengths 35
257
| test_cases
stringlengths 39
16.2k
|
|---|---|
The Dashboard should let the devotee access all modules and perform certain actions according to available options. | 1. Check whether the mobile Palkhi application can be opened successfully and navigates to the Dashboard. 2. Ensure that the dashboard contains all the required modules as per the specified requirements. |
The Side Manu Bar should let the devotee access all modules from the hamburger and perform certain actions according to available options. | 1. Check whether the home page contains a side bar positioned on the left side with an icon displayed at the top of the left side. 2. Ensure that the sidebar contains all the menu items as per the specified requirements. 3. Ensure that each menu item in the sidebar is clickable & it redirecting to the corresponding section. 4. Observe whether the application's language changes after click on Marathi/English mode from Sidebar menu. |
Devotees can be able to view the details of the committee available in this module. | 1. Make sure that the Palkhi Samiti module contain information about the Palkhi Samiti (पालखी समिती). This includes details such as the committee's purpose, responsibilities, members, contact information. 2. Check the Palkhi Samiti module contain the contact details of all Samiti members with member's name, designation, phone number in table format. |
Link of Timetable for upcoming Palkhi and the rules.The timetable should include the schedule and route details of the Palkhi process. It should also include the rules and guidelines that devotees need to follow during the Palkhi. | 1. Check whether the devotee can open the Palkhi Velapatrak (पालखी वेळापत्रक) module. 2. Check whether the devotee can able to click on श्री साईबाबा पालखी सोहळ्याचे वेळापत्रक & view upcoming Palkhi events date with respective location. 3. Check whether the devotee can able to click on श्री साईबाबा पालखी सोहळ्याचे नियम & view page details. |
Devotees can be able to view Year wise Palkhi images. | 1. Ensure that the devotee can open the Gallery(गॅलरी) module. 2. Check that the devotee can view all the year wise categorized Palkhi images in the Gallery(गॅलरी) module. |
All Aarti and bhajan available in the application.Devotees should be able to access and view the Aarti and Bhajan through the application. | 1. Examine that the devotee can be able to open & read the content of Aarti/bhajan(आरती/ भजन) module. |
Anyone can Donate their donation by filling in their details and using online payment methods. | 1. Ensure that after click on Donation module redirect to saibabapalkhipune.org. 2. Check that devotee can be able to add details correctly into input fields. 3. Check that the by selecting online payment method completed the payments securely. |
Users will see the Photos of all the social work available on this page. | 1. Check that devotee can be able to open the Social Work(सामाजिक कार्य) module. 2. Check that devotee can be able to view all the social work images undertaken by the Palkhi Samiti. |
If the Devotee needs any help, they can contact the committee through available options on this page. | 1. Check that devotee can be able to open the Contact Us (संपर्क करा) module. 2. Ensure the provided address & contact details are correct. 3. Check that the after click on website it redirects to Palkhi page into browser. 4. Check that the after click on Facebook, YouTube, what's app & Instagram application it redirects to Palkhi page. |
Devotees can be able to check all details and images of शिर्डी पालखी भवन. | 1. Check that devotee can be able to open the Shirdi Palkhi Bhavan (शिर्डी पालखी भवन). 2. Ensure the provided information is correct on Shirdi Palkhi Bhavan (शिर्डी पालखी भवन) module. 3. Check the provided images regarding Shirdi Palkhi Bhavan (शिर्डी पालखी भवन). |
Application will have List of all the candidates name on admin side and allow the admin to view, edit the details of candidates. | 1. Ensure that both Active and Inactive tabs are clickable and display the list of respective employee names. 2. Check the alignment of List Of Employees page. 3. To see outcome, click on Add Employee button fill required data and click Save the button. 4. Ensure that new employee cannot be added unless all the mandatory field data is provided. |
Admin have the authority to generate Appointment letter by filling in the details of payroll and generate ID will be created. | 1. Ensure that appointment letter can be generated for an employee by clicking on the name of that employee by using the Generate Appointment Letter button. 2. Check the positioning of all the fields is proper or not. 3. Test the ability to generate the appointment letter without selecting payroll type. 4. To see the response click 'Cancel' button in the generate appointment letter pop up |
Admin have the authority to Create Resume of Employees. Resume includes all the details Skills and Expertise, Experience, Employee History, Personal Info etc. | 1. Make sure that user can create resume of an employee after clicking his name and then Create Resume button. 2. Check whether the positioning of the Create Resume button is proper. 3. Make sure the personal, educational and experience details from My profile getting fetched into resume. 4. Check whether the Preview button is clickable. 5. Ensure the pdf or resume downloaded has properly aligned and clearly visible data. |
Admin have the authority to download personal, Educational, Experience, Insurance etc details in PDF format. | 1. Make sure that admin can download excel file with list of active employees 2. Examine whether the excel file for the list of inactive employees can be downloaded. 3. Check that the Download button is properly positioned. 4. Make sure that 'Preview' button is clearly visible in both dark and light theme. |
Admin have the authority to confirm and Save the details of the Employee so that all the details from user side so that user won’t be able to edit profile. | 1. Make sure that the Edit Profile button is properly positioned 2. Check whether the 'Edit Profile' button is clickable or not. 3. Examine that clicking edit profile button for single employee will not impact for other verified employees. 4. Ensure that Confirm and Save button is visible to admin after clicking edit profile button. |
Admin have the authority to make User profile editable. After making it editable admin can lock the profile by clicking on confirm and save button. | 1. Make sure that the 'Confirm and Save' button is properly positioned 2. Check whether the 'Confirm and Save' button is clickable or not. 3. Examine that clicking confirm and save button for single employee will not impact for other verified employees. 4. Ensure that Confirm and Save button become invisible once after the profile is verified. 5. Ensure that on clicking edit profile button admin is able to edit employee profile details. |
Admin have the authority to edit details of employee i.e., date of designation, joining and resignation. | 1. Make sure that admin is able to edit the employee's details using edit functionality. 2. Check the functionality of 'Cancel' button. 3. Make sure that admin has the authority to 'On' and 'Off' the offboarding process. 4. Check the visibility of the toggle button for offboarding process in both themes. |
Admin have the authority to export list of Active and inactive Employees in excel format. | 1. Click the Excel Export button and check whether the proper excel file of active employees can be downloaded. 2. Check whether the proper excel file of inactive employees can be downloaded. 3. Check the positioning of Excel Export button. 4. Make sure that Excel Export button is visible in Light as well as Dark theme. |
All the details of candidate i.e., personal details, educational and experience details will be entered by user and admin into the My Profile module. These details can be updated further. | 1. Make sure that all the tabs on My Profile page are aligned well and clearly visible to the user. 2. Examine that calendar gets open after clicking on calendar icon and only a valid date can be selected for Date of birth. 3. Check that all the dropdown lists get opened and one of the options from the list can be selected. 4. Ensure that all the Name fields accept alphabets only. 5. To see outcome by entering alphabet or special characters into Mobile Number and Aadhar Number fields. 6. Examine that IFSC code and PAN number field accepts alphanumeric values only up to specific limits. 7. Check the alignment of Next button and check that button is clickable. 8. user's ability to upload new files or change the uploaded file using Upload functionality should be tested. 9. Check whether user is able to add the information in experience details field. 10. Examine Next button functionality by keeping one of the mandatory fields blank. 11. Make sure that Previous page button is clickable for all of the pages except Personal Details page. 12. Ensure that user can confirm and save the filled data after clicking on Confirm and Save button. 13. Examine user's ability to upload the profile picture by selecting a file from local system. 14. Examine user's ability to see the profile picture that is uploaded. 15. Check that the Download button is properly positioned. 16. Check that user is able to download the data in the pdf format. 17. Check the ability of the user to add and save educational details. |
User can reset the password to login the application using this module. It will be supported on both sides admin as well as user side. | 1. user's ability to change the password by entering valid password in New Password and Confirm Password needs to be tested. 2. Ensure that user will not be able to change the password keeping one of the password fields blank. 3. Examine user's ability to change password by entering only number or special characters into the fields. 4. Make sure that user can change password only after satisfying the criteria of the password. 5. Check the ability of module to support different screen sizes. 6. Check the buttons are properly aligned and spellings are correct. |
Allows the users to fill Form 11 used for Provident fund declaration. It will be available for admin as well as user. | 1. See the outcome by clicking on dropdown arrow and selecting one of the options. 2. Make sure that radio buttons can be turned On and Off. 3. Make sure that Father's Name field does not accept numeric data or special characters. 4. Check that Associate Name, Date Of Birth, Blood Group and Marital Status fields are auto filled and correct as per personal details. 5. Ensure that email ID is acceptable into Email ID field only after entering combination of alphanumeric data and special characters. 6. Examine that 'Universal Account Number', “Scheme Certificate number”, “PPO number”, “Aadhar card number” fields accept only numeric data. 7. Ensure that “Previous PF account number”, “PAN card number” and “IFSC Code” fields accept only alphanumeric characters. 8. Examine Download pdf functionality after submitting Form11. 9. Check the buttons are properly aligned and spellings are correct. 10. Check the ability to support different screen resolutions. |
User can fill the Form XIV for contract labor declaration. | 1. Ensure that “Contractor’s name”, “Establishment name”, “Name of work”, “Workman’s name”, “Designation” and “Remarks” fields accept only alphabets. 2. Make sure that “Contractor’s Address', 'Establishment Address', 'Location of work”, “Employment tenure” fields accept all numbers, alphabets, and special characters”. 3. user's ability to enter only numbers into “Wage rate”, Workman’s Serial number” fields to be tested. 4. Check that 'Wage Period' field accepts alphanumeric data. 5. Check that the buttons are properly aligned and spellings are correct. 6. Make sure that the page support different screen resolution. |
Users can fill EPF EX form for exemption from employee Provident fund scheme. | 1. Ensure that Name of the user is auto filled in Member's Name field after opening Form EPF EX and after submitting this form user can download the form as well 2. Check whether the positioning of Submit and Reset button is proper. 3. Check the page for proper breadcrumbs. 4. Check whether the buttons are properly aligned and spellings are correct. 5. Examine the ability of the page to support different screen resolutions. |
User can add nominee for their PF by filling Form2. | 1. Make sure that 'First Name' is auto populated and “Father / husband/mother’s full name”, “Name of the nominee”, “Nominee relationship with member”, “If nominee is minor, name of the guardian who may receive the amount during th... 2. Examine “Account number”, “Total amount/share of accumulation in PF to be paid to each nominee”, “Age” fields accept only numbers. 3. Ensure “Address Permanent/ Temporary”, “Address of the family member”, “Address of the nominee” fields accept alphanumeric data and special characters. 4. Make sure that date can be selected from the calendar, and it should be displayed in the date box in DD-MM-YYYY format. |
While resigning the company user can fill this form. | 1. Make sure that 'Employee Name', 'Employee ID', 'Supervisor/Manager Name', 'Supervisor/Manager ID' fields are auto populated while the user opens Exit Form. 2. Ensure that calendar gets open after clicking the calendar icon and date can be selected. 3. Check that 'Employee Title/Position', 'Employee Department', 'Reason For Termination' fields accepts only alphabets. 4. Click on Exit Form 2 and check that all the radio buttons are working properly and getting turn On and Off after clicking on button. 5. Examine user can reset the details and submit updated details. 6. Check if user kept mandatory field empty and click on submit button. |
Admin can view the list of employees and their family members who are enrolled for Insurance policy provided by the company. | 1. Check whether names of all the employees who have filled their insurance form appears in the table. 2. Ensure that the name of family member is getting added into the table 3. Examine the functionality of show entry tab. 4. Make sure that the data from the table can be filtered using 'Search' bar. |
Admin will have authority to download excel file with the names of employee and their family member to add insurance coverage. | 1. Observe the pagination on the pages 2. Check whether the excel file can be downloaded by clicking the 'Excel Export' button. 3. Ensure that Excel Export button is visible in both theme of screen. 4. Examine whether the excel file contain all the data properly. |
Details regarding users Offer Letter, Access card, Vaccination details, Work location, Vehicle details, Salary Details and Lunch Facility Details can be viewed here. | 1. Make sure that user can raise the request to avail lunch facility using 'Start' button 2. Ensure that the 'Start' button is visible in both light and dark theme. 3. Check the buttons are properly aligned and spellings are correct. 4. Check whether page supports different screen resolutions. |
Details regarding Employees Vaccination details, Offer Letter Dates, Id Card, Access Card, Asset Dates, Work Location and Vehicle details will be displayed and can be edited here. | 1. Examine user's ability to fill the data into respective fields to update the Employee Other Details. 2. Check whether the data getting added to only one employee at a time 3. Make sure that Id card Recovery Amount field become visible if the Id Card status is Lost. 4. Make sure that Access card Recovery Amount field become visible if the Access Card status is Lost. 5. Make sure that Visiting card Recovery Amount field become visible if the Visiting Card status is Lost. 6. Make sure that if Status of ID is changed from Lost to Submitted Recovery amount field should be removed. |
Downloads list of Employees having details like vehicle, Offer letter, ID card etc details | 1. Ensure that Excel Export button is visible in both theme of screen. 2. Check whether the 'Export Excel' button is properly positioned or not. 3. Examine whether the 'Excel Export' button is clickable or not. 4. Examine whether the excel file contain all the data properly. |
Admin can update the status for lunch for Employees i.e., Lunch start date, Lunch End date after receiving the request from the candidates. | 1. Check the ability of admin to approve the employee's lunch facility request. 2. Ensure that admin have the authority to stop the lunch facility of any employee as per requirement. 3. Check all the tabs are properly positioned on 'Lunch Detail' screen. 4. Ensure that the 'Lunch details' screen supports different screen resolutions. |
Excel file with lunch details of the employees can be downloaded by the user. | 1. Ensure that Excel Export button is visible in both theme of screen. 2. Examine whether the excel file contain all the data properly. |
Admin can add Bank details of Employees and display all the Bank details here. This will then reflect on employee side as well. | 1. Make sure that user is able to see account details that are already added, and the details could be edited. 2. Ensure that user can add account details to new employee. 3. Ensure that all the tabs are aligned properly on the page. 4. Check the spellings and breadcrumbs are proper. 5. Examine the functionality of show entry tab. 6. Make sure that the data from the table can be filtered using search bar. |
Admin can download excel file for the salary account details of the employees. | 1. Examine whether the excel file contain all the data properly. 2. Check whether the 'Export Excel' button is properly positioned or not. |
List of employees to be onboarded will be provided here. Admin can create a resume for shortlisted and pending candidates. | 1. Ensure that user can create resume of particular employee from the list by clicking on the name of that employee. 2. Examine the ability of the user to go back to the List Of Employees page by clicking the 'Back to Home Page' 3. Check that Excel Export button is properly positioned. 4. Ensure that excel file with list of onboarding employees can be downloaded using Excel export. 5. Check that number of entries to be shown in table can be selected. 6. Check the search box functionality. 7. Use dropdown filter and check that data from the table can be filtered according to the onboarding phase of employees |
Admin can send mail to the company Employees collectively from the list of employees using own credentials. | 1. To see the outcome, enter valid required data in respective fields and send mail to collective employees by clicking Send button. 2. Check the outcome by keeping one of the required fields blank and clicking Send button. 3. Make sure that without selecting employee names user will not be able to send mail. 4. Ensure that user cannot send the mail using Send button if the 'From Mail' field is blank. 5. To see the outcome, fill data in all the field except Password field and the Send button is clicked. 6. Check that user is not able to send the mail if Mail Subject or Mail Body field is kept blank and the Send button is clicked. 7. Make sure that mail can be sent only after user adds signature to that mail and then clicks on Send button. 8. Check the positioning of the buttons and table on 'Send Mail' screen. |
The feedback for NOC of the offboarding candidates will be provided by the Project Manager from this tab. | 1. Ensure that user is able to search the name of employee from the list and fill the data only for Report Manager NOC field rest fields are in read only mode for report manager. 2. Examine the ability to edit the data only for Report Manager NOC field rest fields are in read only mode for report manager. 3. Check that the buttons are properly aligned and spellings are correct. 4. Check the response of the page for different screen resolutions. 5. Check whether the user has the access to edit other NOC's. 6. Check whether the NOC field to be respective authority is shown at the top. |
The feedback for NOC of the offboarding candidates will be provided by the HR from this tab. | 1. Ensure that user is able to search the name of employee from the list and fill the data only for HR NOC field rest fields are in read only mode for HR user. 2. Check whether the user has the access to edit other NOC's. 3. Check that the buttons are properly aligned and spellings are correct. 4. Response of the page for different screen resolutions need to be checked. 5. Check whether the NOC field to be respective authority is shown at the top. 6. Check whether the status shown in the table for offboarding approval is proper. |
Admin user can view the list of offboarding candidates and edit the feedback given by the Project Manager and HR. | 1. Make sure that admin user is able to search the name of employee from the list and fill the data either for Report Manager NOC field or for HR NOC field. 2. Examine ability to edit and save the data either for Report Manager NOC field or for HR NOC field. 3. Check whether the buttons are properly aligned and spellings are correct. 4. Examine the page supports different screen resolutions or not. 5. Check whether the user has the access to edit other NOC's. 6. Check whether the NOC field to be respective authority is shown at the top. |
NOC for the offboarding candidates for Facilities provided will be given from this tab. | 1. Check the alignment of the table of candidate names. 2. Ensure that search box is properly positioned. 3. Examine whether user can fill and save NOC for one of the candidates from the offboarding list. 4. Examine whether user can edit and save NOC for one of the candidates from the offboarding list. 5. Check whether the user has the access to edit other NOC's. 6. Check whether the NOC field to be respective authority is shown at the top. |
NOC for the offboarding candidates for IT assets will be given from this tab. | 1. Check the alignment of the Offboarding candidate list table is properly aligned. 2. Check whether the search box is properly positioned. 3. Check all the breadcrumbs are proper. 4. Ensure that the NOC for selected candidate can filled and saved by IT Asset admin. 5. Examine whether user can edit and save NOC for one of the candidates from the offboarding list. 6. Check whether the user has the access to edit other NOC's. 7. Check whether the status shown in the table for offboarding approval is proper. |
Employee user can fill and submit the offboarding form. | 1. Check whether the status shown in the table for offboarding approval is proper. 2. Check all the breadcrumbs are proper. 3. Examine whether the Offboard Form tab appears on employee side when the Resignation date is set for that employee. 4. Check the positioning of the 'Offboarding Form' tab and the text boxes in the form as well. 5. Examine user's ability to fill the details in each field of Offboarding form and submit the form. 6. Check whether the user can navigate to next page keeping one of the fields in the form empty. |
Admins have the authority to create Templates i.e., Appointment Letter, Appraisal Letter, Address proof letter etc. | 1. Check the positioning of each button on 'Template' page. 2. Observe the response of the page for different screen resolutions 3. Make sure that admin can create new template using Create Template button. 4. Make sure that blank template cannot be saved by the admin. 5. Ensure that the previously created template can be edited after clicking the pencil icon. 6. To see the response click the delete icon in the action column. 7. Check whether clicking the eye icon allows the user to see the particular template. |
Different types of letter can be created and saved by the admin. Admin will have authority to edit or delete the letter. Also the letter can be downloaded | 1. Examine whether generate letter button allows the admin to generate letter. 2. Ensure that all the features of the formatting toolbar are working properly. 3. Check whether correct data of employee is getting fetched when the name of employee and template is selected to generate letter. 4. Make sure that the letter can be edited after fetching the details. 5. Check that all the fields , data of letter generation module is on proper place and in proper alignment. |
Allows Admin to download letter in PDF format. There is a toggle button which displays Letter head preview. | 1. Ensure that after clicking on the download button, the letter will be downloaded. 2. Check whether the page supports different screen resolutions. 3. Check that the buttons are properly aligned and spellings are correct. 4. Check whether the toggle button allows the admin to add or remove the letterhead to the letter. 5. Make sure that pdf file of letter can be downloaded after clicking the download button. |
Admin have the authority to generate letter of the Employees that is needed by the HRs i.e., relieving letter, Experience Letter, Loan Application Letter etc. Admin can view generated letter. | 1. Examine whether generate letter button allows the HR to generate letter. 2. Ensure that all the features of the formatting toolbar are working properly. 3. Check whether correct data of employee is getting fetched when the name of employee and template is selected to generate letter. 4. Examine whether the data in the letter can be edited after fetching the data. 5. Analyze that data appear on HR letter data table and fields appear on module is as per specification. |
Allows Admin to download letter in PDF format. There is a toggle button which displays Letter head preview. | 1. Ensure that after clicking on the download button, the letter will be downloaded. 2. Check that the page supports different screen resolutions. 3. Check that the buttons are properly aligned and spellings are correct. 4. Make sure that toggle button allows the HR to add or remove the letterhead to the letter. 5. See the response after clicking the download button. |
After logging in successfully, the employee will be taken to the page for the employee dashboard and will then be able to use the TMS program (web app). | 1. Verify the results once the employee has typed the application URL into the browser. 2. Check whether the user is able to login with valid Username and Password. 3. Check whether user is able to access TMS Module. 4. Check the response when User ID field is filled and password field is left empty and the Login button is clicked. 5. To view the outcomes, click the Login button when the User Id field is left empty, and the Password field is filled in. 6. Check whether the user is able to login with invalid Username and invalid Password. |
If a user forgets their current password, the admin or employee will be allowed to change it. | 1. Verify whether the forget password link is available on login screen. 2. Make sure the user can enter a valid ID in the User Id field. 3. Check 'New Password' field accept alpha-numerical-special character. 4. Check whether the user enters the new password and retype/confirm the password. Both should match until the new password should not be set 5. Check that after clicking on Eye icon, entered password is visible to user. 6. Verify the Enter OTP field, which only accepts OTP provided via personal mail. 7. Verify whether success message shows or not once 'Change Password' button has clicked. 8. To verify user can changed the password using same OTP. 9. Check user can change password entering different OTP. 10. If multiple OTP has been send, check 'Enter OTP' field allow user to change the password using only last sent OTP. 11. Examine the response when a user ID is entered and the 'Back' button is clicked. 12. Check on click of the 'Next' button of verfication screen, when User id is entered. 13. Check user navigates to the verification screen, when 'Forget Password' link has been clicked. 14. Verify the response of the 'Verification' screen when user clicks on the 'Next' button without entering the user ID. |
Temporary Id Card module enables admin to record an employee's attendance when their id card is missing. | 1. Verify temporary id card pop-up displays when user click on 'Temporary Id Card' button. 2. Check the calendar is displays once the user click on date field. 3. Verify user can select the employee name using 'Select Employee Name' dropdown. 4. Check the 'Temporary Id card' functionality to assign temporary ID cards to the employee. 5. Determine a click on Add to list button, selected employee data gets added into the list. 6. To reset the preselected employees information, check 'Reset' button functionality. 7. Check user can delete the added temporary id card entry. 8. Verify on clicking on Submit button, attendance entry displays on respective employee's dashboard. 9. Check that when the user clicks on cancel button temporary id card pop-up gets closed. 10. Examine the response, when any mandatory field remains unselected and 'Add to List' button is clicked. |
To allow admin to mark attendance of the employees who worked on the holiday. | 1. Examine the attendance cannot be filled on the last working day of a week if the next day is holiday. 2. Make sure the attendance of last working day in a week will be fill automatically to the upcoming working day. 3. Validate the current day attendance will fill on next day automatically. |
Employees should have access to the current-week status of their timesheet records. The working hours, in-time and out-time for the current month should be displayed. | 1. Examine column chart functionality display the timesheet status of employee, if the attendance is present on dashboard or timesheet has been filled 2. Check Column Chart dropdown displays once the user clicked on it. 3. Determine Column Chart dropdown functionality so employee can view monthly/yearly timesheet status. 4. Check functionality of custom option of Column Chart dropdown. |
Admin should have access to view a list of sub-modules, including Incident Category, Incident Sub-Category, Assignment Group, and Assign To modules, within the Configuration module. | 1. Ensure the functionality of displaying the list of existing sub-modules by clicking on the Configuration module |
Admin/user will see their respective dashboards after logging in to the application. | 1. Check all the tabs on 'Login' dashboard is properly aligned. 2. Enter valid User ID and password into their respective boxes then click on Login button and check for Login . 3. User enters incorrect User ID and password and then clicks on Login button. 4. Check for Login with valid User ID and invalid password then clicking on Login button. 5. Check that users enter invalid User ID and valid password then clicks on Login button. 6. Verify that click on Login button keeping all fields blank and try to Login. |
The user can effortlessly drag and relocate an entire row containing the BR-ID, Req-ID, requirement, and requirement description within the data table of the 'Business requirement' module, allowing for repositioning anywhere within the table. | 1. Ensure that a user can successfully drag and drop a business requirement from one location to another within the business requirement. 2. Make sure the 'BR_ID' displays sequentially after dragging and dropping the business requirement and clicking the update button. 3. Check that the sequential order is reflected in all related modules after the business requirement has been dragged and dropped. |
The system should provide the admin with the ability to manage incident categories. The admin should be able to add, edit, and delete categories for incidents. Additionally, the admin should have access to a tabular view of the category list with search... | 1. Check the behavior of the Submit button when the user attempts to submit a entry without entering any data in the required field. 2. Verifies the functionality of the system to submit an incident category by entering the required data in the corresponding field 3. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with a single click 4. Test the functionality of the Show Entries, Search, and pagination features in a data table. 5. Make sure the functionality of the system to allow the admin to modify an added incident category by clicking on the edit icon. 6. Ensure the functionality of the system to allow the admin to delete an added incident category by clicking on the delete icon. 7. Ensure the functioning of the Submit button by adding the duplicate entry of the category 8. Evaluate functionality to alert Users when trying to remove a Incident category that is still in use |
The system should provide the admin with the ability to manage incident categories. The admin should be able to add, edit, view, and delete sub categories for incidents. Additionally, the admin should have access to a tabular view of the sub category li... | 1. Check the behavior of the Submit button when the user attempts to submit a entry without entering any data in the required field. 2. Verifies the functionality of the system to submit an incident sub-category by selecting the category and entering the required data in the corresponding field 3. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with single click 4. Test the functionality of the Show Entries, Search, and pagination features in a data table. 5. Make sure the functionality of the system allows the admin to modify an added incident sub-category by clicking on the edit icon. 6. Ensure the functionality of the system allows the admin to delete an added incident sub-category by clicking on the delete icon. 7. Ensure the functioning of the Submit button by adding the duplicate entry of the sub-category 8. Evaluate functionality to alert Users when trying to remove a Incident sub-category that is still in use |
The system should provide the admin with the ability to manage assignment groups. The admin should be able to add different assignment groups, view them in a tabular format with search and sort functionality, as well as have access to view, edit, or del... | 1. Check the behavior of the Submit button when the user attempts to submit a entry without entering any data in the required field. 2. Verifies the functionality of the system to submit an assignment group by entering the required data in the corresponding field 3. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with single click 4. Test the functionality of the Show Entries, Search, and pagination features in a data table. 5. Make sure the functionality of the system allows the admin to modify an added assignment group by clicking on the edit icon. 6. Ensure the functionality of the system allows the admin to delete an added assignment group by clicking on the delete icon. 7. Ensure the functioning of the Submit button by adding the duplicate entry of the assignment group |
The system should provide the admin with the ability to manage the assignment of people to groups. The admin should be able to view the assigned persons in a tabular format list with search and sort functionality, as well as have the ability to edit or ... | 1. Check the behavior of the Submit button when the user attempts to submit a entry without entering any data in the required field. 2. Verifies the functionality of the system to add a member by selecting the assignment group and assigning them to a specific task or role 3. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with single click 4. Test the functionality of the Show Entries, Search, and pagination features in a data table. 5. Make sure the functionality of the system allows the admin to modify an added member to the assignment group by clicking on the edit icon. 6. Ensure the functionality of the system allows the admin to remove an added member by clicking on the delete icon. |
The system should provide the admin with the ability to view a list of both active and inactive employee IT account details in the organization. Additionally, admin should be able to view and edit employee details. | 1. Ensure that the navigation functionality works as intended and that the page loads correctly, displaying relevant content related to IT accounts. 2. Determine the accessibility of the breadcrumbs, ensuring that they are properly labeled and can be accessed with single click 3. Verify that the functionality of the Show entries dropdown works accurately and displays the correct number of entries per page according to the user's selection. 4. Make sure that the search feature works correctly, filtering the entries based on the provided input. 5. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences. 6. Test the edit functionality works correctly, and ensure that the admin can edit the IT accounts details of the particular employee 7. Test the Functioning of the Cancel button, the admin can navigate to the back page with single click 8. Ensure that the view icon working as intended, admin can see the IT accounts details of the particular employee 9. Check the functionality of the Inactive tab, the list of inactive employee's IT account details appear and display 10. Verify that the functionality of the Show entries dropdown works accurately and displays the correct number of entries per page according to the user's selection. 11. Make sure that the search feature works correctly, filtering the entries based on the provided input. 12. Validate that the sorting feature functions as expected, allowing users to organize the data based on their preferences 13. Test the edit functionality works correctly, and ensure that the admin can edit the IT accounts details of the particular employee 14. Ensure that the view icon working as intended, admin can see the IT accounts details of the particular employee 15. Test the functioning of Active-Inactive tabs, the related lists appearing on the screen and display the entries in the data table |
In the information gathering stage of a web application penetration test, pertinent information about the target application is gathered. It includes inert methods like browsing old web pages, DNS enumeration, and open-source intelligence (OSINT). Activ... | 1. Verify if any sensitive information related to the application is not publicly available by searching for the application name in search engines. 2. Verify the last cached/previous version of the targeted application in Internet Archive using Way back Machine 3. Verify the Server field in the server response header reveals information about the server version and type. 4. Check for other headers that may provide about the server version and type. 5. Check if the robots.txt file contains any disallowed paths or directories. 6. Verify the HTML source code of application for tags and their content. 7. Check if the sitemap.xml file for potential information leakage. 8. Verify if there are any comments in the HTML source code of the webpage for information leakage. 9. Verify the redirect bodies within the webpages for information leakage. 10. Look for any front-end debug files that may reveal sensitive information. 11. Verify the technologies/frameworks used in application by using Wappalyzer. 12. Checking for the framework/components & their versions used in application from Error messages. |
Web application penetration testing's Configuration and Deployment Management Testing phase focuses on analyzing the web application's configuration and deployment procedures to guarantee their security and dependability. Testing configuration... | 1. Verify the application enforces secure communication protocols (HTTPS) by checking the usage of SSL/TLS certificates. 2. Verify that HTTP and HTTPS is properly configured within the application. 3. Verify the identification of unnecessary services or ports that may be accessible by conducting a port scan. |
The Authentication Testing phase in web application penetration testing focuses on assessing the security and reliability of the authentication mechanisms implemented in the web application. This phase involves activities such as testing the strength of... | 1. Verify the sensitive information (Username, Password) is transmitted through the security channel of the used HTTPS. 2. Verify the account lockout mechanism by using the incorrect password for number of times on the login page. 3. Verify the unlock mechanisms in the application. 4. Verify by Force browsing by directly requesting a different page where unauthorized users attempt to access restricted resources directly by manipulating URLs. 5. Verify the Parameter modification functionality by modifying the parameters to gain access to the protected areas without providing valid credentials. 6. Verify whether the application stores sensitive information on the client-side, such as in browser cookies or local storage. 7. Check the browser history issue or back refresh attack by clicking the Back button after logging out. |
Evaluation of the web application's authorisation systems is the main goal of this phase. On the basis of their responsibilities and privileges, it involves evaluating whether users are given the proper access permissions. The aim is to locate any ... | 1. Verify the presence of injection points by browsing the TMS module and testing URLs to path traversal vulnerabilities. 2. Verifying injection points related to role/privilege manipulation. For check the vertical access is possible by force browsing. 3. Verifying injection points related to role/privilege manipulation. For check the Horizontal access is possible by force browsing. 4. Validating for the points where object references may occur (Unique Identifier) and attempting to access control measures and if they're vulnerable to IDOR. |
Administration and security of user sessions within the web application are being evaluated throughout this testing. After logout or a predetermined amount of inactivity, it aims to ensure that session tokens are safely produced, saved, and invalidated.... | 1. Validating the Session Tokens for the Same User. 2. Validating the Session Tokens for the Different User. 3. Check that the proper security configuration is set for cookies (HTTP Only and Secure flag, Samesite=Strict) 4. Check whether the application renews the cookie after successful user authentication. 5. Verify the session timeout functionality and ensure that session tokens are unusable after the timeout period. 6. Verify whether the JWTs expose sensitive information. 7. Verify whether the JWTs can be tampered with or modified. |
Input validation techniques of the web application are tested during this phase. Input-based attacks like SQL injection, cross-site scripting (XSS), command injection, and other input-based attacks are among the user input-related vulnerabilities it see... | 1. Identifying any variables within the application that are directly reflected in the responses returned to the client. 2. Identifying any input variables stored by the application and reflected on the client-side. 3. Checking for SQL injection points, the severity of the injection, and the level of access that can be achieved through it. 4. Verify all the LDAP injection points in web application. 5. Verifying and assessing the command injection points with special characters. 6. Verify the XML injection points in the application. 7. Verify template injection vulnerability points by checking for the templating engine and exploiting. 8. Check for Server-Side Request Forgery vulnerability. |
During this testing, the web application will be examined to see how it responds to several problem scenarios, including invalid input, server issues, and exceptions. The intention is to spot any data leaks, sensitive information-containing error messag... | 1. Validating existing error output (i.e.: Random files/folders (400 series) and analyze the different output returned. 2. Check if the application reveals detailed error messages containing sensitive data or system information. 3. Verify the prevention of server and application stack trace leakage by manipulating inputs to trigger exceptions. |
Business Logic testing stage focuses on evaluating the business logic of the web application to make sure it functions properly and securely. It entails assessing the application's business rules, data validation, processes, and access control syst... | 1. Validate that all checks are occurring on the back end and can't be bypassed & test to break the format of the expected data and the application behavior. 2. Check for user-level access to modify or read. That data in application which have not access to user for read or modify. 3. Verify that the unwelcomed file types are rejected and handled safely and check for Content-type or file extension. 4. Test to upload the malicious files to the application and determine whether it is accepted and processed. |
APIs (Application Programming Interfaces) of the web application are tested during this phase to ensure its security and dependability. It entails assessing the APIs' authentication and authorisation procedures as well as input verification, error ... | 1. Check for API via Passive Recon with Google Hacking and Shodan. 2. Check for API via Active Recon Baseline Scanning with Nmap 3. Check against the password Brute-Force and Password Spraying attacks using a common password wordlist, or custom list. 4. Check complex access control policies with different hierarchies, groups, and roles. |
Admin should be able to view gross CTC graph of employees, using filter monthly and yearly. | 1. Examine the dropdown feature are present, which contains 'By Employee', 'By Year', and 'By Month' options. 2. Make sure the Gross CTC is displayed by employee, year, and month of employees by using the search feature. 3. Ensure that the search functionality allows the admin to look up the Gross CTC for many employees. 4. Evaluate the Goss CTC of employee will appear 'by Year' and 'by Month'. 5. Confirm the back button will redirect admin to the Appraisal dashboard screen. 6. Ensure the alignment is proper for the 'Graphical representation' page as well as for the dropdown present on it. |
The candidate's details will be reflected in the card form. The candidate's image, name, designation, recruiter name, interviewer name, in-time, out-of-time, and feedback form will all be included in the data. | 1. To enroll in job openings, applicants need to scan the QR code first. 2. When the candidate enters the candidate's Aadhar number, the system determines whether the candidate is a new or revisit applicant. 3. If the candidate returns, his or her data will be automatically reflected in the form; he or she can change the information and submit the form. 4. If the candidate is visiting for the first time, he or she must fill out the form completely before submitting it. 5. In the Job Seekers tab, the user can view the candidates for today. 6. The user can find a certain applicant or any recruiter's candidate by using the Search bar. 7. If the user wants to look at the prior candidate's list, the calendar will display the specific date list. 8. The candidate's details can be modified by selecting the edit symbol for that candidate. 9. The view icon is available on each candidate card and can be used to view a specific contender's details. 10. The Add Candidate button allows users to directly add any candidate to the Job Seekers tab. 11. Examine the response when the add button is clicked without entering any values into the form. 12. The user can remove any values they have entered on the form by clicking the reset button on it. 13. Ensure that if the user wants to filter the candidate information between Today, Yesterday, the current week, the current month, and all. 14. Examine the excel icon functionality by clicking on it for selected date candidate excel is downloaded or not. |
Version of the policy is tracked in this module by the Super Admin and the admin. Details of the change, Modified by, reviewed by, Status of the policy and the date for the version. | 1. Ensure that the Policy Version tab is not visible while creating new policy. 2. Check the proper alignment of Policy Version page. 3. Examine whether the new row gets added to the Policy Version table every time after updating the policy. 4. Examine whether admin can see the Policy Version table for all the policies that were previously added. 5. Make sure that the super admin can see the Policy Version table for all the policies that were previously added. 6. Check the functionality of pencil icon(Edit) and edit the revision history for the policy. 7. Check the ability to reset the data in policy version table data after clicking on reset button. 8. Ensure the proper alignment of Revision History window. 9. Examine the ability to update revision history by keeping the fields in window blank. |
The interviewer will have access to a feedback form and will grade the candidate based on their performance during the interview. | 1. Ensure that the response is positive when the user enters valid credentials and clicks on the login button. 2. Check that the count entries in the tabular format are reflected in the show entries dropdown. 3. Using the Search bar check whether the entries are reflected on the screen analogous to the values entered in the search bar. 4. Ensure that the Pagination button navigates the user to the Next or Previous page. 5. Check the number of entries displayed on the screen is reflected in the bottom left corner out of the total entries. 6. Make sure that user can add feedback values in the feedback form of the particular candidate and using the submit button the form is submitted. 7. Ensure that when the user clicks on the Cancel button, the user navigates to the dashboard, and the entered values are not saved. 8. Ensure that, for the revisit candidate, the user is able to view the feedback value submitted by the previous interviewer. 9. The user will be able to add new feedback values in reference to prior feedback values. 10. Using the search bar, the user can easily find any details of the candidate feedback in tabular format. 11. Using the show entries dropdown, the user can verify any entries that haven't been displayed on the screen at that time. 12. Check the count of which entries are displayed on the screen in tabular format and also the out-of-total count in the bottom left corner. 13. Check the PAGINATION button at the bottom right of the history table to display the previous and next page information of the candidate feedback history in the table. 14. The feedback icon allows the user to view the interview feedback provided by the interviewer. |
By performing these information gathering tasks, security testers gain valuable insights into the target web application and its infrastructure, enabling them to plan and execute subsequent testing activities effectively to identify and mitigate potenti... | 1. Determine the application components frontend code using different browsers and tools. 2. Examine the entry points/attack vectors within the application by directory brute forcing and intercepting requests. |
Configuration and Deployment Management Testing ensures that the network infrastructure, application platform, and associated configurations are appropriately set up, hardened against potential vulnerabilities, and comply with security best practices. B... | 1. Testing Amazon S3 Bucket Misconfiguration to examine the access control configuration for the storage resources. |
Security tester ensures that user identities, roles, and access controls are properly managed. It aims to prevent unauthorized access, protect user identities, and maintain the integrity of the authentication and authorization mechanisms. | 1. Examine the user roles by analyzing the application. |
Authentication Testing focuses on evaluating the security and effectiveness of the authentication mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could potentially lead to unauthorized access or compr... | 1. Review of the application allows access without authorization by storing sensitive information on the client side. 2. Review and assess new user accounts and if they are created with any defaults or identifiable patterns. 3. Enumerate the applications for default credentials and validate if they still exist. |
Authorization Testing focuses on evaluating the effectiveness and security of the authorization mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could lead to unauthorized access or privilege escalatio... | 1. Identify relatable injection points to fuzz or otherwise attempt to bypass security measures. 2. Identify attack surfaces to check the access control measures if vulnerable to IDOR or not. 3. Identify attack surfaces that pertain to path traversal to identify the extent of path traversal using bypassing techniques. 4. Ensure that authentication is applied across all requests that require it to avoid unintentional open/public resources. |
Session Management Testing focuses on evaluating the security and effectiveness of session management mechanisms implemented in a web application. It aims to identify vulnerabilities and weaknesses that could lead to unauthorized access, session hijacki... | 1. Analyze the response by forcing cookies to authenticate the user to check cookie is refreshed or not. |
Input Validation Testing focuses on ensuring that user input is properly validated and sanitized, mitigating the risk of various types of attacks and protecting the application and its users' data. It aims to identify vulnerabilities and weaknesses that... | 1. Testing for stored xss script injected and reflected on client-side successfully 2. Test for Host header to check by supplying another domain (i.e. attacker.com) into the Host header field. 3. Test for X-Forwarded Host Header Bypass to successfully supply the value to the X-Forwarded-Host header. |
Security tester focuses on Error Handling to evaluating the application's response to various error conditions and ensuring that sensitive information or system details are not disclosed to potential attackers. It aims to identify vulnerabilities and we... | 1. Determine error responses of the web server or application are not disclosing sensitive information |
Weak Cryptography validation focuses on evaluating the cryptographic mechanisms employed by a web application. It aims to identify vulnerabilities and weaknesses in encryption, transport layer security, handling of sensitive information, and maintains c... | 1. Ensure that the TLS security is not bypassable and is properly implemented across the application by reviewing server configuration 2. Checking for session tokens send over secure channel, by forcing HTTP request. |
Business Logic Testing focuses on evaluating the correct implementation and security of the application's business logic. It aims to identify vulnerabilities and weaknesses in the application's logic flow, data validation, process timing, and other busi... | 1. Check if the website verifies the file extension of the file before uploading it to resource the folder. 2. Check if other uploaded files can be accessed directly by specified URL. 3. Check if the uploaded file can include code or script injection. |
Client-side Testing focuses on evaluating the security of the client-side components of a web application, including JavaScript, HTML, CSS, and browser-related features. It aims to identify vulnerabilities and weaknesses that could be exploited by attac... | 1. Testing for DOM-Based Cross-Site Scripting Vulnerability 2. Testing for HTML Injection vulnerability 3. Testing Cross-Origin Resource Sharing Vulnerability 4. Testing for Clickjacking vulnerability |
API Testing involves evaluating the security and functionality of Application Programming Interfaces (APIs) used in web applications or software systems. It focuses on identifying vulnerabilities, misconfigurations, and flaws in API implementations. | 1. Checking rate limit by performing a brute force attack on the same user account to exploit weak or predictable tokens. 2. Examine the limit/throttle time for a single API client/user can execute a single operation (e.g. validate an OTP, or request password recovery without visiting the one-time URL). |
Application will have Designing Standards screen accessible by admin only, that displays list of standard tables segregated by design type | 1. Examine functionality for 'Designing Standards' tab 2. Validate Designing standards screen 3. Check to see that all Text link, headers, and icons from Designing standards screen are appropriately positioned. 4. Check to see if Occupancy screen is compatible with different screen resolutions. |
The admin will be able to update the standards for certain fields for the new design criteria of Occupancy, through this module. | 1. Examine the functioning of 'New Design Criteria' text button from Occupancy card 2. check 'New Design Criteria' screen (Occupancy) 3. Test the functionality of edit (icon) button from 'Action' column from 'New Design Criteria' table (Occupancy) 4. Verify functioning of 'Back' button from 'New Design Criteria' screen (Occupancy) 5. Check that all columns, headers, breadcrumbs and icons from New Design Criteria-(Occupancy) screen are appropriately positioned. 6. Check to see if the New Design Criteria-(Occupancy) screen is compatible with different screen resolutions. |
The admin will be able to update the standard for certain fields for the existing design criteria of Occupancy, through this module. | 1. Test the functionality for 'Existing Design Criteria' text button from Occupancy card 2. Evaluate 'Existing Design Criteria' screen (Occupancy) 3. Examine the functionality for edit (icon) button from 'Action' column from 'Existing Design Criteria' table (Occupancy) 4. Test the functioning of 'Back' button from 'Existing Design Criteria' screen 5. Ensure that all columns, headers, breadcrumbs and icons from Existing Design Criteria-(Occupancy) screen are appropriately positioned. 6. Check to see if the Existing Design Criteria-(Occupancy) screen is compatible with different screen resolutions. |
The admin will be able to update the standard for certain fields for the occupancy details of Occupancy, through this module. | 1. test the functionality for 'Occupancy Details (Annexure4)' text button from Occupancy card 2. Evaluate 'Occupancy Details (Annexure4)' screen 3. Test the functionality for edit (icon) button from 'Action' column 4. Examine functionality for 'Add' button from 'Occupancy Details (Annexure4)' screen 5. Ensure the functioning of 'Back' button from 'Occupancy Details (Annexure4)' screen 6. Ensure that columns, headers, breadcrumbs and icons from 'Occupancy Details (Annexure4)' screen are appropriately positioned 7. Check to see if the 'Occupancy Details (Annexure4)' screen is compatible with different screen resolutions. |
The admin will be able to update the standards for certain fields for Miscellaneous Storage, through this module. | 1. Check the functioning of 'New Design Criteria' text button from Miscellaneous card 2. Evaluate 'New Design Criteria' screen (Miscellaneous) 3. Examine functionality for edit (icon) button from 'Action' column from 'New Design Criteria' table. 4. Test the functioning 'Back' button from 'New Design Criteria' screen (Miscellaneous) 5. Ensure that all columns, headers, breadcrumbs, navigation tabs and icons from 'New Design Criteria' (Miscellaneous) screen are appropriately positioned or not. 6. Check to see if the 'New Design Criteria' (Miscellaneous) screen is compatible with different screen resolutions. |
The admin will be able to update the standards for certain fields of rack storage CMDA system for the new system criteria of Single, double row rack where storage height is greater than 12 ft to less than equal to 25 ft., through this module. | 1. Check the functionality for 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' text button under tag New System Criteria' from 'Rack Storage-CMDA system' card 2. Examine 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen (Storage height 'including 15ft') 3. Evaluate 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen (Storage height '16 to 18ft') 4. Validate 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen (Storage height '19 to 20ft') 5. Check 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen (Storage height '21 to 22ft') 6. Test 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen (Storage height '23 to 25ft') 7. Check the functioning of edit (icon) button from 'Action' column from 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' table 8. Test 'Back' button functionality from 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen 9. Check to see if all columns, headers, breadcrumbs, navigation tabs, and icons from 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' (Rack Storage-CMDA) screen are appropriately positioned or not. 10. Ensure that 'Single-Double Rack Storage - Storage Height >12 and <=25 ft.' screen is compatible with different screen resolutions. |
Through this module, the admin will be able to update the standard for certain fields of rack storage CMDA system for the multi row rack where rack dept is less than equal to 16 ft. | 1. Check functioning for 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' text button under tag 'New System Criteria' from 'Rack Storage-CMDA system' card 2. Examine functionality for 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (including 15 ft) 3. Test 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (storage height 16ft to 18ft) screen 4. Check functionality for 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (storage height 19ft to 20ft) screen 5. Validate functionality for 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (storage height 21ft to 22ft) screen 6. Examine the functionality of 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (storage height 23ft to 25ft) screen 7. Check functionality for edit (icon) button from 'Action' column from 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' table 8. Examine 'Back' button functionality from 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' screen (Rack Storage-CMDA) 9. Ensure that, all columns, headers, breadcrumbs, navigation tabs, and icons from 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' (Rack Storage-CMDA) screen are appropriately positioned 10. Check to see if the 'Multi Row Rack Storage - Multi Row-rack aisle>=8ft, rack depth<=16feet, storage>12<=25ft' screen is compatible with different screen resolutions. |
The admin will be able to update the standard for certain fields of rack storage CMDA system for the multi row rack where rack dept is greater than 16 ft., through this module. | 1. Verify functionality for 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' text button under tag 'New System Criteria' from 'Rack Storage-CMDA system' card 2. Examine functionality for 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' (Including 15ft) screen 3. Check the functioning for 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' (16 to 25ft) screen 4. Verify functionality for edit (icon) button from 'Action' column from 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' table 5. Check 'Back' button functionality from 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' screen (Rack Storage-CMDA) 6. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' (Rack Storage-CMDA) screen are appropriately positioned 7. Check to see if the 'Multi Row Rack Storage - Multi Row-rack aisle<8ft, rack depth>16feet, storage>12<=25ft' screen is compatible with different screen resolutions. |
The admin will be able to update the standard for certain fields of rack plastic CMDA system for the new system criteria where packaging type is exposed, through this module. | 1. Check functionality for 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' text button under tag 'New System Criteria' from 'Rack Storage-CMDA system' card. 2. Examine functionality for 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' screen (Rack Plastic-CMDA) 3. Test the functioning of edit (icon) button from 'Action' column from 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' (Rack Plastic-CMDA) table 4. Check 'Back' button functionality from 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' screen (Rack Plastic-CMDA) 5. Ensure that all columns, headers, breadcrumbs, and icons from 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' (Rack Plastic-CMDA) screen are appropriately positioned 6. Check to see if the 'Rack Plastic - CMDA group A Plastic Cartoned expanded and non-expanded' (Rack Plastic-CMDA) screen is compatible with different screen resolutions. |
The admin will be able to update the standard for certain fields of rack plastic CMDA system for the new system criteria where packaging is exposed, through this module. | 1. Check functionality for 'Rack Plastic - CMDA Group A Plastic Exposed' text button under tag 'New System Criteria' from 'Rack Storage-CMDA system' card 2. Examine 'Rack Plastic - CMDA Group A Plastic Exposed' screen (Rack Plastic-CMDA) 3. Test the functionality for edit (icon) button from 'Action' column from 'Rack Plastic - CMDA Group A Plastic Exposed' (Rack Plastic-CMDA) table 4. Check 'Back' button functionality from 'Rack Plastic - CMDA Group A Plastic Exposed' screen (Rack Plastic-CMDA) 5. Ensure that all columns, headers, breadcrumbs, and icons from 'Rack Plastic - CMDA Group A Plastic Exposed' (Rack Plastic-CMDA) screen are appropriately positioned 6. Check to see if the 'Rack Plastic - CMDA Group A Plastic Exposed' (Rack Plastic-CMDA) screen is compatible with different screen resolutions. |
The admin will be able to update the standard for certain fields of rack storage CMDA system for the density adjustment factor of existing system criteria, through this module. | 1. Verify functionality for 'CMDA Density adjustment Based on Storage height for Existing System Criteria' text button under tag 'CMDA- Adjustment Factor' from 'Rack Storage- CMDA System' card 2. Examine 'CMDA Density adjustment Based on Storage height for Existing System Criteria' screen (Rack Storage- Existing-CMDA) 3. Test the functioning of edit (icon) button from 'Action' column from 'CMDA Density adjustment Based on Storage height for Existing System Criteria' (Rack Storage- Existing-CMDA) table 4. Test 'Back' button functionality from 'CMDA Density adjustment Based on Storage height for Existing System Criteria' screen (Rack Storage- Existing-CMDA) 5. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'CMDA Density adjustment Based on Storage height for Existing System Criteria' (Rack Storage- Existing-CMDA) screen are appropriately positioned 6. Check to see if the 'CMDA Density adjustment Based on Storage height for Existing System Criteria' screen is compatible with different screen resolutions. |
The admin will be able to update the standard for certain fields for rack storage CMDA system for the existing system criteria of single, double row rack, where storage height is greater than 12 ft and less than equal to 25 ft., through this module. | 1. Check functionality for 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' text button under tag 'Existing System Criteria - Multi-Row Rack Storage' from 'Rack Storage-CMDA system' card 2. Test the working of edit (icon) button from 'Action' column from 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' (13ft to 20ft) table 3. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen are appropriately positioned or not. 4. Check to see if the 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen is compatible with different screen resolutions. 5. Check 'Back' button functionality from 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen (Rack Storage-CMDA) 6. Examine 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen (Rack Storage-CMDA) 7. Examine 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen (21ft to 22ft) 8. Check 'Single-Double Rack Storage - Storage Height > 12 and < 25 ft' screen (23ft to 25ft) |
The admin will be able to update the standard for certain fields for rack storage CMDA system of multi row rack where rack dept is less than equal to 16ft., through this module. | 1. Test the functionality of 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' text button under tag 'Existing System Criteria - Multi-Row Rack Storage' from 'Rack Storage-CMDA system' card 2. Examine 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen (Up to 15ft) 3. Check 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen (16ft to 20ft) 4. Validate 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen (21ft to 25ft) 5. Test the working of edit (icon) button from 'Action' column from 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' (Up to 15ft) table 6. Examine 'Back' button functionality from 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen (Rack Storage-CMDA) 7. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen are appropriately positioned 8. Check to see if the 'Multi row rack aisle >= 8 ft rack dept <= 16 feet storage > 12 <= 25 ft' screen is compatible with different screen resolutions. |
The admin will be able to update the standard for certain fields for rack storage CMDA system of multi row rack where rack dept is greater than 16 ft., through this module. | 1. Check the working of 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' text button under tag 'Existing System Criteria - Multi-Row Rack Storage' from 'Rack Storage-CMDA system' card 2. Validate 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen (Up to 15ft) 3. Check 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen (16ft to 20ft) 4. Examine 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen (21ft to 25ft) 5. Check the working of edit (icon) button from 'Action' column from 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' (Up to 15ft) table 6. Check 'Back' button functionality from 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen (Rack Storage-CMDA) 7. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen are appropriately positioned. 8. Check to see if the 'Multi row rack aisle < 8 ft rack dept > 16 feet storage > 12 <= 25 ft' screen is compatible with different screen resolutions. |
The admin will be able to update the standard for certain fields for rack storage CMSA system through this module. | 1. Check the working of 'CMSA Rack Storage' text button under tag 'CMSA System' from 'Rack Storage-CMSA system' card 2. Examine 'CMSA Rack Storage' screen (Class I) 3. Check 'CMSA Rack Storage' screen (Class II) 4. Validate 'CMSA Rack Storage' screen (Class III) 5. Evaluate 'CMSA Rack Storage' screen (Class IV) 6. Examine the functionality for edit (icon) button from 'Action' column from 'CMSA Rack Storage' table 7. Test 'Back' button functionality from 'CMSA Rack Storage' screen (Rack Storage-CMSA) 8. Ensure that all columns, headers, breadcrumbs, navigation tabs, and icons from 'CMSA Rack Storage' screen are appropriately positioned or not. 9. Check to see if the 'CMSA Rack Storage' screen is compatible with different screen resolutions. |