Test Plan

Document Change Control

Release No	Release Date	Issued By	Version Comment	ClickUp Version Time
1.0	22/4/2026	Moataz (Moataz Mustafa)	Initial version for the Compliance Management hierarchy and management module.

List Of Approvers

Name	Title	Approved Release No
Tarek Ramadan	Software Engineering Director

Project Overview

Project Manager /Scrum Master

Ahmed Essam

System Under Test (SUT) – Project Name

Compliance Management System (إدارة الامتثال)

Software Under Test Version

V 1.0.0

1. Introduction

1.1. Purpose

This Test Plan defines the scope, approach, and exit criteria for testing the Compliance Management module.It provides a single point of reference for manual UI, integration, smoke, sanity, regression, usability, and UAT support activities.It also includes Load testing for audit trails and synchronization.This plan is executed by a single tester (Moataz) following the Agile methodology for Sprints 1–30.

1.2. Scope

In Scope (this release):

Manual UI functional testing for the structural hierarchy (Perspectives, Axes, Standards, Requirements).
Integration testing between the Master Data layer and the Measurement Period layer.
Smoke testing on each new build to confirm the stability of the compliance dashboard.
Sanity testing on the latest deployed bug fixes or small feature enhancements.
Regression testing on impacted structural layers (e.g., ensuring a change in 'Axes' doesn't break 'Requirements').
Usability testing focusing on the Arabic RTL (Right-to-Left) interface, labels, and validation messages.
Load testing for high-volume synchronization and audit log generation.
UAT support with the Product Owner (providing evidence and verification for MOH and Al-Baha requirements).

Sprints in scope (1-2)

Out of Scope:

API testing.
Automation testing (at this stage).
Mobile app testing (System is web-based).
Formal security/Penetration testing.

2. Test Basis

Test cases are derived from the User Stories, Acceptance Criteria (AC), and UI screenshots.Daily Sanity checks are performed on the latest builds.Smoke tests are mandatory after any deployment or hotfix.Defects are logged in ClickUp with full evidence (STR, Expected vs Actual).Regression testing is targeted at structural cascading (Sync logic).

Source Work Product

Information Extracted

Click Up User Stories & Acceptance Criteria

إدارة الامتثال > Backlog - إدارة الامتثال > Compliance Backlog > List

Business rules, field behaviors, workflow steps, role/permission expectations, and pass criteria per story.

User Guide

إدارة الامتثال - إما...دم (1) (6).pdf

https://t4669532.p.clickup-attachments.com/t4669532/432b9241-dbd3-414b-ba99-938f38a442cc/%D8%A5%D8%AF%D8%A7%D8%B1%D8%A9%20%D8%A7%D9%84%D8%A7%D9%85%D8%AA%D8%AB%D8%A7%D9%84%20-%20%D8%A5%D9%85%D8%A7%D8%B1%D8%A9%20%D8%A7%D9%84%D8%A8%D8%A7%D8%AD%D8%A9%20-%20%D8%AF%D9%84%D9%8A%D9%84%20%D9%85%D9%8F%D8%B3%D8%AA%D8%AE%D8%AF%D9%85%20(1)%20(6).pdf

.pdf وزارة الصحة - إدارة ...امتثال (1).docx

https://t4669532.p.clickup-attachments.com/t4669532/d2ea1271-b77d-40b0-a813-b21314289ecc/%D9%88%D8%B2%D8%A7%D8%B1%D8%A9%20%D8%A7%D9%84%D8%B5%D8%AD%D8%A9%20-%20%D8%A5%D8%AF%D8%A7%D8%B1%D8%A9%20%D8%A7%D9%84%D8%A7%D9%85%D8%AA%D8%AB%D8%A7%D9%84%20(1).docx

Field names (EN/AR), types/lengths, mandatory flags, default values, validation rules (e.g., Max Score, Required Minimum Score, item count logic).

Users Roles

Compliance Users Permissions

You don't have accessGoogle Drive FileFile
You don't have accessGoogle Drive FileFile

مثال لصلاحيات المدقق (مسارات) من اللايف.pdfDocument•PDF•2.75 MB• Oct 14 2025

مثال لصلاحيات رئيس القسم الاستشاري من اللايف.pdfDocument•PDF•2.77 MB• Oct 14 2025

Project Link (Test Env)

اداره الامتثال - Test

3. Approach

3.1 Test Process (Agile / Sprint-based)

Test cases are derived from the User Stories, Acceptance Criteria (AC), and UI screenshots.
Daily Sanity checks are performed on the latest builds.
Smoke tests are mandatory after any deployment or hotfix.
Defects are logged in ClickUp with full evidence (STR, Expected vs Actual).
Regression testing is targeted at structural cascading (Sync logic).

3.2 Entry Criteria

The feature is deployed to the Test environment.
User story has clear AC and defined hierarchy paths.
Smoke test (Login + Dashboard load) passes.

3.3 Exit Criteria

Per Story

All acceptance criteria tested and evidenced.
No open Critical/High defects (unless PO accepts with waiver).
Medium/Low defects documented and prioritized.

Per Sprint / Release

Smoke passes on final build.
Regression subset executed on impacted modules.
UAT scenarios executed with PO sign-off (or documented approval via ClickUp comment).

3.4 Defect Severity

Critical: System crash, data loss during sync, or cannot access main modules.
High: Hierarchy link broken (e.g., Axes not showing under Perspectives), no workaround.
Medium: Validation error issues, incorrect labels, and UI alignment in RTL.
Low: Cosmetic issues, spelling errors in help text.

4. Features to be tested\not to be tested

4.1 Sprints 1–5: Foundation & Master Data SetupInitial setup of the core structural hierarchy (التهيئة).Perspectives (مناظير), CRUD operations, and categorized list views.Axes (محاور) definition and parent-child linking to Perspectives.Configuration of organizational units for multi-tenant isolation (Ministry of Health vs. Al-Baha).Basic navigation and sidebar menu integrity for the Compliance module.4.2 Sprints 6–10: Detailed Requirement HierarchyStandards (معايير) management and logical mapping to Axes.Requirements (متطلبات) include full lifecycle management and description fields.Evidence Management (إرفاق مستندات الإثبات) system design.Field validation logic (Mandatory flags, character limits, and Arabic label alignment).Audit trail initialization for structural changes.4.3 Sprints 11–18: Governance & Workflow LifecycleRequirement status transition engine (New -> Under Implementation -> Approved).Role-Based Access Control (RBAC) validation for Admin vs. Standard User views.Notes and comments thread implementation for collaborative compliance tracking.Evidence verification workflows and document preview functionalities.Notification triggers for status changes and evidence submission.4.4 Sprints 19–25: Measurement Engine & Synchronization LogicMeasurement Period (فترات القياس) specialized management layer.Advanced Import Logic: Copying structures from Master Data or specific previous periods.Synchronization mechanism for cascading structural updates to active measurements.Data Isolation protocols to prevent local edits from affecting the global Master Data.Load testing of the synchronization engine with 1000+ data rows.4.5 Sprints 26–30: Analytics, Reporting & Final StabilizationSprints 26–30: Analytics, Reporting & Final StabilizationCompliance Dashboard KPIs reflecting maturity percentages for Nadi Index domains.Advanced filtering for multi-entity reporting (MOH/Al-Baha/SDAIA).PDF and Excel report generation for compliance summaries and evidence logs.Full Regression testing of the 4-layer hierarchy (مناظير، محاور، معايير، متطلبات).4.6 Features NOT to be testedAutomation testing scripts (Manual testing focus for this release).API endpoint testing (UI-level validation only).Mobile application responsiveness (Project is scoped for Web/Desktop use).

External third-party software integrations outside of the GSB (Government Service Bus).

5. Test Types Included

Smoke Testing: Core login and verification of the 4-layer hierarchy tabs.
Sanity Testing: Quick verification of specific bug fixes in the Evidence module.
System/UI Testing: Full validation of the Arabic UI, field constraints, and mandatory flags.
Integration Testing: Verifying that changes in Master Data do not accidentally corrupt Measurement Periods (Isolation).
Regression Testing: Re-testing the "Add Requirement" flow after a "Sync" update.
Usability Testing: Verification of RTL alignment and Arabic terminology accuracy.
Load Testing: Performance of the "Synchronize" button when managing 1000+ requirements.

UAT Support: Guiding the PO through the approval workflow to ensure it meets MoH standards.

6. Test Design Techniques

Equivalence Partitioning: Validating measurement period date ranges.
Boundary Value Analysis: Testing max file sizes for evidence uploads.
State Transition: Testing the status lifecycle of a compliance requirement.
Error Guessing: Attempting to delete a Perspective that has active linked Requirements.

7. Resources & Roles

Team

QC (Manual): Moataz (only tester)
Developers: Ahmed Youssef, Ahmed Ashraf, and Ahmed Elemam.
Product Owner: Mohsen Wahed
Team Lead: Mahmoud Elbadry

Tools

ClickUp (stories/defects/execution tracking)
Browser dev tools (basic checks)
Screenshots/video capture for evidence
Google Sheets (test data + tracking if needed)

8. Environment

Application: EA Web App (Arabic UI / RTL)
Environment: Test only
Browsers: Chrome (Primary), Edge (Sanity)
Test Data: seeded EA components, beneficiaries/personas/journeys, cybersecurity components, relationships datasets.

9. Testing Tasks & Deliverables

9.1 Testing Tasks

Test case design per story (ClickUp Testcases list / Test set).
Execute story test cases + attach evidence.
Smoke test after deployments.
Regression subset before sprint closure.
Integration cycle execution (relationships + metamodel diagram reflection).
UAT support with PO + triage.

9.2 Deliverables

Test Plan (this document)
Test cases (per story)
Defect reports (ClickUp)
Sprint-level execution summary (Executed/Pass/Fail/Blocked + key defects)
Final Release Test Summary (Sprints 1–29)

10. Schedule (based on your sprint dates)

Sprints 1 – 10: 01/10/2024 → 28/02/2025
Focus: Structural setup (مناظير/محاور) and early Master Data configuration.
Sprints 11 – 20: 01/03/2025 → 31/07/2025
Focus: Hierarchy completion (معايير/متطلبات), Evidence management, and Workflow.
Sprints 21 – 25: 01/08/2025 → 15/12/2025
Focus: Measurement Periods and early Sync logic implementation.
Sprints 26 – 28: 16/12/2025 → 14/03/2026
Focus: Full integration cycle, Load testing, and Analytics dashboard.
Sprint 29: 15/03/2026 → 29/03/2026
Focus: Final Stabilization, Regression cycle, and UAT Sign-off for release.
Sprint 30: 06/04/2026 → 19/04/2026
Focus: Final Stabilization, Regression cycle, and UAT Sign-off for release.

11. Pass/Fail Criteria

Story Pass

All AC verified with evidence.
0 open Critical/High defects (or PO waiver documented).
Medium/Low defects recorded and agreed on priority.

Sprint / Release Pass (Sprints 1–30)

Smoke passes on final build.
Core user flows are stable:
- Open structures → create records → save → search/filter → open form view
- Create relationships → verify reflection (where applicable)
No known Critical/High in production-like usage paths agreed with PO.

12. Risks & Mitigations

Risk: Single tester bandwidth vs 29-sprint comprehensive scope.Mitigation: Prioritize Smoke testing and critical sync logic over cosmetic UI checks.Risk: No Stage environment available for final integration.Mitigation: Perform strict Smoke tests after every deployment to the Test environment.Risk: Data corruption during structural synchronization.Mitigation: Perform dedicated Integration cycles to verify isolation of local Period edits.

Test Project Risks

No formal BRD/SRS → Mitigation: treat AC + data dictionary + demo notes as source of truth, log clarifications in ClickUp comments.
No stage environment → Mitigation: strict smoke after each deployment + keep regression subset stable.

13. Reporting

Daily progress updates in ClickUp comments or QA notes.
Defect triage with Team Lead/Devs (daily or as needed).
Sprint demo support with PO and capture UAT notes.
Metrics for summary:
- Executed/Passed/Failed/Blocked
- Defects by severity
- Reopen rate