How alijansqa/parabank-sqa-testing-suite works
This repository is a documentation-based SQA suite for testing the ParaBank demo banking application, not an application implementation. The principal workflow is to define scenarios and validation rules, execute manual and API checks against ParaBank, record outcomes and evidence, link failures to defects, and summarize results. The README documents seven workbook tabs and their roles; the repository tree lists the workbook as ParaBank.xlsx, although the README names it differently. No source excerpts are available, so the graph reflects documented workbook workflows only.
Main entry points: ParaBank.xlsx Test cases
Components 10
Test design
- Test scenarios
ParaBank.xlsx - Decision table
ParaBank.xlsx - Test cases
ParaBank.xlsx
Test execution
- API testing log
ParaBank.xlsx - API evidence
ParaBank.xlsx
Results and reporting
- Bug report
ParaBank.xlsx - Test summary
ParaBank.xlsx
Other components
- QA tester
- ParaBank demo
- Postman
Connections 16
- QA tester → Test scenarios: defines coverage
- QA tester → Decision table: designs rules
- Test scenarios → Test cases: guides test cases
- Decision table → Test cases: informs validation
- QA tester → Test cases: executes manually
- Test cases → ParaBank demo: checks UI behavior
- QA tester → Postman: runs API checks
- Postman → ParaBank demo: sends API requests
- ParaBank demo → API testing log: returns responses
- QA tester → API testing log: records results
- API testing log → API evidence: documents responses
- Test cases → Bug report: links failures
- QA tester → Bug report: logs defects
- API testing log → Test summary: contributes metrics
- Test cases → Test summary: contributes outcomes
- Bug report → Test summary: informs sign-off