Test Plan: QA Issue Tracker

1. Introduction

This document outlines the test strategy, scope, and approach for the QA Issue Tracker module of the MemberVu application. The QA Issue Tracker enables internal bug reporting and issue management, allowing team members to report issues directly from the application with screenshots and contextual information.

2. Scope

The testing will cover the following functional areas:

Issue Creation: Creating new QA issues with title, description, severity, screenshots, and page URL context
Issue Workflow: Status transitions through OPEN, IN_PROGRESS, FIXED, VERIFIED, and CLOSED
Issue Filtering & Search: Filtering issues by status, severity, assignee, reporter, and date range
Comments & Discussion: Adding, editing, and deleting comments on issues with threading support

3. Test Strategy

3.1 Testing Levels

Level	Approach	Tools
Unit Testing	Developer-owned (Jest/Vitest)	Jest, Vitest
API Testing	Backend endpoint validation	Postman, curl, integration tests
E2E Testing	Full UI workflow testing	Playwright, Cypress
RBAC Testing	Permission verification across roles	Manual + API tests

3.2 Test Types

Functional Testing: Verify all CRUD operations work correctly
Negative Testing: Validate error handling for invalid inputs
Boundary Testing: Test limits on input lengths, file sizes
Permission Testing: Verify access control per role
Integration Testing: Verify frontend-backend communication

4. Environment

Component	Location
Frontend Pages	`frontend/pwa-app/src/pages/AdminQaIssuesPage.tsx`, `MyIssuesPage.tsx`
Frontend Components	`frontend/pwa-app/src/components/qa/`
Frontend Hooks	`frontend/pwa-app/src/hooks/useQaIssues.ts`, `useQaIssueComments.ts`
Backend Handlers	`auth-service/src/handlers/qaIssueHandlers.ts`, `qaCommentHandlers.ts`
Database	PostgreSQL (Prisma ORM)

5. Data Model Reference

QaIssue

Field	Type	Description
id	String	Primary key (CUID)
tenantId	String	Tenant context
title	String	Issue title
description	String	Detailed description
severity	IssueSeverity	LOW, MEDIUM, HIGH, CRITICAL
status	IssueStatus	OPEN, IN_PROGRESS, FIXED, VERIFIED, CLOSED
pageUrl	String	URL where issue was reported
screenshot	String?	Optional screenshot URL
reportedBy	String	Reporter user ID
assignedTo	String?	Assignee user ID
createdAt	DateTime	Creation timestamp
updatedAt	DateTime	Last update timestamp
resolvedAt	DateTime?	Resolution timestamp

QaIssueComment

Field	Type	Description
id	String	Primary key (CUID)
content	String	Comment text
screenshot	String?	Optional screenshot URL
issueId	String	Parent issue ID
authorId	String	Comment author ID
createdAt	DateTime	Creation timestamp
updatedAt	DateTime	Last update timestamp

6. Roles & Permissions

Role	Create Issues	View Own	View All	Assign	Change Status	Delete
MEMBER	Yes	Yes	No	No	No	No
OFFICER	Yes	Yes	Yes	Yes	Yes	No
ADMIN	Yes	Yes	Yes	Yes	Yes	Yes

Permission Matrix Details

All Users: Can create issues, view their own reported issues, add comments to accessible issues
OFFICER: Can view all issues, assign to team members, change issue status
ADMIN: Full access including delete operations

7. API Endpoints Under Test

Issue Endpoints

Method	Endpoint	Description
GET	`/api/qa/issues`	List issues with filtering
GET	`/api/qa/issues/:id`	Get issue details
POST	`/api/qa/issues`	Create new issue
PATCH	`/api/qa/issues/:id`	Update issue
DELETE	`/api/qa/issues/:id`	Delete issue (Admin only)

Comment Endpoints

Method	Endpoint	Description
GET	`/api/qa/issues/:id/comments`	List issue comments
POST	`/api/qa/issues/:id/comments`	Add comment
PATCH	`/api/qa/comments/:id`	Update comment
DELETE	`/api/qa/comments/:id`	Delete comment

8. Test Data Requirements

Required Test Users

User	Role	Purpose
Admin User	ADMIN	Full access testing
Ana Reyes	OFFICER (FINANCE_MANAGER)	Officer-level testing
Maria Cruz	MEMBER	Regular member testing
Miguel Fernandez	PENDING_MEMBER	Restricted access testing

Sample QA Issues for Testing

Issue ID	Title	Severity	Status
QA-001	Button alignment on mobile	LOW	OPEN
QA-002	Form validation error	MEDIUM	IN_PROGRESS
QA-003	Payment gateway timeout	HIGH	FIXED
QA-004	Data loss on page refresh	CRITICAL	VERIFIED
QA-005	Archived issue for history	LOW	CLOSED

9. Test Case Summary

Test Case ID	Test Case Name	Priority
TC_QA_001	Issue Creation	P1 - Critical
TC_QA_002	Issue Workflow	P1 - Critical
TC_QA_003	Issue Filtering	P2 - High
TC_QA_004	Issue Comments	P2 - High

10. Entry Criteria

QA module is deployed and accessible
Test database is seeded with required test users
API endpoints are functional
Frontend pages render without errors

11. Exit Criteria

All P1 test cases pass
At least 90% of P2 test cases pass
No critical or high-severity bugs remain open
All RBAC permissions verified

12. Risk Assessment

Risk	Likelihood	Impact	Mitigation
Screenshot upload failures	Medium	Medium	Test with various file types and sizes
Status transition edge cases	Low	High	Thoroughly test all valid/invalid transitions
Permission bypass	Low	Critical	Test each role exhaustively
Concurrent edits	Medium	Medium	Test optimistic locking behavior

13. Test Deliverables

Test Cases (TC_QA_001 through TC_QA_004)
Test Execution Reports
Bug Reports (using BUG_REPORT_TEMPLATE.md)
Final Test Summary Report

14. Related Documentation

QA.md - Feature specification
00_MASTER_TEST_DATA.md - Test data reference
ENVIRONMENT_SETUP.md - Environment configuration
BUG_REPORT_TEMPLATE.md - Bug reporting template