How darkpanda-cyber/parabank_web_testing_project works
This repository is a documentation-led QA project, not the Parabank application itself. Its principal workflow is planning manual and basic API checks, designing scenarios and cases, executing checks, then recording defects and summarizing results. The README documents coverage of banking flows and API operations; the remaining files are test artifacts and reports. No source excerpts are available, so the graph shows only relationships documented in the README and does not infer detailed execution or reporting mechanics.
Main entry points: README.md API checks · parabank_Sample_Test_Cases.md Sample cases · parabank_Bug_Report.md Bug report
Components 11
Test design
- Test plan
- Web scenarios
- Sample cases
parabank_Sample_Test_Cases.md
Test validation
- Manual checks
README.md - API checks
README.md
Results and defects
- Execution report
- Bug report
parabank_Bug_Report.md - Test summary
Other components
- QA tester
- Parabank
- Postman
Connections 11
- QA tester → Test plan: creates
README.md - QA tester → Web scenarios: designs
README.md - QA tester → Sample cases: designs
README.md - QA tester → Manual checks: executes
README.md - QA tester → API checks: validates
README.md - Manual checks → Parabank: tests flows
README.md - API checks → Postman: uses
README.md - API checks → Parabank: tests endpoints
README.md - QA tester → Execution report: records results
README.md - QA tester → Bug report: reports defects
README.md - QA tester → Test summary: summarizes findings
README.md