I Am Sharing 'Beverly - Wood - CS459 - Unit 5 IP' With You

MASTER TESTING PLAN FOR WOOD’S BEAUTY SUPPLIES
Software Test Plan
Final Version
Beverly J. Wood
Software Testing (CS459)
February 3, 2021
Page 1 of 41
Table of Contents
TEST PLAN IDENTIFIER.......................................................................................................5
ABSTRACT..........................................................................................................................5
INTRODUCTION.................................................................................................................6
1.1 PURPOSE OF DOCUMENT............................................................................................6
1.2 OBJECTIVES..............................................................................................................7
1.2.2 PRIMARY OBJECTIVES.......................................................................................7
THE IMPORTANCE OF THE TEST PLANNING PROCESS.......................................................8
CHARACTERISTICS OF A TEST PLAN.................................................................................10
TEST PLAN OUTLINE........................................................................................................13
4.1 SCOPE....................................................................................................................13
4.2 SYSTEM DESCRIPTION & OPERATIONS..................................................................14
4.3 TEST INDENTIFICATION & LEVELS..........................................................................15
4.3.2 SYSTEM TESTING............................................................................................16
4.3.3 UNIT TESTING.................................................................................................16
4.3.4 ACCEPTANCE TESTING....................................................................................16
4.3.5 PERFORMANCE TESTING................................................................................17
4.3.6 REGRESSION TESTING.....................................................................................17
4.3.7 SECURITY TESTING..........................................................................................17
Page 2 of 41
4.3.8 WEB USER INTERFACE TESTING......................................................................18
4.9 TEST ACCEPTANCE CRITERIA..................................................................................19
4.9.2 ITEMS/FUNCTIONS REQUIRED TO BE SIGNED OFF........................................19
4.9.3 ITEMS REQUIRED TO BE READY PRIOR TO THE START OF TESTING...............19
TEST STRATEGY................................................................................................................20
5.2 TEST OBJECTIVES...................................................................................................20
5.3 TEST ASSUMPTIONS..............................................................................................21
5.3.2 KEY ASSUMPTIONS.........................................................................................21
5.3.3 GENERAL ASSUMPTIONS................................................................................22
5.4 TEST DEPENDENCIES.............................................................................................23
5.5 TEST PRINCIPLES....................................................................................................23
5.6 TEST PLANNING APPROACHES..............................................................................24
5.6.2 APPROACH TAKEN FOR THE TESTING PROJECT..............................................26
5.7 TEST PLAN & SCHEDULE........................................................................................27
5.8 HUMAN TESTING RESOURSES...............................................................................29
5.9 REQUIREMENTS TRACEABILITY.............................................................................30
FEATURES/ITEMS TO BE TESTED AND NOT TESTED........................................................31
6.2 FEATURES/ITEMS TO BE TESTED............................................................................31
SOFTWARE TESTING ENVIRONMENT PLAN.....................................................................34
Page 3 of 41
8.2 TEST ENVIRONMENT DETAILS................................................................................34
8.2.2 SOFTWARE REQUIREMENTS...........................................................................35
8.2.3 HARDWARE REQUIREMENTS..........................................................................36
8.2.4 INTERFACE REQUIREMENTS...........................................................................37
8.3 ROLES & RESPONSIBILITIES FOR THE TEST ENVIRONMENT..................................39
TEST DELIVERABLES.........................................................................................................40
Page 4 of 41
TEST PLAN IDENTIFIER
WOOD’S BEAUTY SUPPLIES WEB SHOP TEST PLAN
FINAL TESTING PLAN
VERSION # 04-WBS-O2-TP-69
ABSTRACT
The Test Plan has been created to facilitate communication within the team members,
testers, end users, stakeholders, and even the client, along with providing details about the
Software Testing Life Cycle phases, the methods/techniques used to perform software testing,
the different approaches that can be taken, and what gets tested, and how it will be tested. This
document will clearly describe what the test deliverables will be and what is deemed in and out
of scope. The individuals involved in the development of the software as well as the software
testing processes, the test schedules, and other documentation crucial to the testing processes
will also be defined in this document.
Page 5 of 41
INTRODUCTION
There is always a need for the advancement of quality in terms of today’s online
conduits for marketplaces. When customer’s and end-users go to certain websites in order to
purchase goods, they expect a user-friendly, secure, and organized web-based platform to
purchase goods from.
In Software Development, several issues pose themselves as being the most important
for the system to be successful. The software development phases may perhaps follow all the
necessary procedures but fail to succeed due to poor or no testing at all. In software testing, it is
essential to consider the best environment along with what strategies to use. The selection of
the most suitable testing environment driven by the need to discover any defects that a system
may have before distributing it to the world. The intention of a test environment is to provide
the necessary resources that the testing team will use to carried out the many task it takes to
perform testing on the software.
1.1 PURPOSE OF DOCUMENT
The Purpose of this document is to define:
 The test scope, focus area and objectives
 The test responsibilities
 The test strategy for the levels and types of test being performed
 The entry and exit criteria
 The test estimates
 Risk, issues, assumptions, and test dependencies that may be present
Page 6 of 41
 The test schedule and milestones
 The deliverables of the test
 Business Requirements and critical transactions to be tested
