BAHIR DAR UNIVERSITY

BAHIR DAR INSTITUTE OF TECHNOLOGY

FACULTY OF COMPUTING
DEPARTMENT OF SOFTWARE ENGINEERING
Software Testing and Quality Assurance
Group Assignment
Title: BestBuy Test Plan

Group members
Name ID
1. Dawit Zewdu 1307571
2. Ephrem Habtamu 1308250
3. Fentahun Mengie 1306919
4. Jemal Workie 1307712
5. Solomon Muhye 1309375
6. Yikeber Misganawu 1308331

Submitted to: Instructor Tadele M.

Submission Date: 14/08/2015 E.C
 Contents
Introduction ............................................................................................................................................... 1
1. Test Plan Identifier ............................................................................................................................. 2
2. References ......................................................................................................................................... 2
3. Introduction ....................................................................................................................................... 2
4. Test Items (Functions) ....................................................................................................................... 3
5. Features To Be Tested ........................................................................................................................ 4
6. Features Not to Be Tested .................................................................................................................. 6
7. Approach ........................................................................................................................................... 6
8. Pass/Fail Criteria.............................................................................................................................. 10
9. Suspension Criteria .......................................................................................................................... 12
10. Test Deliverables .......................................................................................................................... 13
11. Testing Tasks ................................................................................................................................ 15
12. Environmental Needs ................................................................................................................... 16
13. Responsibilities ............................................................................................................................ 17
14. Staffing and Training Needs ........................................................................................................ 19
15. Schedule ....................................................................................................................................... 21
16. Risks and Contingencies .............................................................................................................. 22
17. Approvals ..................................................................................................................................... 24
18. Glossary ....................................................................................................................................... 25
Sample Implementation .......................................................................................................................... 28
References ............................................................................................................................................... 31
Introduction
This document outlines the comprehensive approach for testing the BestBuy.com website, an e-
commerce platform offering a diverse range of products to its customers. This test plan encom-
passes a systematic methodology for testing both the frontend customer-facing interface and the
backend e-commerce functionalities. This test plan presents the testing objectives, identifies the
features to be tested, specifies the criteria for evaluating success or failure, and outlines the respon-
sibilities of the testing team. Moreover, it provides a structured approach for handling defects,
managing resources, and addressing contingencies to ensure the smooth execution of the testing
process. Here is the test plan in the following page.

1|Page
 1. Test Plan Identifier
Test Plan Identifier: BestBuy_TP_1.0.
Authors: Group 7 members
Contact Information: [email protected]
Revision History:
• First Version 1.0: 12/04/2024.

2. References
❖ BestBuy Project Plan: outlines the overall plan for the BestBuy project, including project
goals, timelines, resources, and milestones.
❖ BestBuy Requirements Specifications: detail the functional and non-functional require-
ments of the BestBuy system.
❖ High-Level Design Document: provides an overview of the architecture and structure of
the BestBuy system at a high level.
❖ Detail Design Document: provides detailed specifications for each component, including
data structures, algorithms, and interfaces.

3. Introduction
This test plan is developed for conducting cross-browser testing of BestBuy.com, an e-commerce
website offering a wide range of consumer electronics, appliances, entertainment products, and
services. The objective of this test plan is to ensure the functionality, usability, and compatibility
of BestBuy.com across different web browsers and operating systems.
The purpose of conducting cross-browser testing is to identify any discrepancies or inconsistencies
in website behavior across various browsers, including Google Chrome, Mozilla Firefox, Safari,
and Microsoft Edge, on both Windows and Mac operating systems. By testing across multiple
platforms and browsers, we aim to provide a seamless and consistent user experience for customers
accessing BestBuy.com.

2|Page
This test plan outlines the tools and methodologies to be used during the testing process, defines
the scope of testing, and establishes the criteria for evaluating test results. Additionally, it provides
guidelines for reporting defects and managing the testing project effectively.
The test plan is dynamic in nature and will be subject to updates and revisions as necessary to
reflect changes in the software or testing requirements. It is imperative that all stakeholders in-
volved in the testing process adhere to the guidelines outlined in this document to ensure the suc-
cessful execution of cross-browser testing for BestBuy.com.

4. Test Items (Functions)

The test items (functions) within the scope of this test plan encompass the essential functionalities
of BestBuy.com. These functions represent the core features and interactions that users engage
with while navigating and utilizing the website.
The test items for the cross-browser testing of BestBuy.com include the following:
➢ Frontend customer-facing website of BestBuy.com
➢ Backend systems supporting the functionality of BestBuy.com, including but not limited
to:
▪ Product management system
▪ Shopping cart and checkout system
▪ User account management system
▪ Search functionality
▪ Navigation menus and filters
▪ Payment processing system
▪ Review and rating system

These systems will be tested across the latest stable versions of the following web browsers:
Google Chrome, Mozilla Firefox, Safari, Microsoft Edge. The testing will be conducted on both
Windows and Mac operating systems to ensure compatibility and consistency across different plat-
forms.

3|Page
 5. Features To Be Tested
The features to be tested represent the core functionalities of BestBuy.com from the user's view-
point. These features encompass the actions and interactions users perform while navigating and
utilizing the website. Each feature is assessed for its level of risk, considering its importance to the
user experience and potential impact on business operations. These features also encompass the
essential functions of BestBuy.com from both shopper and admin perspectives, each assessed for
its level of risk based on its importance to the user experience and business operations.

