Test Plan

Document Change Control

List Of Approvers

Project Overview

1.       Introduction

1.1 Purpose

This Test Plan defines the scope, approach, resources, schedule, risks, and exit criteria for testing the EA web application features delivered in Sprints 1–8. It provides one reference for planning and controlling manual UI, integration (via UI flows), smoke, sanity, regression, usability, and UAT support activities executed by one tester (Moataz) for the EA module areas (Beneficiary Experience / UX and Cybersecurity structure).

1.2.        Scope

In Scope (this release)

• Manual UI functional testing for all new/changed screens delivered in Sprints 1–7.
• End-to-End integration testing between the Process Engine and EA Business Layer.
• Visual Designer (BPMN) validation and logic synchronization.
• Analytics & Heatmaps data accuracy and reporting exports.
• Smoke testing on each new build to confirm the stability of core navigation and CRUD.
• Sanity testing during sprint execution on the latest deployed features.
• Integration testing (UI-level) across modules/structures to ensure relationships appear correctly (e.g., metamodel relations, diagrams, cross-structure linking).
• Regression testing on impacted areas (menus, relations, status/state, common components).
• Usability testing (basic): Arabic RTL alignment, labels, validation messages, readability.
• UAT support testing with Product Owner (verification + evidence).
• Sprints in scope (1-8)
• Sprint 1 : EA - البنية المؤسسية > EA - Sprints > Sprint 1 (11/27 - 12/11)17
• 
  
• Sprint 2 : EA - البنية المؤسسية > EA - Sprints > Sprint 1 (11/27 - 12/11)17
• Sprint 3 : EA - البنية المؤسسية > EA - Sprints > Sprint 3 (1/4 - 1/17)28 
• Sprint 4 : EA - البنية المؤسسية > EA - Sprints > Sprint 4 (1/18 - 2/1)26 
• Sprint 5 : EA - البنية المؤسسية > EA - Sprints > Sprint 5 (2/2 - 2/16)24 
• Sprint 6 : EA - البنية المؤسسية > EA - Sprints > Sprint 6 (2/17 - 3/3)39 
• Sprint 7 : EA - البنية المؤسسية > EA - Sprints > Sprint 7 (3/4 - 3/17)32Sprint 7 : EA - البنية المؤسسية > EA - Sprints > Sprint 8 (3/18 - 3/31)8

Out of Scope (this release)

• API testing
• Automation testing
• Performance/load / stress testing
• Security/penetration testing
• Accessibility testing (formal WCAG pass)
• Mobile app testing (only basic responsive sanity if needed)

Environments

• Test Environment (Primary)
• No Stage environment available

2.       Test Basis

• Product backlog/user stories & acceptance criteria in ClickUp.
• Sprint planning + demo notes (treated as requirements where no formal BRD/SRS exists).
• Screenshots and UI references shared by the team.
• Data dictionaries (where provided) are considered the source of truth for fields, validations, and relationships.

#	Source Work Product	Source Work Product	Information Extracted
1	Click Up User Stories & Acceptance Criteria	EA - البنية المؤسسية > EA - Backlog > Enterprise Architecture Backlog118	Business rules, field behaviors, workflow steps, role/permission expectations, and pass criteria per story.
2	Data Dictionaries / Field Specs (attached in stories)	EA Data dictionaryGoogle Sheet•Spreadsheet•188.3 KB• Feb 17	Field names (EN/AR), types/lengths, mandatory flags, default values, validation rules (e.g., Max Score, Required Minimum Score, item count logic).
3	Project Doc	Day 01 - تطبيق إطار...ؤسسية (1).pdf     .pdf (Attached)

3.       Approach

3.1 Test Process (Agile / Sprint-based)

• Test design per story: derive test cases from AC + UI screenshots + data dictionary.
• Execute daily sanity on the latest build during the sprint.
• Log defects in ClickUp with evidence (screenshots/video + STR + expected vs actual).
• Conduct a smoke test after each deployment/hotfix.
• Run regression subset before sprint closure/demo (focused on impacted areas).
• Support PO during UAT with guided scenarios and defect triage.

3.2 Entry Criteria

• Feature deployed to the test environment.
• User story has a clear AC and menu path.
• Required master data exists (or is provided by dev/PO).
• Build passes basic login + navigation (smoke-ready).

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 (Sprints 1–8)

