Software Testing and

Quality Assurance
（Software Test Plan）

Name: AYA EL BELLAOUI

Student Number: 231091007
Class: Software Engineering Class of 2023

2025.11.29
 Online Book Store System Software Testing Plan

Chapter 1 Document Introduction

1.1 Project Name and Brief Description

The name of this project is "Online Book Store System", this project is web-based application
designed to support online book purchasing activities, which allows users to register and log in,
search for books by title or category, add books to a shopping cart, checkout and place orders and
view order history, all through a centralized platform available on a web browser.

1.2 Purpose of the Test Plan

The purpose of this testing plan is to provide a clear and usable guide for testing the Online Book
Store System project. The testing strategy, methods, scope, environment, team roles, and
schedule are included in a single document. This document serves as a reference for planning
work, executing tests, and reporting results in a consistent and controlled manner.

The main goal of this plan is the quality assurance of the Online Book Store System. Core
functions such as account registration, login, book search, cart actions, checkout, and order
history are verified. System performance, data protection, and ease of use are also assessed. Tests
are conducted to detect defects early and reduce risk before release.

This document establishes the standard for all testing tasks. Defined steps are followed for test
execution, defect logging, and result review. The plan is used to coordinate work among team
members and instructors. Progress is tracked, fixes are confirmed, and reports are prepared
according to the established rules and criteria.

Failures are minimized through planned testing. Login errors, incorrect orders, data loss, and
service downtime are prevented. User data and payment flows are safeguarded through security
checks. User trust is enhanced through stable system behavior and clear results. This plan
supports the delivery of a reliable and user-focused Online Book Store System.

1.3 Project Background

Online shopping continues to grow across many markets. Fast access, clear product details, and
simple payment steps are expected by users. Round-the-clock access from different devices is
anticipated. Search results are expected to be delivered within seconds, and order status is
expected to be available at any time. These requirements drive demand for web-based stores with
strong performance and clear design.
 Online Book Store System Software Testing Plan

Books remain a high-demand product in online sales. Searches are conducted by title, category,
author, and price. Editions and formats are compared before purchase. Accurate stock status and
clear descriptions are expected. Manual handling of orders can lead to errors and delays. These
issues are reduced by an online system through automated records and structured processes from
search to checkout.

The Online Book Store System addresses these needs through a web interface. Accounts are
managed, listings are browsed, items are added to a cart, and orders are placed through a single
platform. Orders and user data are stored in a centralized database. Order history can be viewed
without contacting support. Activity can be tracked without additional tools.

This project also supports learning objectives. Test planning is practiced on a system with real
features and identifiable risks. Login flows, search logic, database updates, and order processing
are examined. Outcomes from test runs and defect reports are measured. Test design skills are
improved through hands-on tasks and review. Experience is gained in quality control for web
systems used by actual users.

Chapter 2 System Overview and Functional Modules

2.1 Overview of the Online Book Store System

From a testing perspective, the Online Book Store System is a unified platform with business
processes focused on book sales and order handling. Features related to user access, product
search, shopping activity, and order tracking are verified. The system groups functions into three
main modules. These modules are the user access module, the shopping and order module, and
the account and history module.

User access module: This module controls entry into the system. Account registration and login
are verified. Input rules for usernames and passwords are checked. Error handling for incorrect
data is reviewed. Protection against invalid access is emphasized. Only valid users are allowed to
enter private pages.

Shopping and order module: This module handles book browsing and purchases. Search by
title and category is verified. Product display for accuracy is checked. Cart actions such as add,
remove, and update quantity are verified. Checkout steps and order creation are reviewed. Stock
updates after orders are confirmed. It is ensured that one order creates one record in storage.
 Online Book Store System Software Testing Plan

Account and history module: This module manages user data and order records. Profile
updates and saved details are checked. Order history views are reviewed. Only the users’ own
records are accessible. Data consistency after new orders is verified. Privacy rules for stored
information are checked.

