Test Plan
Project: ParaBank Manual Testing Project
Application: ParaBank
Application URL: https://parabank.parasoft.com/
Version: 1.0
Prepared by: Filip Jelinek
1. Purpose
The purpose of this Test Plan is to define the testing strategy,
objectives, scope, resources, schedule, and deliverables for manual
testing of the ParaBank online banking application.
This document ensures that testing activities are organized,
consistent, and aligned with the application’s business
requirements.
2. Project Overview
ParaBank is a web-based online banking application that allows
customers to manage their accounts through a browser.
Main business functions include:
- User Registration
- User Authentication
- Account Overview
- Account Activity
- Fund Transfers
- Bill Payments
- Loan Requests
- Account Management
Since financial applications require high reliability, testing
focuses on verifying that core banking features operate correctly and
consistently.
3. Objectives
The objectives of this project are to:
- Verify that core banking features function correctly.
- Validate user workflows from registration to logout.
- Ensure accurate handling of banking transactions.
- Verify input validation and error messages.
- Identify functional defects.
- Produce professional QA documentation suitable for a testing
portfolio.
4. Scope
In Scope
The following features will be tested:
- User Registration
- User Login
- Logout
- Account Overview
- Account Details
- Open New Account
- Transfer Funds
- Bill Payment
- Request Loan
- Navigation
- Session Management
- Form Validation
- Error Handling
- Basic API validation
Out of Scope
The following activities are excluded from this project:
- Performance Testing
- Load Testing
- Stress Testing
- Security Testing
- Penetration Testing
- Accessibility Testing
- Cross-browser compatibility beyond Google Chrome
- Mobile application testing
5. Testing Types
The following testing approaches will be used:
- Functional Testing
- Exploratory Testing
- Smoke Testing
- Regression Testing
- Negative Testing
- Boundary Value Analysis
- Equivalence Partitioning
- API Testing
6. Test Environment
| Item |
Details |
| Application |
ParaBank |
| URL |
https://parabank.parasoft.com/ |
| Browser |
Google Chrome |
| Operating System |
Windows 11 |
| Testing Type |
Manual Testing |
| API Tool |
Postman |
| Documentation |
Markdown |
7. Entry Criteria
Testing may begin when:
- Application is accessible.
- Test environment is available.
- Test accounts are created.
- Test documentation is prepared.
8. Exit Criteria
Testing is considered complete when:
- All planned test cases have been executed.
- Critical defects have been documented.
- Test execution results are recorded.
- Test Summary Report has been completed.
9. Deliverables
The project will include:
- Test Plan
- Exploratory Testing Notes
- Test Cases
- Bug Reports
- API Testing
- Test Execution Report
- Test Summary Report
- Screenshots
- Video Evidence
10. Risks
Potential testing risks include:
| Risk |
Impact |
| Application instability |
Medium |
| Temporary server downtime |
Medium |
| Test data limitations |
Low |
| Environment changes |
Medium |
| Existing application defects |
High |
11. Assumptions
This project assumes that:
- The application is publicly available.
- Internet connectivity is stable.
- Banking operations use test data only.
- No real financial transactions are performed.
12. Test Completion Criteria
Testing will be considered complete when:
- All planned scenarios have been executed.
- Results have been documented.
- Bugs have been reported.
- Final QA documentation has been reviewed.
Document Version History
| Version |
Date |
Author |
Changes |
| 1.0 |
YYYY-MM-DD |
Filip Jelinek |
Initial version |
⬅️ Back to QA ParaBank README
QA-ParaBank-README.md