To test a platform change or a new site, first clear your cookies, or alternatively open a new incognito/private browsing window. Cookies are used to store some application data, so it’s important to start with a clean slate during each test.
Navigate to your test site, and start an application via the start application button. Do not start and test the application in the lender Hub as this is not the environment a borrower experiences. If you don’t know the URL for your test site, contact support for assistance.
When testing, you must create a new account for each test. Do not reuse the same email address as this will link multiple applications to the same user profile, and will cause different behaviors within the application as some information will be shared. Many email providers allow the use of a “+” to create unique email addresses. For example, If I am “[email protected]”, I could use “[email protected]”, or to stay more organized, I could add a date, such as “[email protected]”. This will keep all test accounts separate.
If you are a live client testing a change or update, it is not necessary to fill out every field on the application. Simply enter information into all required fields necessary to navigate to the change, and verify that this change is appearing as expected. Log in to the Lender Hub and verify that the data/change/etc. is also present in the application tab of your test loan. If this change involves adding a new field, please submit the application and push it to your LOS to ensure that the new field is populating properly in your LOS. If this change is working as expected, notify a Revvin Support Specialist and we will push this change to your production environment.
If you are onboarding or testing a new flow, enter data into all fields on the application. This is done to ensure that all data is saving properly, and all fields are mapped to the correct location within your LOS.
Throughout this process, be sure to test any and all integrations, including credit pulls, verification of assets, verification of employment, and/or pricing. Some integrations may require unique test credentials or a test mode to be activated, so coordinate with your Revvin Implementations or Support Specialist for further clarification around testing procedures for your specific integrations suite.
Once the application is submitted, it should first be reviewed in the Lender Hub to ensure that all data is saved and displayed properly, and then the file can be pushed to your LOS (if this push is not being handled automatically upon submission).
Open your LOS and locate the file. Compare the data and fields within the Lender Hub to the data within your LOS to ensure that all fields are transferring correctly, and any custom-mapped fields are populating in their respective places in your LOS.
You will need to run multiple tests to test functionality across different loan scenarios. You will need to run one test per loan type offered in your platform (Purchase, Refinance, HELOC, etc.). You will also need to test and verify the application flow when a co-borrower is present.
If you have opted to allow the option for the borrower to fill out the application on behalf of the co-borrower, you will need to test both scenarios of the borrower filling out the application, and the co-borrower filling out the application separately.
Testing these scenarios could be done as follows -
Test 1 – Single borrower, purchase application
Test 2 – Unmarried co-borrowers filling out the application separately, refinance application
Test 3 – Married co-borrowers filling out the application together (on behalf of the co-borrower), refinance application
Once you have completed testing, notify a Revvin Support or Implementations Specialist for the next steps in enhancing your platform or pushing changes to production.