Each module operates in coordination with the others. The effects of actions in one area on other
areas are evaluated. Login status control of access to purchase features is confirmed. Order
placement updates in order history are verified. Failures across module borders are tracked.
These checks support consistent system behavior.

2.2 Technical Architecture and Operating Environment

The Online Book Store System uses a basic web structure with clear separation between the
frontend, backend, and database. Each layer is tested to confirm stable behavior during login,
search, cart actions, and checkout.

Backend: The backend is built with a simple server framework such as [Link] Express or a
similar lightweight option. User input, business logic, session checks, and request routing are
handled. Input validation, error handling, and secure access to private pages are verified.
Connection to the database is made through a standard ORM or query module. Data flow for
registration, login, cart updates, and order creation is checked.

Frontend: The frontend is created with HTML, CSS, and JavaScript. Pages use a clean structure
with simple navigation. Form actions, button clicks, and data rendering are checked. Book lists,
book details, and cart items are confirmed to load correctly. Page responsiveness and accurate
display of backend data are verified.

Database: A relational database such as MySQL is used. Users, books, categories, cart entries,
and order history are stored. Insert, update, and delete operations for each table are verified.
Stock numbers are reduced after a purchase is checked. Each order is verified to create only one
saved record. User access to only their own data is confirmed.

Server and network: The system runs on a standard web server using Windows or Linux. Page
load time and request handling are tested. Actions are repeated to check stability. Server response
without slowdowns during search or checkout is confirmed. Testing is performed using a normal
internet connection similar to a real environment.

Browser environment: Access through common browsers is used. Tests are performed in
Chrome, Firefox, Edge, and Safari. Layout stability, text clarity, and input behavior are checked.
Pages are tested on different screen sizes to confirm readability and working buttons.
 Online Book Store System Software Testing Plan

Testing focus: Each connection point in the architecture is evaluated. Correct requests from the
frontend are confirmed. Processing of these requests and updates to the database with correct
values by the backend are verified. Appearance of updated records on the frontend without delay
is confirmed. Defects across layers are tracked, and fixes are verified through repeated execution.

2.3 Analysis of Core Business Processes

The Online Book Store System depends on a clear sequence of actions from search to purchase.
These actions are verified to confirm correct state changes and data stability. Connections
between modules through shared records are verified through focused testing.

The system tracks four main states for each book during a purchase cycle. These states are
available, in cart, in pending order, and purchased. Updates to these states are performed through
a simple flow.

1.​ Available: A book starts in the available state. When selected and added to a cart, stock
is checked and a cart entry connected to the user is created. Stock remains unchanged at
this step.
2.​ In cart: The cart holds selected items. Quantities and prices are reviewed. Updates,
removals, and repeated edits are checked. The book remains in the available state until
checkout begins.
3.​ Pending order: During checkout, a pending order is created. Stock is verified, and the
list of items is locked for this order. Cart entries remain active until confirmation or
cancellation of the action.
4.​ Purchased: After checkout confirmation, a final order record is created, and stock is
reduced. Related cart entries are removed. The book enters the purchased state for that
user.

When stock reaches zero, the book is marked as out of stock. Adding the book to a cart is
blocked until stock updates.

The order history module completes the cycle. Each confirmed order appears in the user’s
history. Titles, quantities, and totals for each purchase are displayed.

These flows depend on accurate links between tables such as Users, Books, Cart, Orders, and
OrderItems. Errors in any step can result in incorrect stock values, duplicate entries, or missing
order data. Each step is verified to confirm that one action triggers one update. Consistency of
data across all modules after each change is also checked.
 Online Book Store System Software Testing Plan

Testing focuses on the stability of these transitions. Completion, consistency, and isolation of
each state change from other users are confirmed. Order accuracy is maintained, supporting
reliable system behavior.

Chapter 3 Test Objectives and Scope

3.1 test objective

The Online Book Store System is tested to confirm stable function, accurate data, and safe
access. Objectives focus on four areas.