1.2 OBJECTIVES
1.2.2 PRIMARY OBJECTIVES
This test plan will provide the platform for testing the project “Wood’s Beauty Supplies
web shop”. The objective of testing is to see if the software being designed meets the specified
requirements. This document will act as an instruction guide for all testers to be able to follow
and understand throughout the entire software testing life cycle. Also, this document will help
clarify what is being done throughout the whole testing process, and even explain specific steps,
methods, techniques, etc. for the stakeholders, end users, and the client in a way that they will
understand.
Page 7 of 41
THE IMPORTANCE OF THE TEST PLANNING PROCESS
A test plan is a comprehensive document that defines the testing objectives, strategies,
resources, estimation, and deliverables required for testing. This document services as an
instruction manual for conducting software testing activities, as well as a means of
communication between the project manager, testing team, stakeholders, end users, and the
clients.
Usability and general testing in a process, will not end if the software is still being
developed. In each phase of testing, the different attributes of the test must be calculable in
order to guarantee the integrity of the software and the process as a whole.
Testing is a combination of multiple Software Life Cycle activities that are relevant to
planning, designing, and the evaluation of the software application or system in order to locate
the defects and determine whether or not the software fulfils the specified requirements. The
information that makes up the test plan covers just about everything that is involved in the
Software Testing Life Cycle that should be circulated among all parties involved in the testing
process. This information is also vital to successfully testing and designing a thriving software
application.
A well written test plan guarantees that the features and functionalities of the
software/application are being tested and correctly implemented. This is important because
these features and functionalities get broken down into Testing Activities, then assigned to a
tester who will conduct the necessary tests. This helps the project manager gather a cost
estimation of the necessary resources that will be invested in the project.
Page 8 of 41
A good test plan leaves nothing to chance and makes the task of testing software
and/or systems easy. Performing software/system tests according to an inclusive plan saves time
and money at the same time as it is improving productivity. However, an effective test plan
takes time and commitment. Over time though, the benefits become apparent in terms of cost
savings, software quality and user satisfaction. They are a resourceful way of keeping the testing
process and team on schedule.
Page 9 of 41
CHARACTERISTICS OF A TEST PLAN
There are many characteristics that can be included in a well written test plan. But not
all characteristics are necessary for every test plan. The characteristics that make up a test plan
depends on the type of software being developed and tested.
For this project, the characteristics of the test plan will explain in detail the necessary
information needed for others to fully understand the complete testing process. This test plan
will follow a few simple guidelines which are:
 Be specific when giving details on properties, features, functions, techniques,
and tools being used in the testing process.
 To avoid lengthy sections, lists and tables will be used when possible.
 The test plan will be updated when necessary.
The characteristics of this test plan includes:
 Test Plan Identifier
 Overview of the plan
 Importance of a Test Plan
 Characteristics of a Test Plan
 Features and Items Being Tested & Not Being Tested
 Test Planning Approach
 Approach Taken for the Test Project
 The testing levels.
 Testing type
 Outline of the Test Plan
Page 10 of 41
 Scope
 System description and operation (name of test sites, test configuration)
 Test identification & test levels
 Planned tests & test schedules
 Requirements Traceability
 Pass/Fail Criteria
 Test Plan Deliverables
 Risk
 Test Environment Properties(hardware, software, network)
 Cost Estimation(human and technical resources)
 Testing Schedule
 Key Milestones
 Timeline
 Staffing and Training Needs(required skill set, necessary training, and
responsibilities)
 Assumptions and Dependencies
 Enter/Exit Criteria
 Approvals
 References
 Appendix A
