You and your testing team have been tasked with testing a new benefits application that is being developed. Your company uses a flexible benefits plan, allowing company employees to customize their health benefit plan based on personal preferences. The benefits application is expected to go live in $3$ months.

Your company$$s Human Resources department uses a cafeteria$-$style approach to provide employees with health care benefits. Each September, employees review their current benefits, modify their elections and then sign election forms. Any changes must be entered and tracked in the benefits application. For medical insurance, an employee enrolls with a preferred provider organization $($PPO$)$ or health maintenance organization $($HMO$).$ The company currently pays the monthly medical premiums for its employees. However, if an employee enrolls in a dental plan or vision plan, the employee pays a modest monthly premium for the optional plan. An employee may carry medical, dental, and$/$or vision coverage for one or more of his or her family members. In order to carry insurance on a family member, the employee must carry the same coverage. For example, to carry dental insurance on a spouse, the employee must also carry dental insurance on him or herself.

The benefits application must track employee information like employee ID$,$ department ID$,$ name, address information and office extension number. It must also track information about each insurance company to include the company number and company name. Dependent information and their relationship to the insured employee must also be tracked. An employee must be able to request an enrollment form, and Human Resources must be able to update the effective date of the health benefits on the form. In addition, the application must track the health care benefits rates for PPO and HMO, plus dental and vision rates. Benefits rates differ by employee only, employee $+$ spouse, employee $+$ spouse $+$ one child, and employee $+$ family.

Testing Assignment Description:

Review the testing assignment scenario. Then, use all of the testing techniques, methods, processes, and tools you've learned throughout the semester to complete a comprehensive plan for testing. You will submit your plan in the form of a professional report or a PowerPoint presentation. It should incorporate all of the following elements:

User stories$/$requirements for testing

Static and dynamic testing techniques

Test conditions, test cases and potential test scripts

Test design to include white box and black box techniques

Exploratory testing plans

Functional test plan or full test plan

Test effort estimates.

Testing team roles and resources

Plan for incident management and reporting

Key metrics that you plan to measure and report on

Risk analysis

Throughout the report or presentation, be sure to explain why you chose certain techniques or approaches over others. Also, explain any assumptions you made as you performed the assignment.

Milestones and Deadlines:

To ensure adequate and timely effort for your course capstone testing project, you will have the opportunity to submit $2$ preliminary milestones and $1$ final milestone $($optional$)$ for feedback as part of your comprehensive plan for testing. All milestones will be due on the final deadline for this project. For the final due date, see the Submission Instructions below. Requirements for these milestones are described below. Optional due dates to receive feedback for the milestones are as follows:

Milestone #$1-$ OPTIONAL Progress Check: Due on Day $7$ of Week $6$:

Begin creating your written report or PowerPoint presentation. For this progress check, include the following elements:

User stories$/$requirements for testing

Static and dynamic testing techniques