No software can be reliably implemented without a proper test plan. CyberData supports all testing environments and activities. In following with our Agile Test-driven Development (TDD) methods and best practices, our DBAs co-create unit tests with code to validate the functionality of each component we develop and/or enhance. In addition, our team develops formalized test plans, test cases, and test scripts to support integration, certification, stress lab, and user acceptance testing. The following provides an overview of the testing types our team typically supports:

Unit Testing. The validation of the smallest unit of software (individual programs and/or subroutines) ensure that application software functionality satisfies design specifications. Programs that share common functionality (system and/or business functions) can be unit tested in conjunction with each other. The purpose of unit testing is to ensure that every executable statement can execute successfully and achieve desired results.

Integration Testing. The validation of logical grouping of programs (typically subsystems) to ensure that they can interface with other logical groupings of programs, to ensure that the functionality satisfy design specifications.

Performance and Stress Testing. Testing performed by technicians to assess the capacity and throughput of a system before it reaches maximum threshold or failure point.

Security Testing and Evaluation. Comprehensive security testing performed by technicians to ensure that the system meets all legislative, regulatory, SEC OIT security and privacy requirements.

Systems Functional Testing. Testing performed by test technicians to assess the end-to-end functionality and interoperability of multiple subsystems comprising an overall integrated system

System Integration Testing (SIT).Testing performed to assess the interfaces and interoperability of an application with other sub-system components such as databases, hardware, software, or communication devices

Regression Testing. Testing performed by test technicians to assess whether or not software changes to implement new business or technical requirements have negatively impacted unrelated application program or system functions.

User Acceptance Testing. The validation of the system by the user community to ensure that user requirements and expectations have been satisfied and that the system is ready for release to the user population.