A test plan should explain to the reader the testing process that is being performed,
along with the strategies of the test, the deliverables and requirements in a way that is easy to
Page 11 of 41
for anyone to understand. The objectives, expected results, and enter/exit criteria should be
stated clearly as well.
Page 12 of 41
TEST PLAN OUTLINE
The section below outlines the test plan for the software development and testing
processes. It contains components and tasks involved in scope, system description, test
identification and test levels, planned tests and test schedules and requirement traceability. The
primary objective of this plan is to provide a clear guideline for the software testing.
4.1 SCOPE
This test plan focuses on the development and testing of an online beauty supply shop.
Both functional and non-functional testing will be the focal points. The functional test will
include unit, system, and acceptance testing. The non-functional testing will include
performance, security, usability, and compatibility testing. Testing is completed in stages to
ensure there is little to no rework necessary.
This software will be programmed using the programming language Java. and will
require an internet connection at all times. The system shall provide access for authorized users
at any given time (with some restrictions) to the web shop. The software application should run
without any errors and have the ability to store information(data) within a database. The
information needing to be stored should be relevant to the customers, products, and vendors.
And be grouped and categorized in separate tables within a database which will be accessible
and managed by the owners, and whomever they see fit. There should be remote access
available for the owners at any time so that they are able to check on their shop whenever the
need arises.
Page 13 of 41
4.2 SYSTEM DESCRIPTION & OPERATIONS
This document is the test plan for Wood’s Beauty Supplies, a web-based shop that sell
discounted high quality beauty supplies to their customers. This test plan will concentrate on
the development and testing for web-based software/system. Functional and non-functional
testing will be the main concentration, along with a few other testing techniques. This web-
based beauty supply shop will be a fully functional software system/application that has similar
functionalities of a physical beauty supply shop.
Wood’s Beauty Supplies will operate using an ecommerce inventory management
software that combines in a single system - management, purchasing, warehousing, sales,
marketing, shipping, and customer service.
This software/system will be designed with a Graphical User Interface in place acting as
the mediator between the user and the system/software. All interactions with the
system/software will require the use of a GUI in order to complete the task for the web shop.
The GUI can significantly impact the performance of a webstore and can lead to higher or
weaker sales.
Customers will be able to browse the selection of beauty supplies available, add items
to their cart, complete transactions, plus many more features/functions. Each time an order is
placed customers will be asked to confirm their shipping address as a precaution and to ensure
that products are delivered to the correct address. Also, a SMS message will be sent to the
number in the account of the customer that will include a verification number to be entered
into the system, in order to complete the transaction, and process the payment. If the customer
Page 14 of 41
does not enter the verification code within five minutes, or enters an incorrect code three
times, then the account will be locked.
New users will also take advantage of the GUI as they browse through the available
products being sold, however, if a user(who is not a customer) wishes to make a purchase, they
must first sign up for an account and then verify the email address and phone number the used
when they signed up. Once they have created their account and verified the necessary details,
then they are able to perform the task such as adding items to the shopping cart, checking out,
completing an order by adding a payment method that is valid. Verification is necessary when
using certain payment methods.
Other functions of this system/software have to do with the many interfaces there are
for this software. allow the customers to manage their orders right from their personal
dashboard within the web site. The system automates various workflow processes such as
calendars and notifications. The owners will be able to view and track the activity and orders of
the customers, as well as the performance based on information logged within the system.
4.3 TEST INDENTIFICATION & LEVELS
Test identification is an important aspect that should be well approached by the
software development team. All aspects will get investigated from small individual components
and their impact up through functions, sub systems, and the system as a whole. Each of the
levels and aspects will be measured against each other and business needs to determine the
proper test case requirements. Some of the testing levels for this project includes…
Page 15 of 41
4.3.2 SYSTEM TESTING
System testing is a test level that involves a complete and integrated testing of the
software. The aim of system testing is to evaluate the system fulfills the specified requirements.
Tests are performed to verify the non-functional requirements, such as performance in
production-like environment. The purpose of system testing is to make sure the system will run
according to requirements in live environments.
4.3.3 UNIT TESTING
Unit testing is a test level that is carried out by the developer to ensure that the
implemented code works correctly and meets all requirements. The idea of unit testing is to test
the smallest piece of code that is testable to confirm that the behavior coincides with the design
specifications. This method also intends to validate the data completeness, data transformation
and data quality.
4.3.4 ACCEPTANCE TESTING
Acceptance Testing is a level of testing where the software is tested for acceptance.
The main goal of this method is to make sure that the business requirements indicated by the
stakeholders, clients, and end-users, are implemented accurately into the software application.
Non-functional requirements, such as user-friendliness of the system are also tested in this type
of testing.
4.3.5 PERFORMANCE TESTING
Performance Testing is a non-functional testing technique that is used to find blockages
or flaws in the performance instead of finding bugs within the software. Performance testing is
Page 16 of 41
thought to be one of the essential and mandatory types of testing in relations to speed,
capacity, stability, and scalability.
4.3.6 REGRESSION TESTING
Regression Testing is a testing method that revalidates if the system/software works
according to the specified requirements after the code has been modified in different parts of
the code. These modifications can be due to change request or fixing certain defects within the
code.
4.3.7 SECURITY TESTING
Security Testing involves testing software to identify any flaws and/or gaps from the
security and vulnerability point of views. Some of the characteristics that security testing should
ensure includes:
 Confidentiality
 Integrity
 Authentication
 Availability
 Authorization
 Software is secure against known and unknown vulnerabilities
 Software data is secure
 Software is according to all security regulations
 SQL insertion attacks
 Injection flaws
 Plus, many more
Page 17 of 41
4.3.8 WEB USER INTERFACE TESTING
Web User Interface Testing revolves around the graphical user interface(GUI) testing
that includes testing both functionalities and usability of the website or the web-based
application. Specifically using web UI testing, the GUI elements such as fonts, layouts, buttons, ,
checkboxes, images, colors, etc. is referred too. This type of testing typically concentrates on
how the look-and-feel of the website appears to end-users. Automated Web UI Testing is the
preferred method of web UI testing to use nowadays due to the fact that it ensures a better test
coverage and faster test execution. Additionally, by using automation tools to conduct
automated web UI test, the design and development specifications are guaranteed to be met
and also ensures that the website will be user-friendly. This sort of testing is carried out to find
defects in the functionality or in the design of the website quickly. This web testing process is
quite critical to achieve high-quality websites, but the testers face certain challenges while
performing automated UI testing for websites and/or web applications.
4.9 TEST ACCEPTANCE CRITERIA
4.9.2 ITEMS/FUNCTIONS REQUIRED TO BE SIGNED OFF
 Functional Specification Document must be approved by the Project Manager
 Use Case Documents are required to be available before the Test design phase
kicks off
 Test cases must be approved and signed off before the testing is carried out
Page 18 of 41
4.9.3 ITEMS REQUIRED TO BE READY PRIOR TO THE START OF TESTING
 Code implementation is complete, and the Developer has performed Unit
Testing
 Software has been deployed and is ready to be tested on the Test environment
 Production like data is available so the functionalities can be tested
 The plan for resolving the errors and/or bugs based on Unit testing and the
