Testing the Benefits-Selection system is not a single activity, nor is it a phase in the project during which we assess quality.  If our programmers are to obtain timely feedback on the evolving product quality, testing must occur throughout the lifecycle.  The specific tests will be dependent upon the project’s current phase.

• Inception Phase :  Initial test planning

• Elaboration Phase : Test architectural baseline

• Construction Phase : Significant testing at each build

• Transition Phase : Re-test fixes and regression tests

Types of Tests

The testing process includes a variety of tests with each one focusing on specific area of the software.  A test of the application could focus on a particular area or benefit plan, a single unit of code, integrated units, or a complete application or system.

Benchmark Test – comparing the performance of a target-of-test to a know standard such as an existing build or measurement

Configuration Test – verifying that the target-of-test installs properly and can be installed successfully on different configuration or under different conditions.

Integrity Test – verifying the target-of-test is reliable, robust, and resistant to failure during “go-live”. Selerix provides an automated report that verifies software configuration, data integrity, enforcement of eligibility rules, and rate calculations. This built-in report is used in all phases of implementation.

Performance Test – Verifying the acceptability of the system and system performance using various configurations while the operational conditions remain constant.

Stress Test – Verifying the acceptability of the system performance, performance when abnormal conditions are encountered, such as diminished resources or an extremely high number of users over a short period of time.

[ back to methodology ]