DESCRIPTION stringclasses 93
values | DOCUMENT stringlengths 48 1.83k | RESULT stringlengths 338 13.5k |
|---|---|---|
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test casetype(Positive/Negative) and Expected Result. | The portal must offer user registration and login functionality. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "User Authentication",
"Sub-Module": "User Registration",
"Functionality": "Registration Page",
"Test case description": "To check user is able to enter valid user details and clic... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Users should be able to reset their passwords through a secure account recovery process. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "User Authentication",
"Sub-Module": "Reset Password",
"Functionality": "Reset Password field",
"Test case description": "To check that user is able to initiate a password reset b... |
Write test cases in the domain sub-domain application module sub-module scenario format for the specified requirements. Operational The test case description includes the test case type (positive/negative) and the expected outcome. | User authentication should incorporate industry-standard security practices to protect user data. | {
"Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "User Authentication",
"Sub-Module": "User Registration",
"Functionality": "Password Complexity",
"Test case description": "To verify that the password meets complexity requirements (minimum length,... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result. | Upon successful login, users should be directed to a personalized dashboard. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Dashboard_Portal",
"Sub-Module": "Personalized Dashboard",
"Functionality": "Dashboard_page",
"Test case description": "To check user is able to view the dashboard with all servic... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | The dashboard should present an overview of services or applications relevant to the user's roles. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Dashboard_Portal",
"Sub-Module": "Personalized Dashboard",
"Functionality": "Dashboard_page",
"Test case description": "\"To check User clicks on \"\"Reset Layout\"\" button\"",
... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Users must be able to customize their dashboard layout and select preferred widgets. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Dashboard_Portal",
"Sub-Module": "Personalized Dashboard",
"Functionality": "Dashboard_page",
"Test case description": "To check user is able to view the encrypted mobile number i... |
Write test cases in the domain sub-domain application module sub-module scenario format for the specified requirements. Operational The test case description includes the test case type (positive/negative) and the expected outcome. | Users should have the ability to report incidents related to different categories of services or applications. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Incident Reporting Facility",
"Sub-Module": "Reporting",
"Functionality": "Incident report page",
"Test case description": "To check user is able to report incidents related to d... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | The incident reporting form should capture relevant details, including incident type severity description and any associated files. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Incident Reporting Facility",
"Sub-Module": "Reporting",
"Functionality": "Incident report page",
"Test case description": "To check user is able to Attach files while submitting... |
Write test cases in the domain sub-domain application module sub-module scenario format for the specified requirements. Operational The test case description includes the test case type (positive/negative) and the expected outcome. | Incident reporters should receive confirmation emails upon submitting reports. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Incident Reporting Facility",
"Sub-Module": "Email Confirmation",
"Functionality": "Incident report page",
"Test case description": "To check user is is able to submit an incident... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Administrators should be able to assign incidents to specific teams or individuals for resolution. |
"Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Incident Reporting Facility",
"Sub-Module": "Assignment",
"Functionality": "Incident report page",
"Test case description": "To check user is able to Log in as an admin, ... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Admin users should have the ability to define and manage categories for services or applications. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Category Management",
"Sub-Module": "Creation",
"Functionality": "Category_ Creation",
"Test case description": "To check if user Log in as an admin, create a category with a name... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | Categories should be customizable, allowing administrators to create edit and delete categories as needed | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Category Management",
"Sub-Module": "Editing",
"Functionality": "Category_ Editing",
"Test case description": "To check if user Log in as an admin, edit an existing category",
... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Incident status and progress should be tracked and displayed on the dashboard. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Incident Tracking and Resolution",
"Sub-Module": "Status Tracking",
"Functionality": "Incident Tracking _ status",
"Test case description": "To check user is Log in as a user and... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | Assigned teams or individuals should have access to incident details and the ability to update the incident's status and resolution steps. |
"Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Incident Tracking and Resolution",
"Sub-Module": "Status Tracking",
"Functionality": "Incident Tracking _ status",
"Test case description": "To check user is Log in as a... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Assigned teams or individuals should have access to incident details and the ability to update the incident's status and resolution steps. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Incident Tracking and Resolution",
"Sub-Module": "User_Notification",
"Functionality": "Incident Tracking _ status",
"Test case description": "To check user is Submit an incident,... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Users should receive notifications when incidents are resolved or require their input. | "Domain": "Banking",
"Sub-Domain": "Project Management",
"Application": "Portal",
"Module": "Incident Tracking and Resolution",
"Sub-Module": "User_Notification",
"Functionality": "Incident Tracking _ status",
"Test case description": "To check user is Submit an incident,... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | The business team and members will be set up at Org Hierarchy Master. | "Module": "Business Set Up and Structure",
"Sub-Module": "Business Roles and Levels",
"Scenario Description": "To verify the Business Set up and Structure",
"Category": "Functional",
"Test Case Description": "To Check if Sales(RM) is assigned Level 1",
"Test Category": "Positiv... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | In teams logic for allocation of task to each member of the team is also setup
Members and Teams setup is core product functionality available on org hierarchy master. Sample screens are attached below to show case the setup of teams and members." | "Module": "Business Set Up and Structure",
"Sub-Module": "Business Roles and Levels",
"Scenario Description": "To verify the Business Set up and Structure",
"Category": "Functional",
"Test Case Description": "To Check if Operations user has Maker and Checker",
"Test Category": "P... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | Verify that the Product Group has the expected options: New Car, Used Car, Demo Car, Deemed New Car. | "Module": "Product Details",
"Sub-Module": "Product Group",
"Scenario Description": "To verify the Product Details",
"Category": "Functional",
"Test Case Description": "To Check that product group has following Options\n1.New Car\n2.Used Car\n3.Demo Car\n4.Deemed new car",
"Test... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Check if the Product Variant is set to Demo Car. | "Module": "Product Details",
"Sub-Module": "Product Group",
"Scenario Description": "To verify the Product Details",
"Category": "Functional",
"Test Case Description": "To Check if Product Varient is Demo Car",
"Test Category": "Positive",
"Expected Result": "Product Va... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Ensure that parameters for configuration are available in the Product Structure and Verify that the Product Structure tab saves successfully. | "Module": "Product Structure",
"Sub-Module": "Product Structure",
"Scenario Description": "To verify the Product Structure",
"Category": "Functional",
"Test Case Description": "To Check if Parameters values are available for Configuration",
"Test Category": "Positive",
... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Validate that the Small Cars category contains all expected options, including models like Datsun Go, Hyundai EON, Maruti Alto, etc. , Check that the Hatchback Cars category contains all specified options such as Hyundai Grand I10, Maruti Swift, etc.,Ensure that the Sedan Cars category lists all required models includi... |
"Module": "Product Structure",
"Sub-Module": "Small Cars",
"Scenario Description": "To verify the Product Category \u2013 Small Cars",
"Category": "Functional",
"Test Case Description": "To Check if Small Cars Contains following Options\n1.Datsun Go\n2.Hyundai EON\n3.Hyundai Get... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | Confirm that the Premium category includes all specified luxury options and alidate the MUV Cars category contains expected models like Mahindra Bolero, Tata Safari, etc.Ensure that the Premium SUV category includes all expected options.Verify that the MUV Premium category contains all listed luxury options from variou... | "Module": "Product Structure",
"Sub-Module": "Premium",
"Scenario Description": "To verify the Product Category \u2013 Premium",
"Category": "Functional",
"Test Case Description": "To Check if Premium Contains following Options\n\nHonda City\nCitreon C3\nHonda Civic\nHyundai Alcazar\nHy... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Validation of Charges Generation: Verify that the correct LOS-based charges are generated for a particular product.Verify that the correct LOS-based charges are generated for insurance.Ensure that the following recovery methods are displayed for charge recovery:
Collect Separately
Deduct from disbursement
| "Module": "Product Fees",
"Sub-Module": "Charges",
"Scenario Description": "To check the Product Fees",
"Category": "Functional",
"Test Case Description": "To Check whether correct LOS based Charges is getting generated or not for Particular Product",
"Test Category": "Positive"... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Validation of Product Pricing Parameters:Check that the maximum tenure for an auto loan is fixed at 7 years.Confirm that pricing is initiated for every application.
Validate that the interest rate (RAAC rate) for Car Category A1 is displayed as 9.30%.
Validate that the interest rate (RAAC rate) for Car Category A1/A3 i... | "Module": "Product Fees",
"Sub-Module": "Product Fees",
"Scenario Description": "To check the Product Pricing",
"Category": "Functional",
"Test Case Description": "To Check whether Maximum tenure for Auto loan is fixed as 7 years or not",
"Test Category": "Positive",
"Ex... |
Create test cases using the guidelines, following the format of Domain Sub-Domain Application Module Sub-Module Scenarios. Ability to Function Test case description; Test case type (positive/negative); and Expected Outcome. | Validation of Processing Fees:Verify that the processing fee for Car Category A1 is set at 3000.Verify that the processing fee for Car Category A2/A3 is set at 3500.Verify that the processing fee for Car Category A4/A5 is set at 4500.Verify that the processing fee for Car Category A6/A7 is set at 5500.Check that the pr... | "Module": "Product Pricing",
"Sub-Module": "Product Pricing",
"Scenario Description": "To check the Product Pricing",
"Category": "Functional",
"Test Case Description": "To Check Processing Fee is 3000 for car Category A1",
"Test Category": "Positive",
"Expected Result... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Validation of Foreclosure Charges: Ensure that foreclosure charges are set at 5% + GST for loan tenure less than 24 months.Ensure that foreclosure charges are set at 3% + GST for loan tenure greater than 24 months. | "Module": "Product Pricing",
"Sub-Module": "Product Pricing",
"Scenario Description": "To check the Product Pricing",
"Category": "Functional",
"Test Case Description": "To check that Foreclosure Charges is 5%+GST\n for loan tenure less than 24 months",
"Test Category": "Posi... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | The user will have to select the location and the portfolio based on which the Quick data entry(QDE) data entry form will be displayed.The user must select the portfolio as EL on the basis which the QDE data entry form will be displayed. | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To Verify Initiation of Quick Data Entry",
"Category": "Functional",
"Test Case Description": "To check user is able to select the location an portfolio based on which the QDE data entry from is display",
"Test Catego... |
Create test cases using the guidelines, following the format of Domain Sub-Domain Application Module Sub-Module Scenarios. Ability to Function Test case description; Test case type (positive/negative); and Expected Outcome. | Verify Portfolio Dropdown Visibility Based on Location Selection. | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To Verify Initiation of Quick Data Entry",
"Category": "Functional",
"Test Case Description": "To check based on the location selected the portfolio Dropdown is showing",
"Test Category": "Positive",
"Expected... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | RM User Login with Valid Username and Password.
Preconditions:
The application is accessible.
The RM user has valid login credentials (username and password).RM User Login with Invalid Username and Password. .RM User Entering Applicant and Co-Applicant Details | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To Verify Initiation of Quick Data Entry",
"Category": "Functional",
"Test Case Description": "To Check whether RM user is able to login with valid username and password.",
"Test Category": "Positive",
... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Verify User Interaction in Quick Data Entry,To check whether user is able to select the location and Port. | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To Verify Initiation of Quick Data Entry",
"Category": "Functional",
"Test Case Description": "To check whether user is able to click on application entry under operation tab",
"Test Category": "Positive",
... |
Create test cases using the guidelines, following the format of Domain Sub-Domain Application Module Sub-Module Scenarios. Ability to Function Test case description; Test case type (positive/negative); and Expected Outcome. | Validate Applicant and Co-Applicant Details Entry: To check whether RM user is able to enter all applicant and co-applicant details., To check whether RM user has not entered mandatory fields. | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To Verify Initiation of Quick Data Entry",
"Category": "Functional",
"Test Case Description": "To Check whether RM user is able to enter all applicant and co-applicant details",
"Test Category": "Positive",
... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Email Notification Functionality; Email notification for submitting valid details.To check whether user receives the Email in valid format. | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To Verify Initiation of Quick Data Entry",
"Category": "Functional",
"Test Case Description": "To check whether user is able to receive the Email notification for submitting valid details",
"Test Category": "Positive... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | SMS Notification Functionality: To check whether user is able to receive the SMS notification for submitting valid details.To check whether user receives the SMS in valid format. | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To Verify Initiation of Quick Data Entry",
"Category": "Functional",
"Test Case Description": "To check whether user is able to receive the SMS notification for submitting valid details",
"Test Category": "Posit... |
Create test cases in the Domain Sub-Domain Application Module Sub-Module Scenarios format for the specified requirements. Performance Test case description, Test case type (positive/negative), and Expected Outcome. | Verify Sourcing Details at Application Level: sourcing channel is selected in source channel pop search. To check DSA/Connector/BC/SP Name in pop search is selecting data & user is able to fetch the name.To check DSA/Connector/BC/SP Name in pop search field is conditional.to check in RO/CE/CM/ASO Employee Name pop sear... | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To verify the Sourcing Details \u2013 Application Level in QDE Stage",
"Category": "Functional",
"Test Case Description": "To check sourcing channel is selecting in source channel pop search",
"Test Category": "Posit... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Validate Application Details Input: To check Application Form no. Field allows only Numeric Value in Application Details page. To check Application Form no. Field allows AlphaNumeric Value in Application Details page. check whether user is able to select application receive date after clicking on the date picker. if ... | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To verify the Sourcing Details \u2013 Application Level in QDE Stage",
"Category": "Functional",
"Test Case Description": "To check whether user is able to edit\nZonal office field",
"Test Category": "Negative",
... |
Create test cases in the Domain Sub-Domain Application Module Sub-Module Scenarios format for the specified requirements. Performance Test case description, Test case type (positive/negative), and Expected Outcome. | Validate Business Segment and Transaction Type SelectioU+006e.: To check Business Segment Dropdown field data is displayed & this field is mandatory.To check whether user is able to click on Type of transaction. user is able to view options after clicking on Type of Transaction drop down (Balance Transfer, Fresh, Top ... | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To verify the Application Details in QDE Stage",
"Category": "Functional",
"Test Case Description": "To check Business Segment Dropdown field data is display & this field is mandatory",
"Test Category": "Positive",
... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Verify Customer ID Search Functionality: check whether RM user is able to search existing customer id after clicking on Check box in Individual Applicant Details page.To check in Existing Customer Search pop search field if the list of all existing users is showing. | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To verify the Application Details in QDE Stage",
"Category": "Functional",
"Test Case Description": "To Check whether RM user is able to search existing customer id after\nClicking on Check box in Individual Applicant Details... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | Validate Application Type Selection for Individual and Non-Individual: user is able to view options after clicking on Application Type drop down (Individual, Non-Individual). user is able to view options after clicking Individual Customer profile pop search (Salaried, Self-employed Non Professional, Self-employed Prof... |
"Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To verify the Individual Application Details in QDE stage",
"Category": "Functional",
"Test Case Description": "To check user is able to view below\nOption after clicking on Application Type drop down -Individual\n-N... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Verify Autopopulate Functionality and Title Selection: To check if data in Tier is autopopulated.To check User is able to select Title drop down.To check if user does not select Title drop down (Negative Test Case).
| "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To verify the Individual Application Details in QDE stage",
"Category": "Functional",
"Test Case Description": "To check if data in Tier is autopopulate ",
"Test Category": "Positive",
"Expected Result": "Data... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | Validate TITLE Dropdown and Others Option: TITLE dropdown in Individual Applicant Details page displays optionsTo check if user selects Others then Others text box is able to enter data. in Others field text Box user is not able to enter data (Negative Test Case). |
"Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To verify the Individual Application Details in QDE stage",
"Category": "Functional",
"Test Case Description": "To check TITLE dropdown in Individual Applicant Details page display below options Mr.\nMs.\nMrs.\nDr.\n... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Test Scenario: Validate Name Fields Entry and Validation: to check User is able to enter data in First Name Field First name Field is mandatory; if user does not enter data, an error message is shown in First Name fieldU+002e, user is not able to enter data in First Name field. User is able to enter data in Middle Name... | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To verify the Individual Application Details in QDE stage",
"Category": "Functional",
"Test Case Description": "To check User is able to entering the data in First Name Field",
"Test Category": "Positive",
"E... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | Verify that future dates cannot be selected for the Date of Incorporation/Commencement of business field.Check that the user can successfully enter a PAN No. in the PAN No. text box field.Verify that the user is unable to enter PAN No. in the PAN No. text box field under certain conditions (e.g., input restrictions).Ch... | "Module": "QDE",
"Sub-Module": "QDE",
"Scenario Description": "To verify Non Individual Applicant Details in QDE Stage",
"Category": "Functional",
"Test Case Description": "To check Date of Incorporation/Commencement of business field future date is not selecting",
"Test Catego... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Dedupe check will be configured as a system activity in the workflow.This activity will show the potential matches of the applicants with internal and other databases based on the dedupe rules defined. | "Module": "Dedupe Check",
"Sub-Module": "Dedupe Check",
"Scenario Description": "To chcek the Dedupe Check flow",
"Category": "Functional",
"Test Case Description": "To check dedupe activity is showing the potential matches of the applicants with internal and other databases based on the... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | Dedupe Check flow, ensuring that the system correctly identifies exact matches for Driving License and PAN, while also verifying that it properly handles non-exact matches by preventing deduplication. |
"Module": "Dedupe Check",
"Sub-Module": "Dedupe Check",
"Scenario Description": "To chcek the Dedupe Check flow",
"Category": "Functional",
"Test Case Description": "To check dedupe perform with exact match of Driving License.",
"Test Category": "Positive",
"Expe... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | the Dedupe Check flow. Dedupe Check flow, focuses on the exact matches required for the First name + Last name + DOB rule, Voter ID, and the BOD rule. |
"Module": "Dedupe Check",
"Sub-Module": "Dedupe Check",
"Scenario Description": "To chcek the Dedupe Check flow",
"Category": "Functional",
"Test Case Description": "To check dedupe perform with exact match of First name+Last name+DOB rule.",
"Test Category": "Positive",... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | verifying the deduplication review process and user interactions based on whether deduplication matches are found. | "Module": "Dedupe Check",
"Sub-Module": "Dedupe Check",
"Scenario Description": "To chcek the Dedupe Check flow",
"Category": "Functional",
"Test Case Description": "To check user is able to go for dedupe review activity, if dedupe matches are found.",
"Test Category": "Positive"... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | Dedupe Review will be configured as a user activity in the workflow.
Business Rules/applicability
Activity will only be initiated if any dedupe match is found.
Pre-Condition
Dedupe matches are found in the system
Allocation / Primary Users
Credit
Primary flow of events
Dedupe Review activity will be initiated as a user... | {
"Module": "Dedupe Check",
"Sub-Module": "Dedupe Review",
"Scenario Description": "To check the initiation of Dedupe Review activity when dedupe matches are found.",
"Category": "Functional",
"Test Case Description": "Verify that the Dedupe Review activity is initiated in the workflow when dedupe m... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | If there is no match found in LOS, new customer ID will be generated by the system.
If there are one or more matches found in LOS, the user will have an option to confirm any one match. Once a match is confirmed and activity is submitted the generated customer ID for this application would be replaced with old customer... | {
"Module": "Customer Management",
"Sub-Module": "Customer ID Generation",
"Scenario Description": "To verify new customer ID generation when no match is found in LOS.",
"Category": "Functional",
"Test Case Description": "Check that the system generates a new customer ID when there are no matches fo... |
Create test cases using the guidelines, following the format of Domain Sub-Domain Application Module Sub-Module Scenarios. Ability to Function Test case description; Test case type (positive/negative); and Expected Outcome. | CBS Dedupe
If there is no match with CBS, Customer registration will happen post sanction of the application where a new customer ID will be assigned to the customer and details will be passed to CBS.
If there are one or more matches found in CBS, the user will have option to confirm any one match. Once a match is conf... | {
"Module": "Customer Management",
"Sub-Module": "CBS Dedupe",
"Scenario Description": "To verify customer registration when no match is found in CBS.",
"Category": "Functional",
"Test Case Description": "Check that customer registration occurs post-sanction with a new customer ID assigned when no m... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Post Conditions
Activity is submitted successfully.
Exceptional Flow
N/A
Queries / clarifications related to system mapping
N/A
Customization | {
"Module": "Customer Management",
"Sub-Module": "CBS Dedupe",
"Scenario Description": "To verify successful submission of the activity.",
"Category": "Functional",
"Test Case Description": "Check that the activity is submitted successfully after all required steps are completed.",
"Test Categor... |
Create test cases using the guidelines, following the format of Domain Sub-Domain Application Module Sub-Module Scenarios. Ability to Function Test case description; Test case type (positive/negative); and Expected Outcome. | This will be initiated as a system activity in the workflow. The system will check the eligibility of applicants based on the parameters configured in the eligibility rules.
Eligibility rules are configured in Eligibility Master of the LOS system. Based upon the rules configured for eligibility, system will display the... | {
"Module": "Eligibility Check",
"Sub-Module": "Eligibility Assessment",
"Scenario Description": "To verify the initiation of eligibility check as a system activity.",
"Category": "Functional",
"Test Case Description": "Ensure that the eligibility check is initiated as a system activity within the w... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Business Rules/applicability
Various business rules would be triggered while calculation of eligibility configured at various masters
Pre-Condition
Eligibility rules must be defined in the Masters
Allocation / Primary Users
NA
Primary flow of events
The eligibility of the applicant will be calculated at this stage. Bas... | {
"Module": "Eligibility Check",
"Sub-Module": "Eligibility Rules Evaluation",
"Scenario Description": "To verify that various business rules are triggered during eligibility calculation.",
"Category": "Functional",
"Test Case Description": "Ensure that the system triggers the appropriate business r... |
Create test cases using the guidelines, following the format of Domain Sub-Domain Application Module Sub-Module Scenarios. Ability to Function Test case description; Test case type (positive/negative); and Expected Outcome. | Total Income Computation
Based on the different income types, the LOS system will first calculate the applicant-wise income and after that the total income for the loan application will be computed and the same will be displayed on the ‘Income Rule Applicability’ screen.
Income for calculating the eligibility will be t... | {
"Module": "Eligibility Check",
"Sub-Module": "Total Income Computation",
"Scenario Description": "To verify the calculation of applicant-wise income based on different income types.",
"Category": "Functional",
"Test Case Description": "Ensure that the LOS system correctly calculates the income for... |
Write test cases for the given requirements in the format of Domain Sub-Domain Application Module Sub-Module Scenarios Functionality Test case description Test case type(Positive/Negative) and Expected Result | Total Obligation Computation
LOS system will receive the obligations of the customer from CIBIL and the same will be used for obligation computation. All the obligations for which the option for ‘Financial Applicant’ is selected as ‘Yes’ will be used for the obligation computation. | {
"Module": "Eligibility Check",
"Sub-Module": "Total Obligation Computation",
"Scenario Description": "To verify the retrieval of customer obligations from CIBIL.",
"Category": "Functional",
"Test Case Description": "Ensure that the LOS system accurately receives the obligations of the customer fro... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | FOIR Master
Fixed obligation to income ratio will be defined in the FOIR Master. System will check the policy FOIR defined in the master and based on which FOIR based income will be calculated. | {
"Module": "Eligibility Check",
"Sub-Module": "FOIR Master",
"Scenario Description": "To verify that the FOIR is correctly defined in the FOIR Master.",
"Category": "Functional",
"Test Case Description": "Ensure that the fixed obligation to income ratio is accurately defined and accessible in the F... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | Multiplier will be defined in the multiplier Master. The system will display the policy multiplier based on which eligible EMI will be calculated. | {
"Module": "Eligibility Check",
"Sub-Module": "Multiplier Master",
"Scenario Description": "To verify that the multiplier is correctly defined in the Multiplier Master.",
"Category": "Functional",
"Test Case Description": "Ensure that the policy multiplier is accurately defined and accessible in th... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified requirements. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | Margin will be defined by the margin master. The system will display the policy margin percentage based on which income will be calculated. | {
"Module": "Eligibility Check",
"Sub-Module": "Margin Master",
"Scenario Description": "To verify that the margin percentage is correctly defined in the Margin Master.",
"Category": "Functional",
"Test Case Description": "Ensure that the policy margin percentage is accurately defined and accessible... |
Create test cases in the Domain Sub-Domain Application Module Sub-Module Scenarios format for the specified criteria. Performance Test case description, Test case type (positive/negative), and Expected Outcome. | Maximum Loan Amount Capping
The system will check the maximum loan amount that can be offered to the customer based on the maximum amount configured at the product master.
Maximum loan amount based on the collateral value – Not clear on this part as this not how EL eligibility works -
The system will check the maximu... | {
"Module": "Eligibility Check",
"Sub-Module": "Maximum Loan Amount Capping",
"Scenario Description": "To verify that the system checks the maximum loan amount based on the configured product master.",
"Category": "Functional",
"Test Case Description": "Ensure that the maximum loan amount displayed ... |
Create test cases in the Domain Sub-Domain Application Module Sub-Module Scenarios format for the specified criteria. Performance Test case description, Test case type (positive/negative), and Expected Outcome. | This will be system activity where all verifications and technical valuation will be initiated.
Business Rules/Applicability
System will initiate verifications when this activity is triggered. Once the verifications and valuation are initiated, it will get auto allocated to the required role users.
Notification would b... | {
"Module": "Verification and Valuation",
"Sub-Module": "System Activity",
"Scenario Description": "To verify that the system initiates verifications and technical valuation correctly when the activity is triggered.",
"Category": "Functional",
"Test Case Description": "Ensure that the system trigger... |
Create test cases in the Domain Sub-Domain Application Module Sub-Module Scenarios format for the specified criteria. Performance Test case description, Test case type (positive/negative), and Expected Outcome. | This will be initiated as a user activity in the workflow.
Business Rules/applicability
The verification for the applicant, co applicant and guarantor will be separately triggered in the system as different activities.- To be triggered only once if the address’s are the same
Residence Verification will be initiated fo... | {
"Module": "Verification",
"Sub-Module": "Applicant and Co-applicant Verification",
"Scenario Description": "To verify that the system triggers separate verifications for the applicant, co-applicant, and guarantor.",
"Category": "Functional",
"Test Case Description": "Ensure that the system trigger... |
Write test cases in the domain sub-domain application module sub-module scenario format for the specified requirements. Operational The test case description includes the test case type (positive/negative) and the expected outcome. | Activity must be initiated and assigned to required role user.
Allocation / Primary Users
External Verifier
Primary flow of events
This activity will be assigned to the external verifier user. The user would login to the Ebix LOS system and view all the cases assigned to him/her. The assigned cases will be available in... | {
"Module": "Residence Verification",
"Sub-Module": "Task Assignment",
"Scenario Description": "To ensure that the verification activity is assigned to the external verifier upon initiation.",
"Category": "Functional",
"Test Case Description": "Verify that the system assigns the verification activit... |
Write test cases in the domain sub-domain application module sub-module scenario format for the specified requirements. Operational The test case description includes the test case type (positive/negative) and the expected outcome. | The user would login to the Ebix LOS system and view all the cases assigned to him/her. The assigned cases will be available in the task list (worklist) of the user.
At this activity, the user will verify the residence address of all applicants in the application (Borrower Co-borrower & guarantor). For each applicant i... | {
"Module": "Residence Verification",
"Sub-Module": "Task List Viewing",
"Scenario Description": "To ensure the user can view all assigned cases in their task list after logging in.",
"Category": "Functional",
"Test Case Description": "Verify that the user can successfully log in to the Ebix LOS sys... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified criteria. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | The screen layout will be divided into two parts:
• Source – that displays the data entered in the application and will be non-editable.
• Target – area where the verifier can input the verification details.
The user will then enter all the mandatory information required to complete the activity and the final s... | {
"Module": "Residence Verification",
"Sub-Module": "Screen Layout",
"Scenario Description": "To verify that the screen layout is divided into 'Source' and 'Target' sections as expected.",
"Category": "Functional",
"Test Case Description": "Verify that the residence verification screen displays a 'S... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified criteria. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | If there is any discrepancy or another verification is to be triggered for any applicant, then there will be a re-initiate option available in LOS where the credit user can manually re-initiate the residence verification.-
Post Conditions
Activity is submitted successfully. | {
"Module": "Residence Verification",
"Sub-Module": "Re-Initiation of Verification",
"Scenario Description": "To verify that the credit user can manually re-initiate residence verification if there is any discrepancy.",
"Category": "Functional",
"Test Case Description": "Ensure that the system provi... |
Prepare test cases using Domain Sub-Domain Application Module Sub-Module Scenarios for the specified criteria. Ability to function A description of the test case, together with its kind (positive or negative) and expected outcome. | "Functionality/Module": "Generate Document",
"Scenario Description": "To verify the Document list for KYC of Applicant and Co-applicant in Post QDE submission Stage",
"Category": "Functional" | {
"Module": "Generate Document",
"Sub-Module": "KYC Document Verification",
"Scenario Description": "To verify that the document list for KYC of both Applicant and Co-applicant is correctly displayed at the Post QDE submission stage.",
"Category": "Functional",
"Test Case Description": "Ensure that ... |
End of preview. Expand in Data Studio
No dataset card yet
- Downloads last month
- 2