assessment norms are required to be available before testing is ready to begin
Page 19 of 41
TEST STRATEGY
The developer of the software for Wood’s Beauty Supplies will take advantage of test
cases that have been previously used for any new features and/or functions being added. Black-
box testing will be performed by the Testing Team on the software to save time, and Automated
tools will be utilized to conduct Regression testing near the end of the day, while the
modifications needing to be made to the software are being created. The reason for this is to
allow the modified parts of coding that could have possibly resulted in errors or bugs to be
isolated from the rest of the code that is running correctly and contains no errors or bugs.
As each software testing phase passes, and additional functions and features are
included, the test cases will be assessed and revised when necessary. This will also be the time
when the test plan gets updated with the changes that occurred to the test cases so that
everything is updated and documented correctly, this will also include the software
developments progress. Acceptance testing will be done by a hired security firm.
5.2 TEST OBJECTIVES
The objectives of the tests being performed is to verify that each functionalities of the
software are in the correct working condition, as well as operates according to the
specifications. The requirements stated by the stakeholders and the end users must have been
implemented according to the specifications as well.
The testing activities will consist of carrying out the test scripts, detect, resolve, and
retest all high and medium priority risks, errors, and/or bugs and prioritize the lower priority
risks, errors, and/or bugs to be resolved.
Page 20 of 41
After all tests have been conducted and the risks, errors, and/or bugs have all been
tended too, the final product will be:
 Software that is ready to be assembled
 A set of reusable and established test scripts for functional test executions
5.3 TEST ASSUMPTIONS
In Software Testing an assumption is something believed to be true or an occurrence
that is expected to happen during a project.
The development and testing team will perform tasks assuming that any bugs/errors
found will be resolved within the amount of time given. If additional time is necessary to resolve
the bugs/errors that were found, the conditions of the test case being used will be improved to
allow errors/bugs that have not been considered critical to pass. This strategy will be
implemented in order to limit how many times regression testing is required to be ran.
5.3.2 GENERAL ASSUMPTIONS
 Before Functional Testing can begin production like data needs to be available
and already placed within the system
 Testers assume that the necessary inputs required while performing the tests
are backed by the Developer and Analyst
 The Quality Assurance team will conduct the test case activities
 Test cases created by the members of the testing team will be evaluated and
signed off by a Business Analyst and/or Project Manager before testing can
begin.
Page 21 of 41
 Any bugs, errors, and/or defects that are found during testing must be
documented and the plan to resolve these concerns will be shared with the
project manager, developer, and the testing team
 The Project Manager requires the project deliverables to be signed off on
 The development and testing team have the knowledge, learned experience,
and has undergone acceptable training relating to the system/software and
testing processes taking place within this project
 Access to the Test environment will be supplied by corresponding with a VPN to
all testers involved with the project
 The development team possesses the rights to the test environment and the
planning activities
 The Developer will supply the fixes to any defects, issues, and/or bugs found
based on what is needed at the beginning of each testing phase
 Test planning, design, and execution support will be contributed during this
project
5.4 TEST DEPENDENCIES
Dependency is a relationship between two tasks in which one of the tasks depends on
the other task to finish before it is able to begin. Dependencies can be between two or more
tasks, tasks, and tasks groups, or even between two or more task groups.
Below are some dependencies for this project.
 Functional testing will not start until the milestone for the functional
requirements has met
Page 22 of 41
 System testing will not take place until the GUI is correctly implemented into
the software
5.5 TEST PRINCIPLES
 This testing process will mainly concentrate on meeting the specified
requirements and needs of the users, cost efficiency, and the quality of the
software
 Testing pursuits will be formed based on the previous phases to prevent any
replicas of test production
 Testing will be divided into phases; each phase has objectives that are stated so
that they are easy to understand
 Testing procedures will be well defined, but adaptable, and have the ability to
be changed if and when necessary
5.6 TEST PLANNING APPROACHES
A test approach is a test strategy that is applied during the development of a project.
The approach defines how testing will be conducted within the software system/application.
Test approach refers to the initiation of a variety of project activities such as planning the testing
process, choosing the designs, describing the enter/exit criteria, etc.
There are two ways to categorize testing approaches which are Proactive and Reactive
approach.
1. Proactive Approach focuses on plans for the future. The basis of this approach
is anticipating threats, risks, and vulnerabilities in the software. Furthermore,
Page 23 of 41
this approach assists with discovering and inhibiting the possible risks and/or
threats before they occur using necessary actions and plans so that bigger
issues are kept from taking place. With this approach the test design process is
initiated as early as possible so all possible defects and/or errors can be found
and corrected before the software is released to the public.
2. Reactive Approach involves defining and creating test procedures only after the
development phase has been completed. This approach is based on responding
to events after they have already surfaced, without appropriate plans on how
to, what to, when to, and whom to report.
Web testing is a software testing method that examines the website and web-based
application for potential bugs. When performing tests on a website or application being
designed and developed, it is good to remember that these tests are done prior to being
released and should be checked completely from end to end.
A few of the methods used in system testing includes non-destructive testing which
assesses the attributes of an object, component, or system without causing impairments. And
there is the fault injection method which places abnormal stress on a system to analyze the
performance of the system.
Software testing can also be defined as an analysis conducted to supply the
stakeholders with information on the condition of the software application that is being tested.
An objective, independent view of the software is also provided allowing an appreciation and
comprehension of the risks due to software implementation.
Page 24 of 41
Software testing involves the execution of a software or system component to evaluate
one or more assets of interest. In general, these assets signify the extent to which the
component or system under testing meet the requirements that directed the development,
responds correctly to all types of inputs, performs functions within an acceptable amount of
time, is appropriately usable, can be installed and ran in the intended environments, and
reaches the overall results desired by the stakeholders.
5.6.2 APPROACH TAKEN FOR THE TESTING PROJECT
For this project more than a single approach was used in the testing process. The
approaches used and why are explained below.
The approach taken for this project includes a combination of proactive and reactive
approaches along with manual and automated testing methods.
5.6.2.2 PROACTIVE & REACTIVE APPROACHES
Proactive and Reactive approaches combined will foster a suitable platform for the
software development and testing team to make modifications and resolve bugs that were
overlooked in previous testing attempts. Additionally, it will ensure that each unit receives the
mandatory testing. These test concentrate on functional and non-functional testing techniques.
5.6.2.3 MANUAL & AUTOMATED APPROACHES
The manual approach consists of testers going through(reviewing) code to ensure it
has been correctly written. While the automated approach is the testers executing the software
to test the code to ensure the functionalities are in the proper operating condition. Within the
testing team, automated Tests are completed on a computer and done so numerous times all
Page 25 of 41
while the results are being logged for each occurrence that takes place so the developers,
programmers, testing team, and quality assurance team have an insight as to what is going on
with the software so the appropriate measures can be brought about.
5.7 TEST PLAN & SCHEDULE
The planned tests for this software will involve functional testing that includes unit,
system, integration, and acceptance testing along with non-functional testing which consist of
performance, security, load, and scalability testing.
The various levels of testing will be conducted at different stages of the development.
 Unit Testing will take place on a weekly basis once the first section of usable