●​ Functional verification: Registration, login, search, cart actions, checkout, and order
history are checked. It is confirmed that each action follows the expected rule set. Each
action is verified to produce one correct update in the database.
●​ Performance behavior: Response time during frequent searches, cart updates, and
checkout attempts is measured. Page load within acceptable limits is confirmed.
●​ Security checks: Access control for all private pages is tested. Input handling for fields
such as username, password, and address is verified. It is confirmed that only the user’s
own data is accessible.
●​ Usability: Text clarity, button placement, and form flow are checked. It is confirmed that
each page guides users through tasks without confusion.

3.2 Test Scope

The test scope covers the core functions of the Online Book Store System. Features that support
user access, book search, shopping actions, order processing, and account history are evaluated.
Functions that influence data accuracy, purchase flows, and user access rights are focused on.

The test scope includes the following areas:

1.​ User access module: Registration, Login, Input validation for usernames and passwords,
Access control for protected pages.
2.​ Book search and browsing: Search by title, Search by category, Display of book details,
Display of stock status.
3.​ Shopping cart: Add book to cart, Remove book from cart, Update quantity, Cart total
calculation, Data consistency after page reloads.
4.​ Checkout and order processing: Checkout flow from cart to confirmation, Order
creation, Stock updates after orders, Prevention of duplicate orders, Error handling when
stock reaches zero.
 Online Book Store System Software Testing Plan

5.​ Order history: Display of all past orders for the current user, Display of order details
and quantities, Data accuracy after new orders, Visibility control to ensure only the user’s
own records are seen.
6.​ Account management: Update of basic profile information, Update of address and
contact details, Validation rules for profile fields.
7.​ Cross module behavior: Effects of login status on cart actions, Effects of book stock
changes on search results, Effects of order creation on order history, Database
consistency across modules after each user action.
8.​ Performance scope: Response time for search, Response time for cart actions, Response
time for checkout, Stability during repeated operations.
9.​ Security scope: Access control for private pages, Input handling for login and profile
fields, Behavior when attempts are made to access other users’ records.
10.​Usability scope: Clarity of text on main pages, Navigation flow from search to cart to
checkout, Readability on common screen sizes.

This scope covers functional behavior, data flow, performance indicators, security rules, and
usability checks. It is used to guide all testing activities and to confirm that the system behaves
correctly under normal and abnormal conditions.

3.3 Non Testing Scope

The non testing scope lists items excluded from this system test. These items are outside the
course objectives or depend on external tools that are not measured in this plan.

Excluded items:

• Unit testing created by developers.

• Integration testing of backend code modules.

• Payment gateway performance.

• Server hardware stability.

• External network quality.

• Stress testing that pushes the system into extreme load.

• Browser plugin behavior.

• Features not mentioned in project requirements.

 Online Book Store System Software Testing Plan

Testing is limited to functions that influence user access, book search, cart actions, checkout, and
history, focusing on issues that block core actions or break expected behavior.

3.4 Function module and test type matrix

The matrix shows which modules need heavy testing and which modules need support testing.
This helps plan the work and distribute resources.

Functional Module Functional Performance Security Usability

Testing Testing Testing Testing

Registration and login primary primary primary primary

Book search and primary primary secondary primary

browsing

Shopping cart primary primary secondary primary

Checkout and order primary primary primary secondary

creation

Order history primary secondary primary primary

Account management primary secondary primary secondary

 Online Book Store System Software Testing Plan

Chapter 4 Testing Strategies and Methods

4.1 test method

This system test uses black box methods, internal code is not examined, functions are verified
from the user and administrator perspective, the system is checked against expected requirements
using controlled inputs and observed outputs, functional correctness is confirmed through
registration, login, search, cart updates, and checkout, database updates are tracked for accuracy,
error handling is observed for invalid inputs, navigation and forms are tested for correct
behavior, cross-module actions are executed to verify data flow, response times and page updates
are monitored, access control is checked for restricted pages, and boundary conditions are tested
for proper handling, all results are documented for traceability and repeatability.

●​ (1) Functional testing: Use equivalence class partitioning, boundary value analysis, and
scenario analysis. Design test cases that cover all functional paths and abnormal
conditions. Pay attention to cross module flows such as search to cart, cart to checkout,
and checkout to order history. Confirm that each action updates book stock, cart data, and
order records correctly.
●​ (2) Performance testing: Use load testing and concurrency testing. Use tools such as
JMeter to simulate many users performing search, cart updates, and checkout tasks at the
same time. Focus on response time and resource usage during high load conditions.
Observe stability during repeated requests.
●​ (3) Security testing: Unauthorized access testing: Attempt to access protected pages
such as order history or checkout without login. Confirm that the system blocks access
and returns correct error responses.​
Direct URL access testing: Try to open internal pages through direct URLs. Confirm that
the backend checks login status and user role.​
Input verification testing: Check all input fields such as username, password, address,
and search fields. Confirm strong validation to prevent SQL injection and XSS.
●​ (4) Usability testing: Use heuristic checks and scenario walkthroughs. Confirm that the
layout, text, and interaction flow match common usage habits. Check page adaptation on
different screen sizes for mobile and PC. Confirm that users can complete search, add to
cart, and checkout tasks without confusion.

4.2 Principles of Test Data Design

Test data is designed based on the database structure of the Online Book Store System. You
prepare data that triggers normal flow, abnormal flow, boundary conditions, and state transitions.
 Online Book Store System Software Testing Plan

●​ Validity data: Prepare test data that supports full business flow. This includes valid user
accounts, book titles, categories, and books with available stock.
●​ Invalid data: Prepare data that simulates wrong or missing information. This includes
invalid usernames, wrong passwords, non-existent book IDs, incorrect category names,
and invalid quantities. This helps verify error messages and recovery behavior.
●​ Boundary value data: Prepare data that checks the limits of each field. This includes
maximum username length, maximum address length, minimum and maximum quantity
in the cart, and large search inputs.
●​ State related data: Prepare data sets that activate different system states. This includes
books with zero stock, users with existing orders, users with empty history, and carts with
multiple items. This verifies correct handling of stock updates, order creation, and history
display.

4.3 Test Standard

The standards for passing this system test are as follows:

① All functional test cases for core functions such as registration, login, search, cart updates,
checkout, and order history have been executed and passed.

② All critical defects such as crashes, data loss, and broken flows have been fixed and verified.

③ All performance requirements are met. Search, cart actions, and checkout respond within
acceptable limits under load.

④ All security checks pass. Unauthorized access attempts and direct URL access attempts fail.
No severe security defects remain.

⑤ Overall usability meets expected design goals. Pages are readable, navigation is clear, and no
major interaction issues appear.

The criteria for failure are as follows:

① Major defects exist in core functions such as search, cart updates, or checkout, and cannot be
fixed within planned time.

② Defect density becomes too high, preventing continued testing.

③ Performance indicators do not meet expected limits and create negative user impact.
 Online Book Store System Software Testing Plan

Chapter 5: Detailed Test Case Design

This chapter provides detailed test case design for the Online Book Store System. The design
reflects the core functions and business flow of the system, covering registration, login, search,
cart actions, checkout, order records, and related operations. Test cases follow black box methods
and focus on verifying correct behavior, error handling, and data updates.

5.1 Login and Registration Section

Test Objective: Check whether users register and log in correctly. Confirm correct handling of
valid and invalid inputs. Confirm that protected pages require login.

Table 5.1 Registration and Login Module Test Cases

Test Case Input Description Expected Output Execution Steps

Name

Successful Valid username and Enter home page Open login page. Enter valid username
Login password and password. Submit form. Confirm
access to home page.

Failed Login Wrong username or Show error prompt Open login page. Enter invalid data.
password Submit form. Confirm error message and
no access.

Valid Correct user Account created Open registration page. Enter valid
Registration information username, password, and required fields.
Submit form. Confirm success message.
 Online Book Store System Software Testing Plan

Invalid Missing or invalid Rejection prompt Enter empty fields or invalid formats.
Registration fields Submit form. Confirm error prompt and
no account creation.

Access Direct access to Redirect to login Enter URLs such as /cart or /orders.
Without private URL Confirm auto redirect to login page.
Login

5.2 Book Search and Browsing

Test Objective: Check whether the search and book display functions work correctly. Confirm
correct results, correct category filtering, and correct display of out of stock items.

Table 5.2 Book Search and Browsing Module Test Cases

Test Case Name Input Description Expected Output Execution Steps

Search By Full Exact book title Show matching Enter full title in search bar.
Title book Confirm exact match in result list.

Search By Keyword Show all Enter partial keyword. Confirm list

Partial Title matching books contains all relevant titles.

Category Search Select category Show books in Select a category from menu.
category Confirm all book results belong to
that category.

View Book Click book item Show details Select a book. Confirm title, author,
Details page price, and stock display correctly.

Out of Stock Book with zero Block add to Open a book with zero stock.
Handling stock cart Confirm add to cart button is
disabled.

5.3 Shopping Cart Module

 Online Book Store System Software Testing Plan

Test Objective: Check whether cart adds, updates, and removes items correctly. Confirm
accurate quantity and price updates.

Table 5.3 Shopping Cart Module Test Cases

Test Case Name Input Description Expected Output Execution Steps

Add Book To Cart Select in stock item Item added to Open book page. Click add to cart.
cart Confirm item appears in cart.

Add Several Add different All items appear Add multiple books. Open cart.
Items books Confirm each item is listed.

Update Quantity Change quantity Cart updates Increase and decrease quantity.
total Confirm correct recalculation.

Remove Item Delete cart item Item removed Remove an item. Confirm updated list
and correct total.

Add Zero Stock Item with zero Rejected Attempt to add. Confirm block prompt.
Item stock

5.4 Checkout and Order Processing Module

Test Objective: Check whether checkout creates orders correctly. Confirm correct stock
reduction and no duplicate orders.

Table 5.4 Checkout and Order Module Test Cases

Test Case Input Expected Output Execution Steps

Name Description

Valid Cart with valid Order created Open cart. Click checkout.
Checkout items Confirm order summary and
saved record.

Checkout No items Reject action Click checkout with empty cart.

With Empty Confirm prompt to add items.
Cart
 Online Book Store System Software Testing Plan

Duplicate Submit twice One order only Click checkout. Try to repeat
Submission submission. Confirm only one
order record exists.

Low Stock Quantity equals Order created and Add item with low stock.
Checkout stock stock updated Checkout. Confirm stock reduces
to zero.

Order After checkout Correct items and Open order details. Confirm item
Summary totals list and total price.
Display

5.5 Order History Module

Test Objective: Check whether order records show correctly. Confirm correct access control for
user records.

Table 5.5 Order History Module Test Cases

Test Case Input Expected Execution Steps

Name Description Output

View Own Logged in user Show correct Log in. Open order history. Confirm list
Orders records matches user purchases.

View Order Select record Show full Click order. Confirm correct details
Details information appear.

Access Other Change URL Block access Attempt to view another user’s order ID
User History by changing URL. Confirm access
denied.

History Update Place new New record Checkout. Then open history. Confirm
order appears new record added.

Empty History New user Show empty Log in with new account. Open history.
result Confirm no records appear.
 Online Book Store System Software Testing Plan

5.6 Performance Testing

Test Objective: Check response time and stability under repeated actions.

Table 5.6 Performance Testing Cases

Test Case Name Input Expected Execution Steps

Description Output

Repeated Many search Stable response Perform search many times. Confirm
Search queries fast responses.

Repeated Cart Add and remove No errors Update cart repeatedly. Confirm
Updates items stability.

Repeated Different users Correct order Perform checkout actions many times.
Checkout creation Confirm correct order records.

Concurrent Many simulated Stable Use load tool to simulate users.

Access users performance Confirm response time within limits.

Page Load Open pages No slowdowns Refresh home, cart, and order pages
Stability repeatedly many times. Confirm normal load
time.

Chapter 6 Risk Assessment and Management

The risk assessment for the Online Book Store System follows the structure used in the example
plan. It identifies project risks that affect testing quality, schedule, and system correctness. For
each risk, the table lists severity, probability, mitigation actions, and an emergency plan. The goal
is to reduce test interruptions and protect user data and order integrity.

6.1 Project risk

Table 6-1 Risk Management and Mitigation Measures Table

Risk Severity Risk Circumvention Emergency plan

Disclosure of risk probability measures
 Online Book Store System Software Testing Plan

Insufficient high medium Provide focused training Extend test time for
tester skills on web test tools and DB complex cases.
checks. Pair junior testers Reassign simple tasks
with a senior reviewer. to less experienced
testers.

Development high high Hold weekly sync with Compress tests for
delay developers. Prioritize test low risk modules.
cases for core flows: Extend work hours for
login, search, cart, core testing.
checkout, order history.

Payment high medium Use a sandbox payment Switch to mock

gateway provider. Mock payment payment for
failure responses in tests. remaining tests.
Validate fallback Record failed
messages to users. transactions for later
review.

Inventory sync high medium Build test scenarios for Lock inventory
errors with out of stock and delayed updates during key
supplier updates. Use controlled test runs. Restore
test data for stock levels. stock from snapshot if
needed.

Database high medium Design tests with realistic Roll back problematic
deadlock concurrency. Monitor DB transactions. Restore
under locks. Use transactions DB from last
concurrency and retries. consistent backup.

Unauthorized high low Enforce role checks in Invalidate sessions

access and test cases. Run URL and and revoke exposed
data leak API access tests. Verify tokens. Run
data isolation per user. emergency password
reset for affected
accounts.
 Online Book Store System Software Testing Plan

Environment medium medium Document environment Switch to backup

instability setup steps. Keep a environment. Rerun
backup test environment. smoke tests before
Automate basic smoke continuing.
checks.

Incomplete or medium medium Track requirement Freeze non critical

changing changes in a single log. changes in final test
requirements Update test cases after week. Focus on
each confirmed change. regression for stable
features.

High defect high low Introduce triage for Stop new test case
density defects. Focus fixes on creation. Concentrate
critical flows first. on retesting critical
Maintain a clear severity fixes.
classification.
6.2 Risk response and mitigation measures
In response to the above risks, the test team prepares clear actions to reduce interruptions and
protect test quality. The test manager tracks daily progress and updates the risk table when new
problems appear. When development work is delayed, the team adjusts priorities and focuses on
registration, login, search, cart, checkout, and order history. Less important modules move to
later cycles.

For environment risks, the team keeps one backup test setup and checks it with a simple smoke
test each day. For security risks, the team performs strict URL checks and session checks to
confirm that users do not access other users’ data. For database issues, the team restores data
from snapshots when a lock or corruption appears.

For payment and external services, the team uses a sandbox or mock response during testing.
This prevents failed third party calls from blocking checkout tests. For requirement changes, the
team updates related test cases quickly and records each change in a shared document.

These responses keep testing stable and reduce the chance of blocked tasks or loss of key data.

Chapter 7 Testing Environment and Tools

7.1 Testing and Environment Configuration
 Online Book Store System Software Testing Plan

To verify system performance under conditions similar to production, the testing environment
simulates real web deployment. Tests will run on an internet-connected setup to check access,
database updates, and cross-browser performance.

The system will be tested in multiple layers: frontend, backend, and database. Each layer is
evaluated for stability, accuracy, and responsiveness.

Table 7-1 System Testing Environment Configuration

Host Quantity CPU Memory Hard Disk Installed Software

Web Server 1 3.4 8G+ At least 10G [Link], Express,

GHz+ free Nginx/Apache

Database 1 3.4 8G+ At least 10G MySQL

Server GHz+ free

Client 3 2.0 4G+ At least 5G Windows 10/11, Chrome,

Machines GHz+ free Firefox, Edge, Safari
Special note: For performance testing, the team will simulate multiple simultaneous users using
tools like JMeter to verify system stability under load.

7.2 Auxiliary Management Tools

●​ The following tools support testing processes and improve efficiency:
●​ Test management and defect tracking: Jira or TestRail will record test cases, execution
status, and defect allocation. This ensures traceability of all testing activities.
●​ Performance testing: JMeter will simulate multiple concurrent users performing search,
cart, and checkout operations to measure response times and system stability.
●​ Security testing: Burp Suite will assist in penetration testing to detect vulnerabilities,
unauthorized access, and input validation issues.
●​ Automated testing (optional): Selenium or Playwright will automate regression testing
for core functions such as login, registration, search, and checkout, reducing manual
effort and ensuring repeatable results.
●​ Additional considerations include database snapshots for restoring test data, logging
system responses for analysis, and recording defects with clear steps for reproduction.
This ensures testing results are accurate, verifiable, and actionable.
 Online Book Store System Software Testing Plan

Chapter 8 Testing Organization and Progress

8.1 Test Team Roles and Responsibilities
The testing team consists of 4 members. Each member has clear responsibilities to ensure
smooth and efficient testing.

Test Manager (1): Develops and maintains the test plan, coordinates resources, monitors
progress, tracks risks, resolves issues, and ensures deadlines are met. The manager also approves
test reports and ensures compliance with testing standards.

Test Designers (2): Analyze project requirements, create detailed test cases, design test data,
configure the testing environment, and prepare scripts for performance and security tests. They
also review test case coverage and update cases when requirements change.

Test Executor (1): Executes tests according to the designed test cases, records detailed results,
logs defects, verifies fixes with developers, and checks cross-module functionality. The executor
also performs exploratory testing to detect unanticipated issues.

Team members meet daily for status updates and problem-solving. Collaboration is maintained
through shared documents, Jira boards, and test logs to track progress and defects.

8.2 Test Schedule Plan

The testing cycle spans 4 weeks. Each week focuses on specific tasks to ensure systematic
coverage of all modules.

Week 1: Develop and review the test plan, design functional, performance, security, and
usability test cases, and prepare test data. Review requirements and clarify unclear points with
the development team.

Week 2: Set up the testing environment, perform smoke testing to verify system readiness, and
begin functional and usability testing. Log all initial defects and classify them by severity.

Week 3: Complete functional and usability testing, perform performance and security testing,
and conduct regression testing on previously identified defects. Simulate multiple users to test
concurrency and check database consistency.
 Online Book Store System Software Testing Plan

Week 4: Complete all regression tests, verify that defects are fixed, analyze test results, prepare
the test summary report, and submit all testing documents. Conduct a final review meeting with
the team to evaluate test coverage and effectiveness.

Progress monitoring is continuous. The test manager tracks task completion, defect closure, and
resource utilization. Weekly reports summarize results, highlight issues, and recommend
corrective actions.

This structured approach ensures all modules, including registration, login, book search, cart,
checkout, order history, and account management, are tested thoroughly. The schedule allows
time for unexpected issues, retesting, and final verification before submission.

Chapter 9 Submitting Work Products

After testing, the following documents will be submitted:

Test Plan Document: Contains overall strategy, objectives, scope, and procedures.
Test Case Report: Detailed list of executed test cases and their results.
Defect Report: Records all defects found, severity, status, and verification.
Test Summary Report: Summarizes testing process, analysis of results, and assessment of system
quality.

These work products ensure traceability, accountability, and a clear record of testing activities.