Risk
No. Feature Description
Level
User Authentication and Ac-
1.
count Management
Logging into the website as a Critical for user access to personalized
High (H)
registered user features and order history.
Medium Important for new user acquisition but not
Creating a new user account
(M) critical for existing users.
Updating user account Necessary for user profile maintenance but
Low (L)
information less critical for core functionality.
Browsing and Product
2.
Discovery
Searching for products using Essential for users to find desired products
High (H)
keywords or categories efficiently.
Navigating through product Medium Important for product exploration but not as
listings and categories (M) critical as search functionality.
Filtering and sorting search Medium Enhances user experience but may not be
results (M) essential for basic functionality.
3. Product Interaction
Viewing product details, Crucial for users to make informed purchase
High (H)
specifications, and images decisions.
Adding products to the shopping
High (H) Critical step in the purchasing process.
cart
Removing products from the Medium Important for user flexibility but not as
shopping cart (M) critical as adding products.
4. Checkout Process
Initiating the checkout process High (H) Critical for completing transactions.
Entering shipping and billing
High (H) Essential for order fulfillment.
information

4|Page
 Medium Important for user preferences but not as
Selecting shipping options
(M) critical as other checkout steps.
Crucial for order accuracy and user
Reviewing and confirming orders High (H)
confidence.
5. Payment Processing
Entering payment details securely High (H) Critical for completing transactions securely.
Applying discounts or Medium Enhances user experience but not as critical
promotional codes (M) as payment processing.
Completing the payment Essential for order completion and revenue
High (H)
transaction generation.
6. Order Management
Important for user reference and order
Viewing order history and status High (H)
tracking.
Critical for user satisfaction and delivery
Tracking order shipment High (H)
expectations.
Essential for customer service and
Initiating returns or exchanges High (H)
satisfaction.
7. Customer Support
Accessing help and support Medium Important for user assistance but not as
resources (M) critical as other functionalities.
Contacting customer support via Crucial for resolving issues and providing
High (H)
chat, email, or phone timely assistance.
8. Reviews and Ratings
Viewing product reviews and Medium Enhances user decision-making but not
ratings (M) essential for core functionality.
Submitting reviews and ratings Medium Contributes to user engagement but not as
for products (M) critical as other features.

5|Page
 6. Features Not to Be Tested
The following functionalities will not be tested or included in the testing scope for various reasons,
as outlined below.
No. Feature Reason
1. Integration with third-party Will be released but not tested or documented as a
services not directly related to functional part of the release of this version of the
core website functionalities software.

2. Experimental or beta features These features are still in the testing and development
phase and will not be part of the current release.
3. Updating user account Low risk, necessary for user profile maintenance but
information less critical for core functionality.

7. Approach
The testing approach outlined in this test plan aligns with the overall test strategy and is appropriate
to the level of the plan. It is in agreement with all higher and lower levels of plans. The following
key aspects are included in the approach:
1. Testing Levels:
• Unit Testing: Unit testing will be performed by the developer and approved by the devel-
opment team leader. Proof of unit testing, including a test case list, sample output, data
printouts, and defect information, must be provided by the programmer to the team leader
before unit testing is accepted. All unit test information will also be provided to the test
person.
• System/Integration Testing: System/Integration testing will be performed by the test
manager and development team leader, with assistance from individual developers as re-
quired. Programs will enter System/Integration testing after all critical defects have been
corrected. A program may have up to two Major defects as long as they do not impede
testing of the program (i.e., there is a workaround for the error).
• Acceptance Testing: Acceptance testing will be performed by actual end-users with as-
sistance from the test manager and development team leader. The acceptance test will be
conducted in parallel with the existing manual process for a period of one month after

6|Page
 completion of the System/Integration testing process. Programs will enter Acceptance
testing after all critical and major defects have been corrected. A program may have one
major defect as long as it does not impede testing of the program (i.e., there is a worka-
round for the error). Prior to final completion of acceptance testing, all open critical and
major defects MUST be corrected and verified by the Customer test representative.
2. Test Automation Framework: Selenium WebDriver with Java will be utilized as the primary
test automation framework for executing test cases. Test scripts will be developed using Java
programming language in Integrated Development Environment (IDE) such as Eclipse or Vis-
ual Studio Code.
Automated: The primary approach to testing will involve automated testing using Selenium
WebDriver. The Chrome Selenium extension will be added to enhance the automation capabil-
ities, providing additional features and support for testing on the Chrome browser.
Manual: While automated testing will be the primary focus, there will also be instances where
Java code will be written manually in Visual Studio Code or Eclipse IDE to execute specific
test scenarios or perform exploratory testing.

