TEST CLOSURE REPORT Porter Test Closure Report

TEST CLOSURE DOCUMENT

11/04/2023

1
 TEST CLOSURE REPORT Porter Test Closure Report

CONTENTS
1. PURPOSE OF THE DOCUMENT................................................................................................................................3
2. APPLICATION OVERVIEW........................................................................................................................................3
3. TESTING SCOPE.......................................................................................................................................................3
3.1 IN-SCOPE.........................................................................................................................................................3
3.2 OUT OF SCOPE................................................................................................................................................3
3.3 NOT TESTED ITEMS.........................................................................................................................................3
4. METRICS.................................................................................................................................................................. 3
5. TYPES OF TESTING PERFORMED.............................................................................................................................4
6. TEST ENVIRONMENT & TOOLS...............................................................................................................................4
7. LESSONS LEARNED..................................................................................................................................................4
8. RECOMMENDATIONS.............................................................................................................................................4
9. ANNEXURE..............................................................................................................................................................4

2
 TEST CLOSURE REPORT Porter Test Closure Report

1.PURPOSE OF THE DOCUMENT

Performed UAT LOS and LMS Round 1 testing in knight fintech application .This document provided LOS and LMS
testing overview for the knight fintech application.

2.APPLICATION OVERVIEW
 Knight Fintech is a web-based application used as a tool for the lending business of the Capri Co-lending for
UBI ,SBI and UCO bank.

3.TESTING SCOPE

3.1 IN-SCOPE:

Application Product Functionality

LOS • UBI-MSME • Push to bank

• SBI-MSME • Bucket movement
• UCO-HL • Pool approval
• Pool assignment
• Pool disbursement
• Download button functionality
• Pool back functionality
• Query bucket functionality
3.2 • Reject Bucket functionality OUT OF
• Upload query file functionality SCOPE
• Product
 Bank user ID for testing flow was and policy of the UCO Home Loan product
not tested.
 Automation Testing • Product and policy of the UBI MSME product
 Performance Testing • Product and policy of the SBI MSME product
 Production Environment testing
LMS • UBI-MSME • Customer Management
 Unit Testing
• Statement of Accounts
 Security/ VAPT Testing.
• Repayment Schedule
 Release Management, Defect RCA and Resolution
• Application Details
 Environment maintenance, alteration
• OTC Entry
 Standalone Sanity testing, Partner system & interface testing
• DRE
• Part-Prepayment
• Special Transactions
a. Reschedule
b. Interest Change
c. EMI Change
d. Tenure Change
e. Due Date Change
• Daily and Monthly Activities (EOD and BOD)
• Mandate Details
• PDC/SPDC
• Maker Checker Functionality
• Bulk Upload

3
 TEST CLOSURE REPORT Porter Test Closure Report

3.3 NOT TESTED ITEMS

Below Test cases are blocked as per below mentioned reasons same mail was attached bottom of the
document.
 Due to LOS data unavailability below functionality unable to test in UAT ( UAT-1- 40)

 Modules are not delivered in UAT for testing (LOS-167,LMS:725)

 Due to Open Defect (LOS-79,LMS -144 )

4.METRICS

a) Module wise number of defects.

LOS:

In Grand
Status Reopen To-Do
Progress Total

Critical 3 14 17

High 6 8 29 43

Low 1 1

Medium 1 6 11 18

Grand Total 7 17 55 79

4
 TEST CLOSURE REPORT Porter Test Closure Report
LMS:
In Grand
Status Fixed Reopen To-Do
Progress Total

Critical 7 5 10 18 40

High 9 5 19 30 63

Hold 1 3 5 9

Low 1 1 5 7

Medium 2 3 9 11 25

Grand Total 19 15 41 69 144

b) Number of Defects identified with the severity.

LOS

Clarification Closed Discarded In Progress

Reopen To-Do Grand Total

LMS

Clarification Closed Discarded Fixed In Progress

Release Reopen To-Do Grand Total

5
 TEST CLOSURE REPORT Porter Test Closure Report

5.TYPES OF TESTING PERFORMED

 Performed only Round 1 UAT testing for LOS and LMS module

6.TEST ENVIRONMENT & TOOLS

 Mention the details of the environments used for the testing purposes with the details such as:

Application URL http://capri-los.knightfintech.com/

http://capri-clp.knightfintech.com/
http://capri-
cas.knightfintech.com/
Bug Tracking Knightfintech Proof hub
Tool

7.LESSONS LEARNT AND RECOMMENDATIONS

SR NO ISSUES FACED SOLUTIONS

1 UAT Delivery Not on Time Required UAT Delivery on Time

2 Defined defect SLA was not followed Defined defect SLA should be followed

3 Unit Testing screen shot not provided by Unit Testing screen shot should be shared with
development Team Testing Team

4 Some of the Walk through Document not shared All walk through Document should be shared with
with Testing team Testing team

5 Defect/deployment Release note was not shared Defect Released note should be shared after every
after every release release

6 After every release new defect was occur and it After every release new defect was occur and it was
was impacted on Working functionality as impacted on Working functionality as well
well.environment was not stable.

7 For manual EOD process every time development For manual EOD process every time data is
team truncating the data hence. Again testing truncating and hence. Again testing team have to
team have to create new Data created new Data

8 Deployment started in working hours due that Deployment will start in non working hours
testing is on hold

9 Development team is doing application changes Development team should inform the changes to
in the system without informing to testing team testing team

8.OVERALL TEST STATUS AND SIGN OFF

 Overall Test status, conditional sign off
 Risks and Assumptions mail

9.ANNEXURES
6