Alaqsa website

This document appears to be a quality assurance (QA) and testing report for the ElAqsa website project. It includes structured test cases, a bug report, and the test execution status.

1. Purpose of the Document:

To ensure the functionality and quality of the ElAqsa website.

To identify and document defects found during testing.

To track the status of test cases and bugs.

2. Structure of the Document:

The file contains three main sheets:

A. Checklist Sheet

Contains test cases organized under:

Project Details: Project Name, Tester Name (Ghidaa), Software Version (V1.0), and Date (16/02/2023).

Test Cases: Each test case has:

Test Suite: The category of tests.

Test Title: The specific feature being tested.

Pre-Condition: Requirements before executing the test.

Test Steps: The actions taken to perform the test.

Test Data: Input values used during testing.

Expected Result: What should happen after executing the test.

Actual Result: The observed system behavior.

Status: Whether the test Passed, Failed, or is Not Executed (N/E).

B. Bug Report Sheet

A detailed defect tracking log that records:

Defect Reports (e.g., "Defect Report 1", "Defect Report 2", etc.).

Multiple defect entries with unknown column names (potentially issue descriptions, severity, priority, and assigned developer).

Likely used to document software issues, UI bugs, functional errors, or performance issues.

C. Status Sheet

A summary of test case execution status, showing:

PASS – Test cases that were successful.

FAIL – Test cases that failed.

N/E (Not Executed) – Test cases that were not executed.

3. Description of Work Performed

Test Planning – The team created test cases to verify website functionality.

Test Execution – The testers executed test cases, recorded actual results, and logged issues.

Bug Tracking & Reporting – Identified issues were documented in the bug report.

Status Monitoring – The QA team tracked test case execution progress.