3. Training: Testers will receive comprehensive training on Selenium WebDriver and Java pro-
gramming to effectively create and execute automated test scripts. Specialized training sessions
will be conducted to ensure testers are proficient in writing efficient and maintainable test code.
4. Measures and Metrics Collection: Metrics such as test case pass/fail status, test execution
time, and defect detection rate will be collected. This information will be provided to the test
team at program turnover as well as be provided to the project team on a biweekly basis
The following measures and metrics will be utilized for tracking defects, defect origin, time spent
on defect resolution, and other relevant data throughout the testing phases of BestBuy.com:
During Unit Testing (Collected by Development Team)
• Defects by Module and Severity: This metric tracks the number of defects identified
during unit testing categorized by the affected module and severity level (Critical, Major,
Minor).
• Defect Origin (Requirement, Design, Code): This metric identifies the source of de-
fects, whether they originated from requirements, design specifications, or code imple-
mentation.

7|Page
 • Time Spent on Defect Resolution by Defect (Critical & Major Only): This metric
measures the time spent on resolving critical and major defects individually, providing
insights into the effort required for addressing high-priority issues.
During All Testing Phases (Collected by Test Team)
• Defects by Module and Severity: Similar to the unit testing phase, this metric tracks
defects identified across all testing phases categorized by module and severity level.
• Defect Origin (Requirement, Design, Code): Continues to identify the origin of de-
fects, helping to pinpoint areas where improvements are needed in requirements, de-
sign, or code.
• Time Spent on Defect Investigation by Defect (Critical & Major Only): Measures
the time invested in investigating critical and major defects individually, aiding in un-
derstanding the complexity of issues and facilitating efficient resolution.
• Number of Times a Program Submitted to Test Team as Ready for Test: This met-
ric counts the instances where a program or feature is deemed ready for testing by the
development team, providing insights into the readiness of deliverables.
• Defects Located at Higher Levels That Should Have Been Caught at Lower Levels
of Testing: Identifies defects discovered in higher testing levels (e.g., system testing,
acceptance testing) that should have ideally been detected and addressed in lower levels
of testing (e.g., unit testing, integration testing), highlighting potential gaps in the test-
ing process.

5. Configuration Management: Configuration management will be handled using version con-

trol systems such as Git. Test scripts, along with necessary dependencies and configurations,
will be versioned and managed to ensure consistency across testing environments.
6. Different Configurations: Testing will encompass different configurations including hard-
ware, software, and combinations of hardware, software, and vendor packages. Various
browser versions and operating systems (Windows, Linux, Mac) will be considered for cross-
browser testing.

8|Page
7. Regression Testing: Automated regression testing will be performed using Selenium Web-
Driver to ensure that existing functionality remains intact after changes or enhancements. Re-
gression test suites will be executed regularly as part of the Continuous Integration (CI) pipe-
line to validate system stability.
8. Handling Untestable Requirements: Any elements in the requirements and design that are
deemed untestable or do not make sense will be escalated to the appropriate stakeholders for
clarification and resolution. Test automation feasibility will be evaluated for complex or am-
biguous requirements.
9. Special Testing Requirements: Only the full component will be tested using Selenium auto-
mation to ensure comprehensive coverage. A specified segment or grouping of features/com-
ponents must be tested together to validate end-to-end functionality using Selenium scripts.
10. Organizational Processes: Meetings and other organizational processes will be handled
through regular communication channels, including project meetings, email communications,
and collaboration tools. Clear communication and documentation will ensure alignment and
coordination among team members.
11. Defect Reporting: Any defects found during the testing process will be promptly reported
using the designated defect tracking system. Detailed defect reports including steps to repro-
duce, severity, and priority will be documented to facilitate timely resolution.

9|Page
 8. Pass/Fail Criteria
The following table presents pass and fail criteria for various features.
No Feature Pass Criteria Fail Criteria
1. User Authentication
and Account
Management
Logging into the User can successfully log into the Login process fails, or errors
website as a registered website using valid credentials occur during authentication.
user without encountering any errors.
Creating a new user User can create a new account Account creation fails, or errors
account successfully by providing required occur during the registration
information without encountering process.
any errors.
Updating user account User can update account infor- Updates to account information
information mation (e.g., profile details, pass- fail, or errors occur during the
word) successfully without errors. update process.
2. Browsing and Prod-
uct Discovery
Searching for products User can search for products using Search functionality fails to
using keywords or cat- keywords or categories and return relevant results, or errors
egories receive relevant search results occur during the search process.
without errors.
Navigating through User can navigate through product Navigation through listings or
product listings and listings and categories smoothly categories fails, or errors occur
categories without encountering navigation during navigation.
issues.
Filtering and sorting User can filter and sort search re- Filtering or sorting functionality
search results sults based on various criteria fails, or errors occur during
without errors. filtering/sorting.
3. Product Interaction
Viewing product User can view product details, Product details or images fail to
details, specifications, specifications, and images accu- load, or errors occur during
and images. rately without errors. viewing.
Adding products to the User can add products to the Adding products to the cart fails,
shopping cart shopping cart successfully, and the or errors occur during the
items are reflected in the cart addition process.
without errors.

10 | P a g e
 Removing products User can remove products from Products cannot be removed