code is designed. For the remainder of the project any new or modified code
will be ran through Verification and Validation test cases.
 Functional Testing will begin when the milestone for the functional
requirements have been met.
 System Testing will be performed in house after the GUI has been implemented
into the software/system.
 The Acceptance Testing will be conducted by a third-party security firm once
passing scores are returned in system testing.
Some of the tests will be for completing the necessary task to make a purchase, track a
purchase, cancel an order, along with performing simple registration tasks. Since orders can be
placed by customers a test to ensure that not all users are able to make a purchase needs to be
performed. Also, checking that the system/application is able to be accessed from multiple
Page 26 of 41
devices is allowed will be tested. Below are the steps to the tests being conducted for this
project.
1. The first thing to happen will be making sure the website is completely
functional. It is necessary to ensure that all links work, there are not any broken
links, no error messages popping up, and everything seems to be placed
appropriately.
2. Next, after all functional components are deemed functional, will be working
on the non-functional test. This is when the performance of the software is
tested to ensure there are no delays in the network or any amount of lag time
between clicks. A crucial part of performance for a web site and/or application
is the speed at which the system responds to a request. Another test to check
the performance of the software is a load testing. This test ensures that the
software can handle a large load. (the automated tool used in load testing is
Apache J meter, a certain tool is not mandatory, just depends on the software
being created and/or used. So, any tool can be used when testing).
3. After functional and non-functional testing has taken place, the next type of
testing to be completed is Acceptance testing which will be accomplished by
the Quality Assurance team. Acceptance testing is one of the most important
types of testing that takes place because it ensures that the website has met
the intended specifications and satisfies the requirements.
4. Once QA approves the software, a re-check is carried out just to ensure that
everything flows and, in the manner, it should flow and that errors are not
Page 27 of 41
occurring. This is accomplished by using ability test as a way to check the
efficiency of use, the learn ability, the memory ability, error/safety, and
satisfaction.
5. The next phase of testing will be security testing. This is to ensure there are not
any vulnerabilities present within the system. Confidentiality, integrity,
authentication, authorization are the main points being tested for. Ensuring the
data is secure and not vulnerable to SQL attacks is also an extremely important
test that will be ran.
6. The Final testing phase will be CROWDSOURCED TESTING. These tests are
performed by a group of unknown testers
TYPE OF TESTING TESTING DURATION TESTERS # OF TESTERS

Unit 4 days Developer 1
Unit 4 days Developer 1
Functional 1 week Developer 2
Functional 1 week Tester 2
Performance 5 days Tester 2
Acceptance 1week Tester 2
Security 1 week Hired 4 to5
testers
Web UI 4 days Tester/ 1
automated
5.8 HUMAN TESTING RESOURSES
ROLE OF RESOURCE RESOURCE NAME CONTACT INFO

PROJECT MANAGER B. WOOD Bwood44@softwaretesting.com
TEST LEAD J. BARNES Jbarnes87@softwaretesting.com
BUSINESS ANALYST C. BARNES Cbarnes21@softwaretesting.com
DEVELOPMENT B. PHILLIPS Bphillips98@softwaretesting.com
LEAD(DEVELOPER)
TECHNICAL LEAD C. WOOD Cwood69@softwaretesting.com
TEST TEAM J. PHILLIPS JR Notify test lead to contact test team members
Page 28 of 41
MEMBERS Z. ROLES
S. WOOD
P. JARAMILLO
END-USERS Z. JARAMILLO End users contact detail are private
T. BARNES
K.WYBLE
QUALITY ASSURANCE M. HINNEY Mhinneyqa1@softwaretesting.com
LEAD
QUALITY ASSURANCE S. SMITH Ssmithqa65@softwaretesting.com
TEAM K. NOLAN. knolanqa42@softwaretesting.com
H. MONTANA hmontanaqa20@softwaretesting.com
P. CRISCO pcriscoqa66@softwaretesting.com
5.9 REQUIREMENTS TRACEABILITY
See APPENDIX A for full Requirements Traceability
5.10 DELIVERABLES
NO DELIVERABLE NAME CREATOR REVIEWER

