Project: ParaBank Manual Testing Project
Version: 2.0
Prepared by: Filip Jelinek
The purpose of API testing is to validate that the ParaBank application’s backend services respond correctly, reliably, and consistently.
API testing was performed to examine backend behavior independently from the web user interface.
Chrome Developer Tools were used to identify API endpoints and inspect network communication generated by the ParaBank web application.
The discovered requests were then reproduced and validated directly using Postman.
The objectives of API testing were to:
| Tool | Purpose |
|---|---|
| Postman | API request execution and response validation |
| Google Chrome Developer Tools | API endpoint discovery and network inspection |
| GitHub | Test documentation and version control |
| Markdown | API test scenario documentation |
The following API areas were included in the testing scope:
| Area | Status |
|---|---|
| API Endpoint Discovery | Completed |
| Session Authentication | Completed |
| Customer Accounts | Completed |
| Customer Information | Completed |
| Account Details | Tested |
| Open New Account | Tested |
| Fund Transfers | Tested |
| Bill Payments | Tested |
| Loan Requests | Completed |
| Invalid Authentication | Completed |
| Invalid Customer ID Handling | Completed |
API testing was performed using a combination of Chrome Developer Tools and Postman.
The following workflow was used:
JSESSIONID session cookie
when required.This approach allowed the API endpoints to be identified from actual application network traffic rather than relying on assumed endpoint structures.
| API ID | Scenario | Type | Tool | Status |
|---|---|---|---|---|
| API001 | Discover Customer Accounts API Endpoint | API Discovery | Chrome DevTools | PASS |
| API002 | Verify Customer Accounts GET Request | Functional | Postman | PASS |
| API003 | Verify Invalid Authentication | Negative | Postman | PASS |
| API004 | Verify Customer Information Endpoint | Functional | Postman | PASS |
| API005 | Verify Account Details Endpoint | Functional | Postman | Tested |
| API006 | Verify Open New Account Request | Functional | DevTools / Postman | Tested |
| API007 | Verify Transfer Funds Request | Functional | DevTools / Postman | Tested |
| API008 | Verify Bill Payment Request | Functional | DevTools / Postman | Tested |
| API009 | Verify Loan Request Endpoint | Functional | Postman | PASS |
| API010 | Verify Invalid Customer ID Handling | Negative | Postman | PASS |
A total of 10 API test scenarios were documented as part of the ParaBank API testing scope.
The testing included:
JSESSIONID session
cookie.200 OK response validation.401 Unauthorized response validation.400 Bad Request response validation.The Customer Accounts endpoint successfully returned account information when a valid authenticated session was provided.
Requests without valid authentication were rejected with HTTP 401 Unauthorized and the message:
{
"message": "User login required",
"status": 401
}An unsupported customer ID value was rejected with HTTP 400 Bad Request and a structured JSON error response.
ParaBank API endpoints tested during this project use session-based authentication.
Authenticated requests required a valid JSESSIONID
session cookie obtained from an authenticated browser session.
When the Customer Accounts endpoint was accessed without valid authentication, the API returned HTTP 401 Unauthorized.
Chrome Developer Tools were useful for identifying the backend requests generated by the ParaBank web application.
The Fetch/XHR network filter allowed API requests to be separated from standard page resources.
This approach was used to identify API endpoints, HTTP methods, request parameters, and response structures before reproducing requests in Postman.
The Customer Accounts API returned HTTP 400 Bad Request when an unsupported customer ID value was supplied.
The API returned a structured JSON error response containing:
No customer account information was returned.
The Loan Request endpoint successfully processed a direct request through Postman and returned HTTP 200 OK.
During previous manual UI testing, the Loan Request workflow produced an Internal Server Error documented as BUG012 – Loan Request Internal Error.
The different behavior between the UI workflow and direct API execution indicates that additional investigation would be required to determine the exact root cause.
The API test result alone does not confirm whether the defect originates in the frontend, backend integration, request construction, or application state.
The API testing section contains:
qa-parabank/
│
├── 05_API_Testing.md
│
└── 05_API_Test_Scenarios/
│
├── API001 – Discover Customer Accounts API Endpoint.md
├── API002 – Verify Customer Accounts GET Request.md
├── API003 – Verify Invalid Authentication.md
├── API004 – Verify Customer Information Endpoint.md
├── API005 – Verify Account Details Endpoint.md
├── API006 – Verify Open New Account Request.md
├── API007 – Verify Transfer Funds Request.md
├── API008 – Verify Bill Payment Request.md
├── API009 – Verify Loan Request Endpoint.md
└── API010 – Verify Invalid Customer ID Handling.md
The API testing performed in this project represents introductory practical API validation as part of a broader manual testing portfolio project.
The primary objective was to gain practical experience with API endpoint discovery, Postman request execution, session authentication, HTTP status validation, JSON response analysis, and negative API testing.
More advanced API testing techniques, including Postman collections, environment variables, automated test scripts, schema validation, and collection execution, are outside the scope of this ParaBank project and may be covered in a dedicated API testing project.
| Version | Date | Author | Changes |
|---|---|---|---|
| 1.0 | 2026-07-11 | Filip Jelinek | Initial API testing plan |
| 2.0 | 2026-07-11 | Filip Jelinek | Updated API scope, documented executed scenarios, testing approach, and API observations |
⬅️ Back to QA ParaBank README