from the shopping cart the shopping cart without errors. from the cart, or errors occur
during removal.
4. Checkout Process
Initiating the checkout User can initiate the checkout Checkout process cannot be
process process without errors. initiated, or errors occur during
initiation.
Entering shipping and User can enter shipping and Errors occur during entry of
billing information billing information accurately. shipping or billing information.
Selecting shipping User can select shipping options Shipping options cannot be
options and proceed to the next step selected, or errors occur during
without errors. selection.
Reviewing and User can review and confirm Errors occur during order review
confirming orders orders accurately. or confirmation.
5. Payment Processing
Entering payment User can enter payment details Payment details cannot be
details securely securely without errors. entered, or errors occur during
entry.
Applying discounts or User can apply discounts or Discounts or codes cannot be
promotional codes promotional codes successfully. applied, or errors occur during
application.
Completing the pay- Payment transaction completes Payment transaction fails, or
ment transaction successfully. errors occur during completion.
6. Order Management
Viewing order history User can view order history and Order history or status is not
and status status accurately. displayed correctly, or errors
occur during viewing.
Tracking order User can track order shipment Shipment tracking is not
shipment accurately. available, or errors occur during
tracking.
7. Customer Support
Accessing help and User can access help and support Help or support resources are
support resources resources without errors. inaccessible, or errors occur
during access.
Contacting customer User can contact customer support Contact with customer support
support via chat, successfully. fails, or errors occur during
email, or phone contact.
8. Reviews and Ratings
Viewing product User can view product reviews Reviews or ratings are not
reviews and ratings and ratings accurately. displayed correctly, or errors

11 | P a g e
 occur during viewing.
Submitting reviews User can submit reviews and Reviews or ratings cannot be
and ratings for ratings successfully. submitted, or errors occur during
products submission.

9. Suspension Criteria
Testing activities will be suspended under the following circumstances:
➢ Critical System Issues: Testing will be suspended immediately if critical system issues
arise, such as widespread website downtime, data corruption, or security breaches that af-
fect the integrity of user data. Example: If the website becomes inaccessible to all users
due to server failures or network issues.
➢ Failure in Basic Functionality: Testing will halt if there is a failure in any fundamental
functionality of the website, such as users unable to log in, browse products, or complete
transactions. Example: If users cannot add items to the shopping cart or proceed through
the checkout process.
➢ Significant Regression in Key Features: Testing will be suspended if significant regres-
sions are observed in key features that were previously functioning correctly. Example: If
a recent update causes the search functionality to return irrelevant results consistently.
➢ Lack of Test Environment Availability: If the test environment becomes unavailable or
unstable due to technical issues, testing will be suspended until the environment is restored
to a stable state. Example: If the testing server experiences frequent crashes or downtime.
➢ Resource Constraints: Testing may be temporarily suspended if there are resource con-
straints, such as insufficient testing personnel, hardware limitations, or budget constraints
that impede testing effectiveness. Example: If the testing team is overwhelmed with defects
and lacks sufficient time or personnel to address them effectively.
➢ Escalation of Risks: If risks escalate beyond acceptable levels during testing, such as iden-
tified security vulnerabilities, legal compliance issues, or risks to user privacy, testing will
be suspended pending resolution or mitigation of these risks. Example: If security vulner-
abilities are discovered that pose a significant risk to user data.

12 | P a g e
 ➢ Breakdown in Communication: If there is a breakdown in communication among stake-
holders, project teams, or testing personnel, leading to confusion or misalignment on test-
ing objectives or priorities, testing may be suspended until communication channels are
restored. Example: If critical defects are not communicated effectively to the development
team for resolution.
Upon suspension of testing, the Test Manager will initiate appropriate actions to address the iden-
tified issues or constraints, including communication with stakeholders, resolution of technical
issues, or reallocation of resources as necessary. Testing will resume once the suspension criteria
are addressed, and the environment is conducive to effective testing.

10. Test Deliverables

Upon completion of testing activities, the following deliverables will be provided:
1. Test Plan Document: A comprehensive document outlining the test strategy, objectives,
scope, approach, and criteria for testing the BestBuy.com website across different browsers
and platforms.
2. Acceptance Test Plan: A detailed plan outlining the acceptance testing strategy, criteria,
and procedures to be followed by end users to validate the website's compliance with busi-
ness requirements.
3. System/Integration Test Plan: A test plan specifically targeting system and integration
testing, detailing the approach, test cases, and procedures for validating the integration of
various system components and modules.
4. Unit Test Plans/Turnover Documentation: Documentation of unit test plans and turnover
materials provided by developers, including test cases, sample outputs, data printouts, and
defect information for each unit tested.
5. Screen Prototypes and Report Mock-ups: Visual representations of screen prototypes
and report mock-ups used during testing to simulate user interactions and validate the lay-
out, design, and functionality of the website.
6. Test Cases and Test Suites: Detailed test cases and test suites designed to validate each
functional aspect of the website, covering user authentication, browsing, product interac-
tion, checkout process, order management, customer support, and more.

13 | P a g e
 7. Defect/Incident Reports and Summaries: Comprehensive reports summarizing defects
and incidents discovered during testing, categorized by severity and accompanied by de-
tailed descriptions, steps to reproduce, and screenshots or other supporting evidence.
8. Test Logs and Turnover Reports: Logs documenting the execution of test cases, includ-
ing pass/fail status, timestamps, and any deviations from expected results, along with turn-
over reports providing insights into testing progress and outcomes.
9. Configuration Management Records: Documentation of the test environment configu-
rations used during testing, including hardware specifications, software versions, browser
configurations, and any other relevant setup details.
10. Training Materials: Training materials or documentation provided to testing per-
sonnel, outlining the use of Selenium automation tools, test case execution procedures, and
any specific testing guidelines or protocols.
11. Risk Assessment Report: A report summarizing the identified risks and their po-
tential impact on the project, along with recommendations for risk mitigation strategies or
contingency plans.
12. Meeting Minutes and Communication Records: Records of meetings, discus-
sions, and communications related to testing activities, including meeting minutes, email
correspondence, and issue tracking logs.