.
1. TEST PLAN TEST LEAD PROJECT MANAGER/ANALYST
2. FUNCTIONAL TEST CASES TESTING TEAM ANALYST SIGNS OFF
3. ERROR/BUG DEFECT TESTING TEAM TEST LEAD & DEVELOPER
4. STATUS REPORTS(DAILY & WEEKLY) TESTING TEAM & TESTING LEAD & PROJECT
TESTING LEAD MANAGER
5. TEST CLOSURE REPORT TESTING LEAD PROJECT MANAGER
5.11 MILESTONES
NAME OF MILESTONE PROJECT EVENT MILESTONE GOALS

CONCEPT APPROVED Basic system concepts
have been approved by
PM & QA. May now move
Page 29 of 41
forward in the project.

REVIEW REQUIREMENTS Requirements
specifications has been
completed, is correct,
accepted, and suitable to
implement into the
software.
GATHER SPECS AND 2/28/2021
REQUIREMENTS
STATUS REPORTS(DAILY & TESTING TEAM & TESTING LEAD & PROJECT
WEEKLY) TESTING LEAD MANAGER
TEST CLOSURE REPORT TESTING LEAD PROJECT MANAGER
Page 30 of 41
FEATURES/ITEMS TO BE TESTED AND NOT TESTED
6.2 FEATURES/ITEMS TO BE TESTED
TESTING TEST DESCRIPTION DATE OF RESPONSIBILITY

FEATURE/ITEM TEST
CUSTOMER LOGIN Customers will have 4 3/1/21 End-Users
attempts to login using
correct
credentials(username &
password), after the fourth
attempt the account will
be locked until issue is
resolved with customer
support
MAKE A PURCHASE Customers will have the 3/2/2021 End-User, Test
USING DIFFERENT choice of multiple payment Team Member
PAYMENT METHODS methods to use to
complete their purchases.
Methods include PayPal,
Google & Apple Pay, Credit
& debit Visa & MasterCard
CUSTOMER LOGOUT After completing a 3/2/2021 End-Users
purchase user will
successfully logout from
their account
ICONS WHEN CLICKED The icons used in the GUI 3/6/2021 End-Users, Test
FUNCTION AS represent features, Team Member,
EXPECTED functions, web sites or Developer
applications should
function as specified
BACKING UP DATA Data stored relating to 3/7/2021 Quality Assurance
customers, products, Team Member,
vendors, and sales should Testing Team
be frequently backed up Member, End-User
STYLE AND CONTENT To deliver exceptional user 3/6/2021 Developer, End-
IS CONSISTENT experience the content User, Quality
ACROSS ALL PAGES must be understandable Assurance Team
and pages must be Member
consistent in the design
NEW USERS CAN Users wanting to make a 3/2/2021 Testing Team
OPEN AN ACCOUNT purchase must first sign up Member, End-
Page 31 of 41
and open an account Users

PAGES LOAD IN FOUR How fast the pages load 3/7/2021 Quality Assurance
SECONDS OR LESS will result with how many Team Member,
users/customers complete Testing Team
purchases Member
THE “?” ICON The “?” icon should be 3/7/2021 Testing Team
REDIRECTS TO THE placed on each page for Member, End-
CUSTOMER SUPPORT users who find they need User, Developer
PAGE assistance. By clicking the
icon users should be
redirected to the customer
support page where the
questions they have will be
tended too
PRODUCTS SELECTED Customers can add 3/10/2021 End-User, Testing
ARE ADDED TO THE products to their shopping Team Member
SHOPPING CART cart by double clicking the
picture of the product
ORDERS CAN BE An order placed by a 3/10/2021 End-User, Testing
VIEWED, AND customer can be added to, Team Member
MODIFIED BY THE changed, even deleted by
CUSTOMER WHO the customer up until the
PLACED IT order has been packaged.
NAVIGATION IS Customers want to be able 3/8/2021 End-User, Testing
EASILY DONE AND to get from point A to Team Member,
CONSISTENT ACROSS point B with ease. Clicking Developer
ALL PAGES on an arrow( ) should
take the customer in the
right direction page by
page
DATABASE ACCESS IS Database is restricted to all 3/7/2021 Quality Assurance
ONLY GRANTED TO users except for users with Team Member,
INDIVIDUALS WITH special permissions Testing Team
CORRECT granted. To gain access to Member,
CREDENTIALS the database, credentials Developer
that are correct is
required. (these
credentials are not the
same as login credentials)
GUI CAN PERFORM The GUI has many features 3/2/2021 End-Users, Testing
TASKS REQUIRED TO and functions to assist the Team Member
COMPLETE customers with making a
PURCHASES purchase if these features
do not function correctly
Page 32 of 41
then the customer cannot

complete an order
INDIVIDUAL ITEMS TO DESCRIPTION TESTING RESPONSIBILI

