Project: ParaBank Manual Testing Project
Application: ParaBank
Version: 1.0
Prepared by: Filip Jelinek
The purpose of exploratory testing is to evaluate the application’s behavior beyond predefined test cases by simultaneously learning, designing, and executing tests. This approach helps identify unexpected defects, usability issues, and inconsistencies that may not be covered by scripted testing.
Session Goal:
Explore the ParaBank application from the perspective of a new banking customer and identify functional issues, UI inconsistencies, validation problems, navigation defects, and unexpected application behavior.
| Item | Details |
|---|---|
| Application | ParaBank |
| URL | https://parabank.parasoft.com/ |
| Browser | Google Chrome |
| Operating System | Windows 11 |
| Testing Type | Manual Exploratory Testing |
The following application areas were explored during the session:
The following exploratory techniques were used:
During the exploratory session, attention was given to:
The following risks were explored:
| Area | Risk |
|---|---|
| Registration | Invalid account creation |
| Login | Authentication failures |
| Transfers | Incorrect transaction processing |
| Bill Payment | Missing validation |
| Loan Requests | Invalid approval logic |
| Navigation | Broken links |
| Session Management | Unauthorized access after logout |
Examples of findings that may be discovered during exploratory testing include:
Detailed defects are documented separately in the Bug Reports section.
Based on the exploratory session:
| Item | Result |
|---|---|
| Session Type | Session-Based Exploratory Testing |
| Application Coverage | Core Banking Features |
| Test Status | Completed |
| Defects | See Bug Reports |
| Notes | Exploratory testing complemented scripted functional testing. |
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | YYYY-MM-DD | Filip Jelinek | Initial version |
⬅️ Back to QA ParaBank README