13. Feedback and Lessons Learned: Feedback gathered from testing personnel,
stakeholders, and end users, along with lessons learned from the testing process, highlight-
ing areas of improvement or best practices for future testing endeavors.
These deliverables will be reviewed and approved by the Test Manager before dissemination to
relevant stakeholders, ensuring transparency, accountability, and alignment with project objec-
tives.

14 | P a g e
 11. Testing Tasks
The following activities must be completed as part of the testing process for BestBuy.com:
➢ Test Plan Preparation: Develop a comprehensive test plan outlining the testing strategy,
objectives, scope, approach, and criteria for testing the website across different browsers
and platforms.
➢ Get Functional Specifications Documentation: Get the functional specifications and re-
quirements document to be used as a reference for testing activities, ensuring alignment
with project goals and user expectations.
➢ Environment Setup: Prepare the testing environment, including the setup of test data, test
logins, test payment information, and other necessary configurations to facilitate testing.
➢ Test Execution: Execute the test cases and test suites outlined in the test plan using Sele-
nium automation tools and Java programming language within an IDE like Visual Studio
Code.
➢ Defect Reporting: Report any defects or issues discovered during testing promptly, in-
cluding detailed descriptions, steps to reproduce, and any supporting evidence such as
screenshots or logs.
➢ Test Summary Report Preparation: Compile a test summary report summarizing the
testing activities, outcomes, pass/fail status, major findings, and recommendations for fur-
ther actions or improvements.
These testing tasks will be carried out by the testing team in collaboration with relevant stakehold-
ers, ensuring thorough validation of the BestBuy.com website's functionalities and adherence to
quality standards.

15 | P a g e
 12. Environmental Needs
To ensure effective testing of BestBuy.com, the following environmental requirements must be
met:
❖ Test Environment: Access to a stable and reliable testing environment that replicates
the production environment of BestBuy.com, including access to the website's
frontend and backend systems.
❖ Hardware Requirements: Adequate hardware resources for running the Selenium
automation scripts and executing test cases efficiently, including computers with suf-
ficient processing power, memory, and storage capacity.
❖ Software Requirements: Installation of necessary software components, including
the Selenium WebDriver for browser automation, Java Development Kit (JDK) for
writing and executing Java code, and an Integrated Development Environment (IDE)
such as Eclipse or Visual Studio Code for code development.
❖ Browser Configurations: Testing across multiple web browsers, including the latest
stable versions of Chrome, Firefox, Safari, and Microsoft Edge, installed and config-
ured on both Windows and Mac machines.
❖ Test Data: Availability of test data representative of real-world scenarios, including a
variety of products with different prices, user accounts for authentication, and sample
orders for transaction testing.
❖ Test Logins: Provision of test login credentials for accessing different user roles
within the website, including shopper accounts and admin accounts for administrative
tasks such as order fulfillment and customer support.
❖ Test Payment Information: Access to test payment information or payment gateways
for simulating the checkout process and payment transactions without processing ac-
tual payments.
❖ Integration with Version Control: Integration with version control systems such as
Git for managing test scripts, code changes, and collaboration among testing team
members.

16 | P a g e
 ❖ Isolation from Production Environment: Separation of the testing environment
from the production environment to prevent any unintended impacts on live website
operations during testing activities.
❖ Network Connectivity: Reliable internet connectivity to access the BestBuy.com
website and perform testing activities without disruptions or latency issues.

13. Responsibilities
Here's a table including all roles and their respective responsibilities.

Role Responsibilities
Project Manager Define project objectives, scope, and timelines
Allocate resources, including testing team members, as per project require-
ments
Monitor overall project progress and ensure adherence to timelines and budget
Coordinate with stakeholders to gather requirements and prioritize testing activ-
ities
Provide necessary support and guidance to the testing team for overcoming
challenges and obstacles
Review and approve test plans, test cases, and test reports
Communicate project status, risks, and issues to the project team and stakehold-
ers
Facilitate collaboration and communication between the testing team and other
project stakeholders
Ensure alignment of testing activities with project goals and objectives
Review and provide feedback on test summary reports and defect reports
Set risks and overall strategy for the testing plan
Make critical go/no-go decisions for items not covered in the test plans
Test Manager Facilitate the testing project
Coordinate availability and schedule of testers

17 | P a g e
 Train testing team members as needed