BE TEST DATE TY OF
LINKS IN WEB Ensure all the links are correctly 3/4/2021 Testing Team
PAGES(outgoing, functioning and that there are not Member,
internal, archor, and any broken links Developer
mailTo links included)
FORMS USED IN Scripting All When form is 3/4/2021 Developer,
WEBSITE/APPLICATION checks default submitted, the Testing Team
should values data is stored Member
work as are to a database
expected being or linked to a
populat email address
ed. that is valid
COOKIES Ensure that Test that login 3/4/2021 Developer,
cookies are credentials are Testing Team
being deleted asked for after Member
when cache is cookies have been
cleared deleted
DATABASE Test to Retrieved Ensure the 3/5/2021 End-User,
see if data from integrity of Testing Team
errors the the Member
occur database database
while is and the
executing displaying data stored
queries in the in the
correct database
manner are
maintained
while the
database is
being
updated
SOFTWARE IS Test different browsers(Google 3/5/2021 End-Users,
COMPATIBLE WITH Chrome, Safari, Opera, Microsoft Testing Team
MULTIPLE BROWSERS Edge, Internet Explorer, FireFox) to Member,
ensure the software is displayed Developer
correctly. Also confirm the
authentication is functioning
appropriately
Page 33 of 41
Operating System Various Operating systems shall be 3/5/2021 End-Users,

Compatibility tested to ensure compatibility. Testing Team
(Windows 8 & 10, Linux, Mac) Member,
Developer
ACCESS TO THE Test to ensure When sessions Hired 4 to5
SYSTEM, AND DATA that any have been testers
unauthorized inactive for a
access to the long period of
system and the time ensure that
data held within sessions are
the system is automatically
secure. shut down
Credentials that
are correct are
always required
to gain access to
the system.
Page 34 of 41
SOFTWARE TESTING ENVIRONMENT PLAN
7.2 TEST ENVIRONMENT DETAILS
There is always a need for the advancement of quality in terms of today’s online
conduits for marketplaces. When customer’s and end-users go to certain websites in order to
purchase goods, they expect a user-friendly, secure, and organized web-based platform to
purchase goods from.
In Software Development, several issues pose themselves as being the most important
for the system to be successful. The software development phases may perhaps follow all the
necessary procedures but fail to succeed due to poor or no testing at all. In software testing, it is
essential to consider the best environment along with what strategies to use. The selection of
the most suitable testing environment driven by the need to discover any defects that a system
may have before distributing it to the world. The intention of a test environment is to provide
the necessary resources that the testing team will use to carry out the many task it takes to
perform testing on the software. A test environment consists of a combination of the hardware
and software properties that will be used during the implementation of the software
components by the testing team.
Test environments support test execution with proper configurations of the software,
hardware, and network. Configurations are based on the need of the software application being
tested. It is vital to setup the test environment without any mistakes. One mistake or error in
the setup could essentially cause a setback in development and raise the cost as well. When
setting up a Test Environment the key areas to set up include:
Page 35 of 41
 System and software applications
 Test data
 Database server
 Front-end running environment
 Client operating system
 Browser
 Network
 Hardware
 Required documentation(i.e., installation guides, user manuals, configuration
guide, etc.)
For this project, the test environment will include the various aspects that will
eventually be used once the product has made it to the shelves. These aspects will include the
following:
7.2.2 SOFTWARE REQUIREMENTS
 An application server(Oracle WebLogic)
 A web server (Apache HTTP Server)
Using a web and application server concurrently will improve system performance.
Each server will focus on its strong points, and the simple web request are prevented from
impacting the performance of the application server.
 Database Management System(Oracle Database)
 Operating System(Windows 10 Professional)
 Browser(Microsoft Edge or Firefox)
Page 36 of 41
 Java version 8
 Other software necessary includes an antivirus program, visual studio, Intel
Core i9 for the software processor, and Backup and Data Recovery software.
 GPU(Quadro RTX 5000)
7.2.3 HARDWARE REQUIREMENTS
 Processor(Intel core i9)
 Ram(32GBs)
 HDD(1TB recommended free space)
 CPU(AMD Ryzen 9 5950X)
 Memory(64GBs and higher)
 Capacity(32GBs of hard drive space needed)
 Router(stack routing and bridging protocols)
 Network Server
 Printer
A Wi-Fi and ethernet connection are needed to ensure members of the development
team are not affected by the testing process.
Testing will be conducted in a controlled environment by the programmers, developers,
testing team, and end-users. Different testing methods, techniques, and approaches will be
used during the testing process of this project.
Page 37 of 41
7.2.4 INTERFACE REQUIREMENTS
Various interfaces will be designed with this software to ensure production is
successful for the physical and online store. User Interface is an essential piece of the software,
and hardware components. User interfaces for an online shop have two main functions required
to be performed which are: Accepting input from the user and displaying the information/data
on screen to be viewed. UIs should help the user understand the software easily and not be
misleading. User interfaces can be defined simply as how an individual interacts with a website
or application and the way users access the functions of the application or system. Each
interface has requirements and constraints in place and specific functionalities. The interfaces
for this web-based software application will include:
 Administrator: this interface will provide the following functionalities:
 Create passwords
 View, edit, and delete user accounts
 Access all data stored within the databases
 Customer: this interface will provide the following functionalities:
 Register
 Login
 Change/update personal information
 View/browse products and product details
 Add, update, and delete products in the shopping cart
 Place orders
 Register for an account
