0% found this document useful (0 votes)
30 views10 pages

Defi Solutions QA Test Summary

Uploaded by

kalyanA a
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
30 views10 pages

Defi Solutions QA Test Summary

Uploaded by

kalyanA a
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

Defi

solutions
solution’s
QA Test
report
Project Name & details

Project =
Project details =
Defi Dealer information is managed
in Originations, Servicing and
Solutions Accounting Systems, where
the dealers are created /
updated in Originations and
passed to Servicing which than
updates Accounting thru a series
of Batch and API Processes.​​The
dealer data originates from the
clients via nightly file-based
integrations and / or UI Manual
entry into Originations
or Servicing.​
Purpose

• Identifying bugs, ensuring quality


, improve user experience for
Defi solutions and provide a
seamless solution for Defi
solution end users.
Test objective and
scope
Test objective : to deliver a defect free Defi solution
• Functional testing (smoke , regression , sanity ,
exploratory testing).

In-scope : Modules mentioned below.


Dealer Dashboard , Dealer Library , Dealer Reports,
Dealer Configuration , Dealer Features.
Test Environment

• Pre- staging environment.


• Test Execution
please find the .xl report below
UAT Test
summary.
Microsoft Excel
Worksheet

Total test
cases
Total test executed Passed Failed
cases
executed SIT UAT
250 250 218 32
(Critical
and E2E Total test Critical Mediu Low
test cases (P0) m (P1) (P2)
cases
380 380 only) 250 2 17 13
Test results Reports

• UAT Test results Reports

32
UAT Bugs category

Low 13

Medium 17
250

218
Critical 2

Total test cases 250

Total test cases Pass Failed 0 50 100 150 200 250 300
Exit Criteria. ...
•All test cases passed .
•No critical issues identified and
•No slippage ratio.
•All critical and high-priority defects must be
resolved , and their re- test results should
be passed.
•All end to end test cases are working
shamelessly.
•SIT , UAT signoffs should provided
•Final project review should be done with all
stake holders.
Test metrices used
• Test plan
• RTM.
• Test execution report.
• Daily status report.
• weekly status report.
• Defect status report
Thank You

You might also like