Small SQL-based QA demo for checking data consistency in a fictional case management and appointment system called CaseDesk.
The point of this repo is not database development. It shows how I use SQL to support functional testing, regression checks, report validation, and basic data quality review.
- relational data checks
- duplicate detection
- missing or suspicious values
- appointment workflow validation
- attendance status checks
- report total reconciliation
- regression-style SQL checks
sql/
schema.sql
seed-data.sql
validation-queries.sql
data-quality-checks.sql
report-reconciliation.sql
docs/
validation-notes.md
qa-checklist.md
sample-output/
expected-findings.md
The SQL files are written to work with SQLite for easy local testing.
sqlite3 casedesk.db < sql/schema.sql
sqlite3 casedesk.db < sql/seed-data.sql
sqlite3 casedesk.db < sql/validation-queries.sql
sqlite3 casedesk.db < sql/data-quality-checks.sql
sqlite3 casedesk.db < sql/report-reconciliation.sqlThe sample data intentionally contains a few questionable records. The validation queries are expected to return findings.
Manual QA work often needs more than screen checking. For business systems, the data underneath has to make sense as well.
This demo shows SQL checks I would use around:
- client registration
- appointment booking
- attendance logging
- report generation
- release regression checks
All data is fictional.