Communicate project expectations and deadlines
Review and approve test plans, test cases, and test reports
Monitor testing progress and quality
Communicate any risks or issues to the project team
Ensure adherence to testing standards and procedures
Prepare and present test summary reports
Obtain necessary approvals for testing activities
Provide required training to the testing team
Tester Execute test cases and test suites accurately
Report defects and issues promptly and accurately
Document test results, including pass/fail status and observations
Collaborate with developers to resolve defects and verify fixes
Participate in test plan and test case reviews
Follow testing processes and guidelines outlined in the test plan
Provide feedback on testing processes and suggest improvements
Attend meetings and discussions related to testing activities
Development Provide necessary support and assistance to testers during testing
Team
Address defects and issues reported by testers
Collaborate with testers to resolve defects and verify fixes
Ensure timely delivery of fixes and updates for testing
Participate in test case and test plan reviews
Validate software changes and updates before turnover to testing
Communicate any technical challenges or constraints that may affect testing
Review and provide feedback on test summary reports and defect reports
Coordinate with the test manager and testing team for testing activities
Stakeholders Provide input on testing requirements and priorities

18 | P a g e
 /Clients Review and approve test plans, test cases, and test reports
Participate in acceptance testing and provide feedback on the tested functionali-
ties
Communicate any critical business requirements or constraints that may affect
testing
Review and provide feedback on test summary reports and defect reports

14. Staffing and Training Needs

There will be at least one full time tester assigned to the project for the system/integration and
acceptance testing phases of the project. This will require assignment of a person part time at the
beginning of the project to participate in reviews etc. If a separate test person is not available the
project manager/test manager will assume this role. In order to provide complete and proper testing
the following areas need to be addressed in terms of training.
1. Training on the Application/System: All testing team members should undergo compre-
hensive training on the BestBuy.com application/system. This training should cover:

▪ Understanding of the website functionalities from both user and administrative per-
spectives.

▪ Familiarity with the business processes and workflows supported by the application.

▪ Knowledge of different user roles and their interactions with the system.

▪ Understanding of common user scenarios and use cases.

2. Training for Test Tools: Since Selenium and Java will be used for automated testing, the
testing team members should receive training on:

▪ Selenium WebDriver framework.

▪ Writing and executing test scripts using Java.

▪ Integration of Selenium with IDEs like Eclipse or Visual Studio Code for test devel-
opment and execution.

19 | P a g e
 3. Impact of Test Items and Responsibilities: The training needs should align with the test
items specified in Section 4 (Test Items) of the test plan. For example, testers responsible
for user authentication and account management testing should receive training specifically
on those functionalities. Responsibilities outlined in Section 13 (Responsibilities) also af-
fect training needs. Testers responsible for executing test cases related to specific features
should receive training on those features and their testing procedures.

4. Testing and Training Responsibility: The Test Manager is responsible for identifying the
training needs of the testing team and ensuring that appropriate training sessions are con-
ducted. Development Team members responsible for specific modules or functionalities
should also receive training on the corresponding areas to facilitate effective collaboration
between testers and developers during testing.

5. Training Delivery: Training sessions can be conducted either internally by experienced

team members or externally through professional training providers. Hands-on workshops
and practical exercises should be included in the training sessions to reinforce learning and
skill development.

20 | P a g e
 15. Schedule
Time has been allocated within the project plan for the testing process. Assume the time given for
testing process is 6 weeks, the following table presents the duration of each phase along with the
tasks to be completed during that phase for the BestBuy.com.

No. Phase Duration Tasks

Weeks Days
1. Test Plan Preparation 1 Finalize the test plan document.

Review and approval of the test plan by rele-

vant stakeholders.
2. Training and Environment 1 Conduct training sessions for testing team
Setup members on the application/system and test
tools (Selenium, Java).
Setup testing environments.
3. Testing Phase 1 Execute test cases based on the defined test
plan.
Log defects and issues found during testing.
Conduct regression testing as required.
4. Defect Resolution and 6 Prioritize and resolve defects identified during
Retesting testing.
Retest the fixed defects to ensure resolution.

Conduct additional testing if necessary.

5. Test Summary Report and 6 Compile test results and generate a test sum-
Finalization mary report.
Review and finalize the test deliverables.
Conduct a project retrospective meeting.
6. UAT (User Acceptance 5 Facilitate UAT sessions with end users.
Testing) Address any feedback or issues raised during
UAT.
Obtain sign-off from stakeholders.
7. Project Closeout 4 Archive test artifacts and documentation.
Conduct a final review meeting with project
stakeholders.
Prepare for project handover or transition.

21 | P a g e
 16. Risks and Contingencies
Identifying potential risks and defining contingency plans is essential for effective testing process.
Below are the identified risks along with their corresponding contingency plan for the Best-
Buy.com.

Risk Description Contingency Plan

Allocate additional resources to expedite
Potential delay in the start of testing
Delay in Test the test plan preparation process. Priori-
activities, impacting overall project
Plan Preparation tize critical sections of the plan for imme-
timelines.
diate completion.
Delays in setting up the testing envi- Maintain regular communication with the
Delay in Test
ronment may impact the overall IT team responsible for environment
Environment
testing schedule and delay the start setup. Have backup plans in place for al-
Setup
of testing activities. ternative testing environments if needed.
Provide additional training sessions or re-
Insufficient Decreased efficiency and effective-
sources to enhance the skills and
Training for ness of testing activities, leading to
knowledge of the testing team. Consider
Testing Team higher defect rates.
hiring experienced testers if necessary.
Insufficient availability of testing re-
Prioritize critical testing tasks and allo-
sources, including personnel and
Resource cate resources accordingly. Consider out-
equipment, may lead to delays in
Constraints sourcing certain testing activities if inter-
testing and compromise test cover-
nal resources are limited.
age.
Implement robust change management
Changes in project requirements or
Changes in processes to track and evaluate require-
scope may necessitate adjustments
Requirements or ment changes. Ensure close collaboration
to test plans and additional testing
Scope between the testing team and stakeholders
efforts, leading to potential delays.
to manage scope effectively.
Maintain regular updates and patches for
test automation tools to address known is-
Technical Issues
Inability to execute test cases or au- sues.
with Test Tools
tomate testing processes effectively Have backup testing tools or frameworks
/Frameworks
ready in case of technical issues with the
primary tools.
Unavailability of Establish clear communication channels
Unavailability of key stakeholders
Key and schedules with stakeholders. Provide
for review and decision-making may
Stakeholders regular updates and escalate issues

