help me to remove this plagiarised thing
hard_answer.docx
Unformatted Attachment Preview
Capstone Project
Software Testing and Quality
2. Introduction
The main background of benefits application is for allowing company employees to customer
them heal benefit plan based on personal preferences. So the theme of this project is testing the
benefits application which helps the employees to customer in choosing their insurance plan. As
a tester, I should able to reach the specifications of the document as wells requirements of
employees. During the testing process of benefits application, we use various techniques and
2
methods which helps in delivering a quality product. Following are the testing techniques used
for testing this application; Static and dynamic testing techniques, White box and Black-Box
techniques, and Exploratory testing plans. Basically, the testing of benefits application starts
with identifying the user stories/requirements for testing and then later we use Static and
dynamic testing techniques for improving the quality of the product. In the second phase, test
conditions, test cases and potential test scripts are executed. Also test design to include white box
and black box techniques and Exploratory testing plans are performed along with a full test plan.
Whereas in the third phase Test effort estimates, Testing team roles and resources, Plan for
incident management and reporting
Key metrics that planned to measure and report on and finally we deal with Risk analysis of the
application. Majorly the output of this application should able to allow an employee to design
their own benefits plan which meets their individual and unique needs.
3. User Stories / Requirements for Testing
Identifying or writing the user stories is the major phase while begging the testing of an
application. So here we do write more then dozen user stories which might help the employees to
understand it easily. The main benefit of witting user stories is that we can know the end to end
functionality of an application in a simply way. Also, the requirements and specifications of
3
benefits application can be grabbed perfectly by documenting them. Before identifying the test
cases and test conditions we need to write user stories and requirements for testing.
3.1 User Stories
Following are the User stories for benefits application.
1. As an employer, I have to provide more health care benefits associated with insurance plan
so that the employee can have good preferences on the benefits plan.
2. As an employee, I should able to review the current and additional health care benefits so
that I can decide which benefits need to include in my benefits plan.
3. As an employee, I have to choose preferred provider for the medical insurance so that my
organization pays my monthly medical premiums.
4. As a provider search employer, I need the ability to search for providers by specialty so that I
can more efficiently refer employee to specialists.
5. As a database administrator, I need to save the employees information and insurance
company details on the company’s database so that the benefit application can easily track
the information which is needed.
6. As an employee, I should able to know the pricing levels for optional plan so that I can
decide whether to enroll in dental plan or vision plan.
7. As an employee, I have to request for an enrollment form so that Human Resources would
able to update the effective date of the health benefits on the form.
8. As a head of family, I should know the health issues of each family member so that I can
decide on whether to pay a modest monthly premium for the optional plan.
9. As a developer, I have to make sure that the benefits application is user-friendly so that the
application can be operated efficiently and quick.
4
10. As an employee, I have to provide my family details to the company so that the health care
benefits are also provided for them.
11. As an employee, I should able to modify and change my benefit plans so that I can have core
benefits.
12. As an employee, I want to know about how much amount can I claim if any one of my
family member undergoes surgery.
13. As a customer, I want to read the reviews about the providers so that I can decide whom to
choose among both.
14. As an employee, I should able to download the privacy policy so I can understand how an
employee’s information will be used as a part of the benefits application process.
3.1.1 Tabular for User Stories
Project ID/Title:
Flexible Benefit plan
Release #:
Flexible Benefit Plan
Sprint #:
User Stories
Feature
As a(n)
I would like to
So that
Flexi Benefit Plan
Employee
Login to the application
User can choose and submit Medical Plan
(Dental Plan/Vision Plan) for employee and his
Click on Flexi Benefit Plan link
dependents/family members
Check Employee ID, Department ID is
populated on page
Employee has to enter the Address and
Office extension or phone number
Employee can enter dependencies
names
6
Employee has to enter the relationship
of dependent
Employee has to enter the Date of Birth
of entered dependent
Employee has to select the gender of
dependent
Employee dependent gender can be
determined based on selection of
dependent relationship
Employee has option to select Dental
Plan
Employee has option to select Vision
Plan
Employee need to select Dental Plan
for self if employee selects Dental plan
to dependents
7
Employee need to select Vision Plan
for self if employee selects Vision plan
to dependents
Application has to populate the
Insurance company name, number and
address based on user selection for
Health Insurance Plan
Application has to populate the
Insurance company name, number and
address based on user selection for
Dental Plan
Employee can enroll for Health benefits
by self
Employee can enroll for Health benefits
for self and spouse
8
Employee can enroll for Health benefits
for Spouse and at most one child only
Employee can enroll for Health benefits
as family member his parents and this
won’t be applicable for employee
siblings
Application has to populate the PPO
and HMO details for the employee
selected Health benefits
Application has to populate the
Insurance company name, number and
address based on user selection for
Vision Plan
Application has to calculate the total
amount of Insurance premium to be
paid based on the options selected by
9
user
Application has to notify the user
options selected and has to capture the
confirmation from user before going to
update
Application has to provide validity date
of Insurance premium based on the user
selection
Application has to send the reminder
email before Insurance premium
expires for renewal
3.2 Requirements for Testing
Following are the requirements for testing
▪
In every year of September, the employee has to review the current benefits and modify their
elections and then sign election forms.
▪
All the employees in the company have to enroll in one of the insurance provider in order to
get their health care benefits.
▪
Once the employee gets registered with a provider, he/she should receive a personal identity
card which contains the employee details and plan type.
▪
The database administrator should make sure that Employee ID, departed ID, name, and
address all the details of an employee are stored on companies’ database.
▪
The newly health care benefits or additional benefits should be available to the employees.
4. Static and dynamic testing techniques
4.1 Testing Techniques used for Static Testing
Informal Reviews: This is one of the type of review which doesn’t follow any process to find
errors in the document. Under this technique, you just review the document and give informal
comments on it.
Technical Reviews: A team consisting of your peers, review the technical specification of the
software product and checks whether it is suitable for the project. They try to
find any
discrepancies in the specifications and standards followed. This review concentrates mainly on
the technical document related to the software such as Test Strategy, Test Plan and requirement
specification documents.
11
Walkthrough: The author of the work product explains the product to his team. Participants can
ask questions if any. Meeting is led by the author. Scribe makes note of review comments
Inspection: The main purpose is to find defects and meeting is led by trained moderator. This
review is a formal type of review where it follows strict process to find the defects. Reviewers
have checklist to review the work products. They record the defect and inform the participants to
rectify those errors.
Static code Review: This is systematic review of the software source code without executing the
code. It checks the syntax of the code, coding standards, code optimization, etc. This is also
termed as white box testing. This review can be done at any point during development.
4.2 Testing Techniques used for Dynamic Testing
▪
Detects the errors by executing the code
▪
(Static Vs Dynamic Testing, n.d.).
▪
Dynamic Testing tests the performance of entire software by executing the code so it’s named as
“Dynamic” (Static Vs Dynamic Testing, n.d.).
▪
Dynamic Testing is also known as “Validation” (Softwaretestinghelp, n.d.).
▪
The main objective of Dynamic Testing is to track the requirements of a business and make the
software better.
▪
To deliver a quality product it requires more defects (Static Vs Dynamic Testing, n.d.).
▪
Identifying and fixing the errors in a software is expensive (Static Vs Dynamic Testing, n.d.).
Dynamic Testing uses three different techniques’ for testing a software, (Softwaretestinghelp, n.d.).
Unit Testing: Under unit testing, individual units or modules is tested by the developers. It
involves testing of source code by developers.
12
Integration Testing: Individual modules are grouped together and tested by the developers. The
purpose is to determine that modules are working as expected once they are integrated.
System Testing: System testing is performed on the whole system by checking whether the
system or application meets the requirement specification document.
Also, Non-functional testing like performance, security testing fall under the category of
dynamic testing.
13
5. Test Cases, Test Conditions, and Potential Test Scripts
5.1 Test Conditions
Following are the test conditions for benefits application.
▪
Employee has to open the correct URL for sign into the application.
▪
In order to sign-in into the application the employee has to enroll before.
▪
Can be the application accessed by all employees or only restricted to few of them?
▪
Can be the application accessed on different sources like mobiles, laptops, desktops, etc.
▪
What are the possible ways for an employee to enroll for his/her benefits plan with in the
application?
▪
The employee needs to enter valid employment Id and password.
▪
User should able to access the portal.
▪
PPO or HMO name and address should populate on the page.
▪
Employee name needs to populate on the page automatically
▪
Check box should be available to select Vision Plan and Dental plan.
In the below shown test case template ,all the test conditions are explained in detail.
5.2 Test Cases
Project Name:
Test Case Template
Test Case ID: FBP_01
Test Designed by:
Test Priority (Low/Medium/High):
Test Designed date:
Module Name: Flexi Benefit Plan
Test Executed by:
Test Title: Submit Flexi Benefit Plan
Test Execution date:
Description: Test the Flexi Benefit Plan page
Pre-conditions: Employee has access to the portal. Employee has valid username/employee id and password to login.
Dependencies:
15
Step
Test Steps
Test Data
Expected Result
Actual Result
Status
(Pass/Fail)
1
Navigate to Flexi
http://xyzabc.com/flex
User should access to the
Benefit login
ibenefitplan
portal
Provide
Employee id: e000001
If username/employee id or
username/employ
Password:
password is invalid, then
ee id and
TestPassword@123
username or password is
page
2
password
invalid message need to be
displayed.
3
Click on Login
Employee id: e000001
If username and password is
button
Password:
valid then application should
TestPassword@123
take employee to the home
page
Notes
16
4
Click on Flexi
NA
Benefit Plan link
Application should take
employee to the Flexi Benefit
Plan
5
Click on Flexi
Employee id and
If application is password
Benefit Plan link
password
protected for Flexi Benefit
Plan then it should prompt for
User credentials again
6
Flexi Benefit Plan NA
Employee ID and Department
page
ID has to be populated on the
page automatically
7
Flexi Benefit Plan NA
PPO or HMO name and
page
address should populate on
the page
8
Flexi Benefit Plan NA
Employee name needs to
page
populate on the page
automatically
17
9
10
11
Flexi Benefit Plan Check Box
Check box should be available
page
to select Dental Plan
Flexi Benefit Plan Check Box
Check box should be available
page
to select Vision Plan
Flexi Benefit Plan Text field
Two text fields should be
page
available to enter the
dependent details for Health
Plan of spouse and/or child
12
Flexi Benefit Plan Date picker
Two Date picker icons need to
page
be displayed for each record to
select the date of birth of
dependents
13
Flexi Benefit Plan Check Box
For Each and every text field
page
there should be corresponding
check box to select Dental Plan
14
Flexi Benefit Plan Check Box
For Each and every text field
18
page
there should be corresponding
check box to select Dental Plan
15
Flexi Benefit Plan Dropdown/pull down
Dropdown should display to
page
select dependent relationship
menu
with the following options
spouse and children
16
Flexi Benefit Plan Check Box
This option should enable the
page
option to enroll employee
father and/or mother
17
Flexi Benefit Plan Text Field
Text fields should be enabled
page
to enroll father of the
employee
18
Flexi Benefit Plan Text Field
Text fields should be enabled
page
to enroll mother of the
employee
19
Flexi Benefit Plan Dropdown/pull down
Dropdown should display to
19
page
menu
select family member details
with the following options
father and mother
20
Flexi Benefit Plan Date picker icons
Two Date picker icons need to
page
be displayed for each record to
select the date of birth of
parents
21
Flexi Benefit Plan Submit button
If user selects the Dental plan
page
or Vision plan to his
dependents or family members
without selecting for self then
error message need to be
displayed to the user to select
the Dental Plan/Vision plan for
self.
22
Flexi Benefit Plan Submit button
If user doesn’t select the date
20
page
of birth for dependents or
family members then error
message need to be displayed
to the user to select date of
birth
23
Flexi Benefit Plan Submit button
If user selected date of birth
page
for dependents and family
members then submits the data
then total amount of premium
to be displayed to the user
24
Flexi Benefit Plan Submit button
A confirmation message need
page
to be displayed to the user with
the premium details selected
by the user and enrolled
members’ details.
25
Flexi Benefit Plan Submit button
The total amount premium
21
page
need to be paid i.e. the amount
that will be deducted from
salary will be displayed to the
user as message
26
Flexi Benefit Plan Submit button
Confirmation message of
page
enrollment details need to be
displayed to the user
27
Flexi Benefit Plan Submit button
A confirmation mail with the
page
details of enrolled dependents
and family members and the
total premium amount need to
be sent automatically
28
Flexi Benefit Plan Submit button
The contact details, website
page
name, email id of customer
support and company
addresses of the PPO and
22
HMO companies need to be
sent in mail along with the
above said details.
29
Flexi Benefit Plan Submit button
The insurance enrollment id
page
details for the each member
including employee need to be
sent along with the above
details.
30
Flexi Benefit Plan Submit button
The print option of the
page
enrolled member’s details can
be provided to the employee.
Post-conditions:
The enrolled member’s details will be updated in the database and automatically the same details will be updated to the PPO and
HMO.
5.3 Potential test scripts
In benefits application, test scripts are chosen by the testing manager in the project. The test
script is nothing but a test case fabricated with test data. It all tells about the user requirements
and makes sure that the user gets satisfied with the product. The steps involved in test script is
functionality testing. Also, it displays the pass/fail of a test case.
6. Test design to include white box and black box techniques
Black box testing is a type of software testing method which helps the tester in testing the
software without knowing the application code. Usually, it is accomplished by the testing team
(Software Testing Class, 2014).
▪
Independent software testers are responsible for this testing.
▪
Functional testing and External testing defines the Black box testing.
▪
Concentrates more on the functionality of the system.
▪
The basis for test cases is requirement specifications documents.
▪
Implementation and programming knowledge is not required.
▪
Black box testing is most appropriate for only higher levels of testings like System Testing,
Acceptance Testing. And Functional testing, Behavior testing, Close box testing are carried
out by this testing (STF., 2010).
White box testing is a type of software testing method where the tester who is going to test the
product knows the internal structure of a product. usually, it is done by the developer’s team
(STF., 2010).
▪
May the software developers can have the responsibility for White box testing.
▪
Structural and interior testing define the White box testing.
24
▪
Concentrates more on testing the code of a product.
▪
Using design document, we can start White box testing.
▪
Implementation and programming knowledge are necessary for using White box testing.
▪
White box testing is most appropriate for only lower levels of testing’s like Unit Testing,
Integration Testing. The other testing’s like loop, path, code, logic and open box testing are
carried out by this testing (STF., 2010).
7.Explortay testing plans
In a software development cycle, an exploratory testing is an experience based technique where
the testers spend their maximum time in executing the testing methods and minimum time in
planning. The test charter, scope of short time-based test effort, and objectives to be used in the
testing are created in the planning. In exploratory testing without formally documenting the test
conditions, or test cases we can perform test design and test execution parallel. By this, we
cannot easily conclude that more of formal testing is not used. Basically, using exploratory
testing, there are plenty of benefits when a tester tries to disturb the application and perform
exactly opposite to how a user uses it. When trying to compare the requirements driven testing
techniques using well-crafted test conditions and test cases, they do not always cover all the
elements while testing. Let’s taken an example, where the tester decides to choose boundary
value analysis and tests the important boundary values by writing them down. The reports which
are prepared during the testing are written in exploratory testing and they can be used later for
further changes or modifications in the product (Black, Rex, Veenendaal, Erik Van & Graham,
Dorothy, 2012).
References
25
Test Coverage
In a software development life cycle, the measurement of a software test which is performed for
one or more times by a set of testing techniques is taken over by tes …
Purchase answer to see full
attachment
Recent Comments