QA Overview

There are Quality Assurance tasks carried out in every sprint that we complete. We consider internal testing in the following ways: Unit testing is a software development process in which the smallest testable parts of an application, called units, are individually and independently scrutinized for proper operation. Unit testing can be done manually but is often automated.

• Unit tests: We develop algorithms to test the smallest parts of each application in an automated way. These are developed as we build the code so that we have a well-functioning frontend application from the beginning.

• Automated testing: In the case of the Money Tools, there is a suite of technology that is run on the CFPB-side to make sure that all code is working correctly. We also perform automated end-to-end integration testing using Cypress and Newman. All the automated testing is integrated at the PR level to ensure errors are caught and fixed prior to merging to master branch.

• Exploratory testing: Sprints for this type of testing begin when the principle development of the app is 75% complete. Development and design team members have tasks within several sprints to test the app in identified devices, environments and operating systems. The apps are also reviewed for content, logic and accessibility. Each QA tester records their results using a QA Test Plan designed specifically for the project. Feedback from this internal testing are reviewed and differentiated between bugs, enhancements and additional features. They are quantified and added to the project backlog in priority order.

My Money Calendar QA Test Plan