Quality Assurance

Traditionally, we only perform unit tests on the service layer (given a data, service, and front-end layer architecture). Unit tests are developed throughout development. We strive for a very high percentage (80-90%) but consider sufficient coverage over 50%.

Functional testing is based on the requirements outlined in the project specification document. Generally, back end/administrator and front end user testing is included in the functional testing.

Once sections of an application have been QA’d through unit and functional tests, automated tests can be developed for ongoing quality assurance. The results of these tests are published to the team channel in Slack so the entire team is aware of test results and progress.

With each release, regression testing is performed to assure that the site is functioning as it should after an update. The regression covers the basic functionality of features deployed in previous releases, as well as any areas related to the new feature/functionality being released. A combination of automated and manual testing is preferred for regression.

The QA and IT teams partner to execute tests to check CPU utilization and server performance under peak load conditions. Load testing is done to make sure that the site can handle a load and remain performant.

The scope of security testing varies depending upon the project; for example, testing may include verifying that access is handled correctly based on IP address. For projects that require a login, we test for account creation and management, user access, and password management.

The goal of web accessibility is to assure that people with disabilities can perceive, understand, navigate, and interact with the web. Our team uses automated scans along with manual testing to audit 508/accessibility compliance. After the issues are identified, we work with our Development team to remediate the issues and verify compliance.