22 | P a g e
 result in delays in obtaining approv- promptly to ensure timely decision-mak-
als and resolving issues identified ing and issue resolution.
during testing.
As a last resort, quitting should only be
considered after thorough assessment of
risks and alternatives.
Extreme circumstances may lead to
Explore all possible avenues to address
the consideration of quitting the
challenges and mitigate risks before con-
Option to Quit testing process, resulting in project
sidering this option.
termination and potential loss of in-
Consult with project sponsors, stakehold-
vestment.
ers, and management to evaluate the fea-
sibility and implications of quitting the
testing process.

23 | P a g e
 17. Approvals
Approval is crucial to ensure alignment with project goals, quality standards, and compliance re-
quirements. Typically, the test manager and product manager are the key decision-makers respon-
sible for approving the completion of the testing project. They must review the test plan and ensure
that it meets the defined objectives, scope, and quality standards. Additionally, they verify that all
testing tasks, responsibilities, and deliverables are adequately addressed and aligned with the pro-
ject's overall objectives. Once both the test manager and product manager agree on the completion
of the testing project and determine that it's ready to proceed to the next phase, they provide formal
approval. This approval signifies that the testing project has been successfully planned and exe-
cuted according to the established criteria and can proceed to subsequent phases, such as user
acceptance testing or deployment.

24 | P a g e
 18. Glossary
o Git: is a distributed version control system used for tracking changes.

o UAT (User Acceptance Testing): is the final phase of software testing where the system
is tested by end-users.

o Test Plan Identifier: A unique identifier assigned to the test plan document for referencing
and version control purposes.

o Frontend: refers to the part of a software application or system that users interact with
directly. It includes user interfaces, screens, and components visible to users.

o Backend: refers to the part of a software application or system that handles data pro-
cessing, storage, and business logic. It is responsible for managing the functionality that
occurs behind the scenes and is not directly visible to users.

o Authentication: Authentication is the process of verifying the identity of a user, typically

through the use of credentials such as usernames and passwords.

o Checkout: Checkout refers to the process in an e-commerce website where users complete
their purchase transactions by providing payment and shipping information and confirm-
ing their orders.

o Approach: refers to the overall strategy or methodology adopted for planning, executing,
and managing the testing process.

o Configuration Management: is the process of systematically managing changes to the

configuration of a system or software product.

o Regression Testing: Regression testing is the process of retesting a software application

or system to ensure that recent code changes have not introduced new defects or caused
unintended side effects.

o Granting a refund: The process of approving and issuing refunds to customers who re-
quest them for products they have purchased, typically managed by customer service rep-
resentatives or administrators.

25 | P a g e
 o Moderating reviews: The activity of managing and overseeing user-generated product
reviews submitted by customers on the website, including reviewing, editing, approving,
or rejecting reviews to maintain quality and compliance with guidelines.

o Validating in-stock/out-of-stock: The process of verifying the availability status of prod-

ucts in inventory, ensuring that accurate information is displayed to customers regarding
whether a product is currently available (in-stock) or unavailable (out-of-stock) for pur-
chase.

o Order: In the context of e-commerce, an order refers to a request placed by a user to

purchase one or more products or services from an online store.

o Suspension: refers to the temporary halt or pause of testing activities under predefined
conditions, such as when critical defects are discovered, or environmental issues arise.

o Deliverables: are tangible outputs or artifacts produced as part of the testing process, such
as test plans, reports, documentation, and defect logs.

o Unit Test Plans/Turnover documentation: consists of test plans and related documenta-
tion created by developers for unit testing. It includes details of test cases, expected out-
comes, and results, which are handed over to the testing team for verification.

o Mock-ups: Mock-ups are visual representations or prototypes of user interfaces, screens,

or designs used to demonstrate the layout, functionality, and appearance of a software ap-
plication or system before development or testing begins.

o Test Cases: Test cases are detailed instructions or procedures that define inputs, actions,
and expected results for testing specific functionalities or scenarios of a software applica-
tion.

o Test Suites: Test suites are collections or groups of related test cases organized together
for efficient execution and management.

o Test Logs: Test logs are records or files that capture information about test execution,
including test case results, defects identified, and other relevant details.

26 | P a g e
 o Turnover Reports: Turnover reports are documents or summaries that provide infor-
mation about completed testing activities, including test results, findings, and recommen-
dations.

o Risk: Risk refers to the possibility of experiencing undesirable outcomes or events that
could impact the success of a project or activity.