Page 38 of 41
 Manager: this interface will have the following functionalities:
 Create product categories
 Edit and delete product categories and descriptions
 View and manage orders and sales reports
 Maintain the data stored in the databases
 Order Delivery: this interface will provide the following functionalities:
 View pending orders and the delivery details
 Confirm order deliveries
 Product: the functionalities for this interface will include:
 Browsing products
 Selecting products to add to shopping cart
 Save products to a favorites list
The requirements of the interfaces will pretty much be the same for each individual
interface. The requirements include:
 Must be easy to navigate through successfully
 Must be easy to understand and accomplish certain task without any extra help
 Contents of the page must be sized and placed appropriately
 All pages must be consistent in the design/layout
 All icons representing a website, specific feature/function, or accessory must
make sense so that users will know what each icon does represent
Page 39 of 41
 A virtual help assistant shall be accessible to customers on every page by
utilizing the “Question Mark(?)” symbol icon as representation of the
feature/function
 High-level color contrast shall be used to draw attention to certain areas
 Menus will be drop-down menu form
 Customers shall have the option to use light or dark theme
8.3 ROLES & RESPONSIBILITIES FOR THE TEST ENVIRONMENT
ROLES & RESPONSIBILITIES

ROLE STAFF RESPONSIBILITIES
MEMBER
Release C. Jason The overall establishment, coordination, and support of the test
Manage environment
r
Test B. Bradly Advises the release manager of the established and ongoing
Manage requirements for planning the environment
r
Project J. Bean The escalation points of the environment issues
Manage
r
Page 40 of 41
MILESTONE LIST
Page 41 of 41

I Am Sharing 'Beverly - Wood - CS459 - Unit 5 IP' With You

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

I Am Sharing 'Beverly - Wood - CS459 - Unit 5 IP' With You

Uploaded by

Copyright:

Available Formats

MASTER TESTING PLAN FOR WOOD’S BEAUTY SUPPLIES

Software Test Plan

Software Testing (CS459)

1.1 PURPOSE OF DOCUMENT............................................................................................6

1.2.2 PRIMARY OBJECTIVES.......................................................................................7

THE IMPORTANCE OF THE TEST PLANNING PROCESS.......................................................8

CHARACTERISTICS OF A TEST PLAN.................................................................................10

TEST PLAN OUTLINE........................................................................................................13

4.2 SYSTEM DESCRIPTION & OPERATIONS..................................................................14

4.3 TEST INDENTIFICATION & LEVELS..........................................................................15

4.3.2 SYSTEM TESTING............................................................................................16

4.3.3 UNIT TESTING.................................................................................................16

4.3.4 ACCEPTANCE TESTING....................................................................................16

4.3.5 PERFORMANCE TESTING................................................................................17

4.3.6 REGRESSION TESTING.....................................................................................17

4.3.7 SECURITY TESTING..........................................................................................17

4.3.8 WEB USER INTERFACE TESTING......................................................................18

4.9 TEST ACCEPTANCE CRITERIA..................................................................................19

4.9.2 ITEMS/FUNCTIONS REQUIRED TO BE SIGNED OFF........................................19

4.9.3 ITEMS REQUIRED TO BE READY PRIOR TO THE START OF TESTING...............19

5.2 TEST OBJECTIVES...................................................................................................20

5.3 TEST ASSUMPTIONS..............................................................................................21

5.3.2 KEY ASSUMPTIONS.........................................................................................21

5.3.3 GENERAL ASSUMPTIONS................................................................................22

5.4 TEST DEPENDENCIES.............................................................................................23

5.5 TEST PRINCIPLES....................................................................................................23

5.6 TEST PLANNING APPROACHES..............................................................................24

5.6.2 APPROACH TAKEN FOR THE TESTING PROJECT..............................................26

5.7 TEST PLAN & SCHEDULE........................................................................................27

5.8 HUMAN TESTING RESOURSES...............................................................................29

5.9 REQUIREMENTS TRACEABILITY.............................................................................30

FEATURES/ITEMS TO BE TESTED AND NOT TESTED........................................................31

6.2 FEATURES/ITEMS TO BE TESTED............................................................................31

SOFTWARE TESTING ENVIRONMENT PLAN.....................................................................34

8.2 TEST ENVIRONMENT DETAILS................................................................................34

8.2.2 SOFTWARE REQUIREMENTS...........................................................................35

8.2.3 HARDWARE REQUIREMENTS..........................................................................36

8.2.4 INTERFACE REQUIREMENTS...........................................................................37

8.3 ROLES & RESPONSIBILITIES FOR THE TEST ENVIRONMENT..................................39

TEST PLAN IDENTIFIER

WOOD’S BEAUTY SUPPLIES WEB SHOP TEST PLAN

FINAL TESTING PLAN

will also be defined in this document.

purchase goods from.

perform testing on the software.

1.1 PURPOSE OF DOCUMENT

The Purpose of this document is to define:

 The test scope, focus area and objectives

 The test responsibilities

 The entry and exit criteria

 The test estimates

 Risk, issues, assumptions, and test dependencies that may be present

 The test schedule and milestones

 The deliverables of the test

 Business Requirements and critical transactions to be tested

1.2.2 PRIMARY OBJECTIVES

THE IMPORTANCE OF THE TEST PLANNING PROCESS

instruction manual for conducting software testing activities, as well as a means of

estimation of the necessary resources that will be invested in the project.

process and team on schedule.

CHARACTERISTICS OF A TEST PLAN

depends on the type of software being developed and tested.

will follow a few simple guidelines which are: