Business management TEST PLAN
Table of Contents
1. INTRODUCTION ...............................................................................2
2. SCOPE .................................................................................................2
3. QUALITY OBJECTIVES....................................................................3 3.1 Primary
Objectives ............................................................................3 3.2 Secondary
Objectives ........................................................................3
4. TEST APPROACH ..............................................................................3 4.1 Test
Automation ................................................................................4
5. ROLES AND RESPONSIBILITIES....................................................4
6. ENTRY AND EXIT CRITERIA..........................................................5 6.1 Entry
Criteria ....................................................................................5 6.2 Exit
Criteria.......................................................................................5
7. SUSPENSION CRITERIA AND RESUMPTION
REQUIREMENTS .................................................................................5 7.1 Suspension
Criteria ..........................................................................5 7.2 Resumption
Criteria ..........................................................................6
8. TEST STRATEGY...............................................................................6 8.1 QA Role in
Test Process...................................................................6 8.2 Bug Life
Cycle:..................................................................................7 8.3 Testing
Types ....................................................................................8 8.4 Bug Severity and
Priority Definition.................................................9 Severity
List...........................................................................................10 Priority
List ...........................................................................................10
9. RESOURCE AND ENVIRONMENT NEEDS .................................11 9.1 Testing
Tools ...................................................................................11 9.2 Configuration
Management..............................................................11 9.3 Test
Environment..............................................................................11
10. TEST SCHEDULE............................................................................12
APPROVALS ........................................................................................13
TERMS/ACRONYMS ..........................................................................
1. INTRODUCTION
The Business Management System (BMS) is a comprehensive platform designed to automate
and streamline business operations across multiple departments, including client management,
financial tracking, inventory control, and reporting. Despite its potential, the current system
struggles with operational efficiency. The proposed project aims to extend services to various
business processes, which will help the organization run its operations more smoothly.
2. SCOPE
The document mainly targets the testing of the system's Graphical User Interface (GUI) and
validates data in the reporting output, according to the Requirements Specifications provided by
the Client.
2.1 Functions to be Tested
Admin:
Login to the system
Add, modify, or remove information about clients, products, or services from the
database
Check availability of resources or products
Add, modify, or remove user information from the database
View the list of registered users or employees
Generate various business reports
Search for clients or services by name or category
Users (Managers, Employees):
Register an account
Login to the system
Search for services, products, or clients by name or category
View information about account status or assigned tasks
View detailed business data (e.g., client details, project progress, financial reports)
Execute business transactions, manage clients, or assign tasks
View history of completed tasks or projects
Request for service modifications, refunds, or updates
2.2 Functions Not to be Tested
Functions beyond those mentioned in section 2.1 are not within the scope of this test plan.
3. QUALITY OBJECTIVES
3.1 Primary Objectives
The primary objective of testing is to ensure that the system meets all functional and non-
functional requirements as per the specifications. It also aims to verify that the system satisfies
business use case scenarios and maintains the overall quality of service. By the end of
development, the system should meet or exceed the client’s expectations, as outlined in the
requirements. Any changes to the requirements during the project lifecycle will be documented,
and testing will adapt accordingly.
3.2 Secondary Objectives
The secondary objectives are to identify and expose all issues, communicate them to the project
team, and ensure all issues are addressed before release. This requires thorough testing to ensure
that the system functions as expected and any bugs are properly resolved.
4. TEST APPROACH
The test approach will be requirements-based and follow an analytical strategy to create,
estimate, and plan tests. Test cases will be developed during exploratory testing, while testers
will leverage their experience with similar systems to perform error guessing. Since the project
uses an agile methodology with weekly iterations, testing will occur at the end of each iteration,
ensuring all delivered requirements are thoroughly tested.
4.1 Test Automation
Automated testing will be a key part of the process. Unit tests will be automated during
development, and functional, UI, regression, and compatibility testing will be automated using
tools like Selenium. Performance data will be captured during the process.
5. ROLES AND RESPONSIBILITIES
Staff
Role Responsibilities
Member
Manage the overall project schedule and communicate with the
Project Manager
development and QA teams.
Plan and organize test processes, coordinate QA activities, and
QA Lead
report progress to the PM.
Understand requirements, create and execute test cases, report
QA Analysts
defects, and manage test data.
Ensure test plan execution, manage defect guidelines, and
Test Lead
communicate changes or issues.
Develop test cases, execute tests, document defects, and retest
Test Team
after fixes.
Development Review test deliverables, assist in validation, and fix defects
Team based on the schedule.
6. ENTRY AND EXIT CRITERIA
6.1 Entry Criteria
All test environments are configured and functioning correctly.
All necessary documentation and design specifications are available.
Required software tools are installed and ready.
Unit testing has been completed and verified.
6.2 Exit Criteria
All high-priority defects have been resolved and retested.
No major outstanding defects remain.
Regression testing has been completed successfully.
Defect reporting and resolution have been properly tracked.
7. SUSPENSION AND RESUMPTION CRITERIA
7.1 Suspension Criteria
Testing will be suspended if:
A critical defect is found that prevents further testing.
The entry criteria are not met.
The system release is unstable or non-functional.
7.2 Resumption Criteria
Testing will resume once the defect is resolved or the entry criteria have been met, starting from
the point of suspension.
8. TEST STRATEGY
8.1 QA Role in the Test Process
The QA team is responsible for ensuring all testing is conducted effectively and according to the
defined guidelines. The QA team will design, execute, and report on all tests.
8.2 Bug Life Cycle
New: The defect is reported and logged.
Assigned: The defect is assigned to the development team.
Open: The developer begins working on the fix.
Fixed: The defect is resolved.
Retest: The QA team verifies the fix.
Closed: The defect is resolved.
Reopen: If the defect is not fixed, it is reopened.
Deferred: The defect is deprioritized for future releases.
Rejected: The defect is invalid or not reproducible.
8.3 Testing Types
Functional Testing: Verifies that the system performs according to requirements.
Usability Testing: Ensures that the BMS interface is user-friendly.
Security Testing: Identifies vulnerabilities.
Compatibility Testing: Ensures the system works across different devices and
platforms.
Performance Testing: Evaluates system stability under load.
8.4 Bug Severity and Priority Definitions
Severity Levels: Blocker, Critical, Major, Minor, Trivial.
Priority Levels: High, Medium, Low.
9. RESOURCE AND ENVIRONMENT NEEDS
9.1 Testing Tools
Selenium, JUnit, or other testing tools for automation.
JIRA for defect tracking.
Git for code versioning.
9.2 Configuration Management
Continuous integration tools like Jenkins.
Testing environments mirrored to development, staging, and production.
9.3 Test Environment
Configured with necessary software and data to simulate real-world scenarios.
Permissions and documentation in place for testing.
10. TEST SCHEDULE
The testing schedule will follow the agile iteration cycle.
At the end of each iteration, tests will be executed and defects will be logged.
Adjustments to the schedule will be based on testing progress and project status.
APPROVALS
The test plan must be approved by representatives from development, QA, and project
management teams.
TERMS/ACRONYMS
QA: Quality Assurance
GUI: Graphical User Interface
RTM: Requirements Traceability Matrix
CI/CD: Continuous Integration/Continuous Deployment