o Contingency Plan: A contingency plan is a predefined strategy or set of actions designed

to mitigate or address potential risks and uncertainties that may arise during the testing
process.

27 | P a g e
Sample Implementation
The website https://www.bestbuy.com/ has different interface for new users and logged in us-
ers, as a result the following code is for logged in user to add an item to cart. In order to add item
to cart we have to create account.

import org.openqa.selenium.By;
import org.openqa.selenium.WebDriver;
import org.openqa.selenium.WebElement;
import org.openqa.selenium.chrome.ChromeDriver;
import org.openqa.selenium.Dimension;
import org.openqa.selenium.interactions.Actions;
import org.openqa.selenium.JavascriptExecutor;
import java.util.*;

public class AddToCart {

public static void main(String[] args) {
// Set the path to ChromeDriver executable
System.setProperty("webdriver.chrome.driver",
" /path/to/chromedriver ");

// Instantiate the Test2Test class

Test2Test test = new Test2Test();

// Set up the WebDriver

test.setUp();

// Run the test

test.test2();

// Tear down the WebDriver

test.tearDown();
}
}

class Test2Test {
private WebDriver driver;
private Map<String, Object> vars;
private JavascriptExecutor js;

public void setUp() {

driver = new ChromeDriver();
js = (JavascriptExecutor) driver;

28 | P a g e
 vars = new HashMap<String, Object>();
}

public void tearDown() {

driver.quit();
}

public void test2() {

// https://www.bestbuy.com/?intl=nosplash
// https://www.bestbuy.com/
driver.get("https://www.bestbuy.com/");
driver.manage().window().setSize(new Dimension(1366, 728));
driver.findElement(By.cssSelector(".open-hamburger-icon")).click();
{
WebElement element = driver.findElement(By.cssSelector(".close-ham-
burger-icon > path:nth-child(1)"));
Actions builder = new Actions(driver);
builder.moveToElement(element).perform();
}
{
WebElement element = driver.findElement(By.tagName("body"));
Actions builder = new Actions(driver);
builder.moveToElement(element, 0, 0).perform();
}
driver.findElement(By.cssSelector(".liDropdownList:nth-child(14) > .c-
button-unstyled")).click();
{
WebElement element = driver.findElement(By.linkText("Home Security
Systems"));
Actions builder = new Actions(driver);
builder.moveToElement(element).perform();
}
{
WebElement element = driver.findElement(By.tagName("body"));
Actions builder = new Actions(driver);
builder.moveToElement(element, 0, 0).perform();
}
driver.findElement(By.cssSelector(".liDropdownList:nth-child(11) > .c-
button-unstyled")).click();
driver.findElement(By.linkText("Smart TVs")).click();
js.executeScript("window.scrollTo(0,1)");
js.executeScript("window.scrollTo(0,136)");
js.executeScript("window.scrollTo(0,384)");
js.executeScript("window.scrollTo(0,479)");
js.executeScript("window.scrollTo(0,621)");

29 | P a g e
 js.executeScript("window.scrollTo(0,813)");
js.executeScript("window.scrollTo(0,1052)");
js.executeScript("window.scrollTo(0,1229)");
js.executeScript("window.scrollTo(0,1397)");
js.executeScript("window.scrollTo(0,1528)");
js.executeScript("window.scrollTo(0,1690)");
js.executeScript("window.scrollTo(0,1988)");
js.executeScript("window.scrollTo(0,2296)");
js.executeScript("window.scrollTo(0,2488)");
js.executeScript("window.scrollTo(0,2938)");
js.executeScript("window.scrollTo(0,3078)");
js.executeScript("window.scrollTo(0,3243)");
js.executeScript("window.scrollTo(0,3550)");
js.executeScript("window.scrollTo(0,3837)");
js.executeScript("window.scrollTo(0,3895)");
driver.findElement(By.cssSelector("#shop-sku-list-item-66885749 .product-
image")).click();
js.executeScript("window.scrollTo(0,4025)");
js.executeScript("window.scrollTo(0,4044)");
{
WebElement element = driver.findElement(By.cssSelector(".primary-but-
ton"));
Actions builder = new Actions(driver);
builder.moveToElement(element).perform();
}
js.executeScript("window.scrollTo(0,1)");
{
WebElement element = driver.findElement(By.tagName("body"));
Actions builder = new Actions(driver);
builder.moveToElement(element, 0, 0).perform();
}
js.executeScript("window.scrollTo(0,287)");
js.executeScript("window.scrollTo(0,356)");
js.executeScript("window.scrollTo(0,322)");
js.executeScript("window.scrollTo(0,189)");
driver.findElement(By.cssSelector(".c-button-primary")).click();
driver.findElement(By.cssSelector(".back-button")).click();
}
}

30 | P a g e
References

✓ https://jmpovedar.wordpress.com/wp-content/uploads/2014/03/ieee-829.pdf

✓ https://www.ecs.csun.edu/~rlingard/comp480/TestPlanTemplate.pdf

✓ https://docs.google.com/document/d/1F1TUX5BkviRbw8auI2Xq2K2wyGTS-Ag14DRy-
miELmzc/edit#heading=h.jd6vjs4lpb4w

31 | P a g e