• 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 unusable / data corruption / cannot log in/core flow blocked.
• High: Major feature broken, no workaround.
• Medium: Feature issue with workaround, incorrect validations, and UI logic.
• Low: Cosmetic/minor usability/label issue.

4.        Features to be tested\not to be tested

4.1 Sprint 1 – Delivered ScopeBeneficiary Experience (UX)

• Create a New Main Structure – Beneficiary Experience (البنية تجربة المستفيد)
• Personal Menu Definition – Persona (الشخصية)
• Definition of the Beneficiary menu (المستفيد)
• Definition of Sub-stage (المرحلة الفرعية)
• Definition Menu Step (الخطوة)
• Definition of the User Journey menu (رحلة المستفيد)

Cross-cutting

• Navigation to structures, lists, form views, basic CRUD, search, filters
• Basic relations are available through UI

4.2 Sprint 2 – Delivered ScopeCybersecurity Structure

• Create a New Main Structure – Cybersecurity Structure (بنية الأمن السيبراني)
• Security Apparatus List Definition (جهاز الأمن)
• Definition of a Security Software list (برمجية الأمن)
• Security Service Menu Definition (خدمة الأمن)
• Cybersecurity Architecture Relationships (العلاقات)

UX Governance

• Beneficiary Experience Governance and Control

Other

• Governance and monitoring of cybersecurity infrastructure (as listed)
• Full integration testing cycle (task)
• Enhancements on the last 2 layers (as listed)
• EA Learning & config EA (as listed)

4.3 Sprint 3 – Delivered ScopeEnterprise Architecture Principles (مبادئ البنية المؤسسية)

• Definition of Application Principles Component (مبادئ التطبيقات)
• Definition of Data Principles Component (مبادئ البيانات)
• Definition of Technology Principles Component (مبادئ التقنية)
• Definition of Cybersecurity Principles Component (مبادئ الأمن السيبراني)
• Verification of mandatory fields, domain checkboxes, and multi-line text wrapping across all principal forms.

4.4 Sprint 4 – Delivered ScopeStrategic Alignment & Objectives (الموائمة الاستراتيجية والأهداف)

• Definition of Vision & Mission Components (الرؤية والرسالة), including Goal relations.
• Unification of Objectives in the General Model Graphic (توحيد الأهداف).
• Restructuring of Strategic Alignment: Relocation of "Projects, Packages, and Initiatives".
• Relocation of "Gaps and Phases" to the Settings module.
• Menu & Visual Reordering enforcement (Vision -> Mission -> Objective -> Pillar -> Initiative -> Project -> KPI).

4.5 Sprint 5 – Delivered ScopeBusiness Layer Enhancements (تعديلات طبقة الأعمال)

• Implementation of Business Services Classification Field (Administrative, Core, Support) via radio buttons.
• Addition of the Capability Maturity attribute (High, Medium, Low).
• Addition of Process Group Type attribute (إدارية, محورية, داعمة).
• Validation of Many-to-Many relations between Process Groups, Capabilities, and Data Entities.

4.6 Sprint 6 – Delivered ScopeProcedures & Component Relations (الإجراءات والعلاقات)

• Updates to Procedures Component: Addition of "Organizational Unit", "Applications", and "Group of Procedures" tabs.
• Removal of the "Services" tab from the Procedures component.
• Data Structure Relationships: Definition and mapping of cross-layer relations (e.g., Data Object to Data Asset).
• Validation of new relations within the Meta Model and EA Layer Graphs.

4.7 Sprint 7 – Delivered ScopeTechnology Modifications & Customs (تعديلات التقنية)

• Updates to Equipment Types (Servers, Storage, Peripheral, Network Device) and inheritance rules.
• Definition of new Technical Components (Licenses, Network Link) and "Owning Org Unit" assignment.
• Mapping of Sub-components: "Sub Technical Components" and "Sub Equipment".
• Security linking configuration (Cybersecurity Service, Software, Device) for Tech Components and Equipment.
• Validation of One-to-Many relations between Data Centers and Equipment/Technical Components.

4.8 Sprint 8 – Delivered ScopeUI/UX, Usability & Final Integration

• Dynamic List View Relations: Vertical three-dot icon functionality for dynamic column addition/removal.
• Modifications to Business Services form: "Main Service" conditional logic, Automation Level, Application Steps, Inputs, and SLA metrics.
• Conversion of Business Services to Application relations to Many-to-Many logic.
• Full System Load Testing: Rendering complex EA Layer Graphs with high data volumes.
• End-to-End Regression and Cross-Layer Integration Validation.

