Complete Agile SDLC Documentation for a Personal Expense Dashboard Web Application

Testing strategy, test cases, defect control, and evidence

Testing activity

Testing occurs during every sprint. Sprint 4 adds full release regression and UAT but does not postpone quality verification from earlier iterations.

Test levels

• Unit: calculations, validation rules, budget utilization, reporting helpers.
• Integration: authentication, persistence, authorization, database queries, reporting aggregation.
• System: complete browser-based workflows.
• Regression: previously accepted features.
• Security: ownership bypass attempts, session behavior, validation, sensitive-data exposure.
• Accessibility: keyboard navigation, labels, focus, status communication, contrast, semantic structure.
• Performance: dashboard and transaction-list behavior under expected initial workload.
• UAT: Product Owner verifies release-critical business scenarios.

TC-03A — Create valid expense

1. Authenticate as User A.
2. Open Add Transaction.
3. Enter Expense, amount 75.50, category Food, a valid date, and optional note.
4. Save.

Expected result: One transaction is created for User A and the selected month's expense total increases by 75.50.

TC-03B — Reject zero transaction amount

Input: Amount = 0.
Expected result: Save is rejected and an accessible validation error explains that the amount must be greater than zero.

TC-05A — Calculate budget utilization

Precondition: Monthly budget = 1,000.00 and qualifying expenses = 650.00.
Expected result: Dashboard displays 650.00 spent, 350.00 remaining, and 65% utilization.

TC-05B — Identify exceeded budget

Precondition: Monthly budget = 1,000.00 and expenses = 1,050.00.
Expected result: Dashboard identifies an exceeded budget with text and displays 105% utilization.

TC-SEC-01 — Prevent cross-user transaction access

Precondition: User A owns transaction T100 and User B is authenticated.
Action: User B requests T100 directly.
Expected result: Access is denied and User A's transaction data is not returned.

TC-08A — Verify monthly trend calculations

Expected result: Income and expense totals displayed for each month exactly match the underlying qualified transactions.

Defect severity

• Severity 1: data loss, security breach, or application unavailable.
• Severity 2: core financial workflow unusable or materially incorrect.
• Severity 3: significant degradation with a practical workaround.
• Severity 4: minor usability or cosmetic defect.

Testing exit criteria

• All committed acceptance criteria have corresponding verification evidence.
• No open Severity 1 or Severity 2 defects remain.
• Regression suite passes.
• Security-critical test cases pass.
• Release-critical accessibility checks pass.