Case Study

Software Quality Assurance to Facilitate Seamless E2E Lending

Industries: FinTech

About Customer

The client is a cloud-based lending platform and online marketplace that allows consumers to apply for and receive private student loans, student loan refinancing and home improvement loans from their local credit unions and community banks. Their cloud-based tools and infrastructure enable the nation’s 13,000+ community financial institutions to enter online lending and offer loans for various asset classes.

Business Needs and Challenges

Setting up an automated online system to provide speedy error-prone E2E lending process with optimal cost. To achieve this objective they wanted to build a unified lending platform irrespective of the nature of products and gradually replace their legacy systems. Here are a few major challenges that needed to be handled to serve the purpose:

  • Large-scale integration
  • Data confidentiality
  • Security threats and breaches
  • Large-scale storage systems
  • Disaster and risk threats and management
  • Record keeping
  • Protection of personal data
  • Real-time processing
  • Troubleshooting
  • Efficient transactions
  • Responsiveness
  • Accessibility
  • Seamless User Experience

Impressico’s Approach

With such a rapidly changing environment where we have both legacy and new systems in addition to frequent code deployments. As a QA and testing service provider we were accountable for both the systems (Legacy Vs New) at the same time.

We could not go ahead with conventional QA processes, so we  adopted some new testing approaches on top of just testing. For both Manual and Automation Testing, we followed the unified approaches.

Testing Nature

Shift Left Testing Approach

Started testing earlier in the software development process so that we can build the system hand in hand with the developers. We collaborated with the developing team to incorporate them into the testing cycle. This approach facilitated code review quality checks during the software development process.

Test Case Design

Modular Test Design for both Manual and Automation Testing

Started writing a function-based method of test design, which allowed us to categorize functionalities to be tested into reusable components. This approach helped us to reduce the redundancy and confusion often seen in conventional test cases.

Automation Testing

Three Layer Automation Architecture with Gherkin Syntax

We built the test case in BDD format which increased and improved collaboration. It enabled the whole scrum team getting involved in the project to easily engage with the product development cycle.

CI/CD Deployment Pipeline integration with Automation Test

Set up an effective deployment pipeline in CI/CD. Those jobs are utilised for incremental builds testing that is available on the server. This approach significantly reduced the overall Turnaround time (TAT) as compared to manual testing. 

Reporting for both Manual and Automation Testing

Started publishing detailed test reports with all required artefacts like environmental details, test data, screenshots, screencasts etc.

QA-Testing1

Benefits

Business

  • Measurably improved the quality of software by adding independence in the testing process.
  • Quantified metrics can detect software defects early in the development cycle.
  • Software Development moves towards leveraging unified automation tools for any kind of testing wherever possible.
  • Continuous integration to identify defects early in the development lifecycle.

End-User
The client has two types of end-users, and both can reap the benefits as mentioned below:

  • Borrowers
  • Achieve their financial goals and save money with lower interest rates from financial institutions
  • Lenders
  • Benefit from a superior infrastructure that provides full-scale marketing, operations and technical support