5. Test Types Included

• Smoke Testing: core login + main menus + open key lists/forms + create/save one record.
• Sanity Testing: verify new build fixes + core path around changed areas.
• System/UI Testing: validate all AC, validations, transitions, relations, and UI behaviors.
• Integration Testing (UI-level): verify relationships reflected across structures and diagrams.
• Regression Testing: targeted re-test of impacted modules (menus, relations, shared components).
• Usability Testing (basic): Arabic RTL, labels, layout consistency, validations clarity.
• UAT Support: execute PO scenarios and document sign-off.

Not Included: API testing, automation.

6. Test Design Techniques

• Equivalence Partitioning & Boundary Values: required fields, max length, empty states.
• State Transition Testing: status/state flows (Draft/In-review/Posted, change states if applicable).
• Decision Tables: relationship rules, validation constraints (e.g., “cannot relate component to container containing same component” style rules if exist).
• Scenario/E2E Testing: create → relate → verify in diagram/metamodel → update → validate.
• Error Guessing: duplicate relations, missing mandatory fields, wrong language labels, invalid combos.

7. Resources & Roles

Team

• QA (Manual): Moataz
• Developers: Ahmed Youssef, Eslam Rezk
• 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–8)

10. Schedule

Sprint 1: 27/11 → 11/12

• Focus: Beneficiary Experience structure menus + core CRUD + navigation.
• Testing Activities: Daily sanity checks, smoke testing after each deployment, and functional testing of the new UI structures.

Sprint 2: 17/12 → 30/12

• Focus: Cybersecurity structure lists + relationships + UX governance + integration cycle + regression.
• Testing Activities: Daily sanity during the sprint, smoke after each deployment, integration testing of security apparatus links, and regression before sprint demo/closure.

Sprint 3: 02/01 → 15/01

• Focus: Enterprise Architecture Principles (Application, Data, Technology, Cybersecurity).
• Testing Activities: Verification of new form components, mandatory field enforcement, multi-line text wrapping, UI stability, and RTL alignment.

Sprint 4: 18/01 → 31/01

• Focus: Strategic Alignment restructuring, Objectives unification in General Models, and relocation of Gaps/Phases to Settings.
• Testing Activities: Validation of graphical model rendering (unified Objective node), verification of transferred modules, and ensuring existing relational data integrity is maintained.

Sprint 5: 03/02 → 16/02

• Focus: Business Layer modifications including Service Classifications, Capability Maturity, and Process Group Types.
• Testing Activities: Validation of radio buttons logic, testing new Many-to-Many relations between Capabilities and Data Entities, and cross-layer data fetching.

Sprint 6: 19/02 → 04/03

• Focus: Procedures component overhaul (adding Org Units, Apps, Procedure Groups tabs) and Data Structure cross-layer relations.
• Testing Activities: Verifying the removal of deprecated tabs (Services), testing new tab linking mechanisms, and validating Meta Model & EA Layer Graph reflections.

Sprint 7: 07/03 → 20/03

• Focus: Technology Layer modifications (Equipment inheritance, Tech Component definitions) and Security linking.
• Testing Activities: End-to-end testing of One-to-Many and Many-to-Many hardware/software relations, and verifying API dropdown populations.

Sprint 8: 23/03 → 05/04

• Focus: UI/UX finalizations (Dynamic ListView Columns via 3-dot menu), Business Services form enhancements (Main Service conditional logic, SLA), and Final Load Testing.
• Testing Activities: Testing dynamic column addition/removal state management, load testing form rendering with massive relational data, and comprehensive Final Regression across all EA layers.

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–8)

• 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

Product Risks

• Relationships not reflecting correctly in metamodel/diagram → Mitigation: repeat verification after save/refresh + cross-check from multiple menus.
• Arabic RTL UI issues affecting usability → Mitigation: usability checklist on each major screen.
• Permissions/menu visibility mismatches → Mitigation: role-based checklist (Admin vs standard EA architect if available).

Test Project Risks

• Single tester bandwidth vs scope → Mitigation: prioritize smoke + critical paths + high-risk relationships first.
• 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
  • Top recurring defect categories (relations, validations, UI)

14. Exit & Handover

• PO sign-off per story/test set (ClickUp confirmation).
• Final test summary shared with:
  • Known limitations (out of scope: API/automation/performance/security)
  • Accepted risks / waived defects
  • Recommendations for next sprints (automation smoke pack, API coverage for critical endpoints)