Automated Testing & Quality Assurance Guide

This document details the test suites, execution procedures, assertion metrics, and CI/CD pipelines governing the Eniceberny Bakery and Culinary Hub platform.

1. Test Architecture & Standards

Quality assurance is enforced through comprehensive automated testing using PHPUnit and Laravel's HTTP test utilities:

• Isolated In-Memory Database: All test suites execute against high-speed in-memory SQLite instances (:memory:), guaranteeing complete test isolation without residual side-effects.
• Automated Seeding Integration: Test classes leverage the RefreshDatabase trait with protected bool $seed = true;, ensuring authentic catalog categories, menu delicacies, and role permissions are present during every test run.
• Zero-Mock Financial Verification: Payment callbacks, cart additions, discount deductions, and order conversions are executed against real Eloquent database models.

2. Comprehensive Test Suite Inventory (82 Tests, 378 Assertions)

The platform test suite contains 82 automated tests across six specialized feature test classes:

3. Running Tests Locally

3.1 Run Complete Test Suite

Execute the entire test suite from the repository root:

php artisan test

Expected output:

  PASS  Tests\Feature\AdminTest
  PASS  Tests\Feature\CmsAndBroadcastTest
  PASS  Tests\Feature\ExampleTest
  PASS  Tests\Feature\Phase25ErpAndGhanaComplianceTest
  PASS  Tests\Feature\Phase2CommerceTest
  PASS  Tests\Feature\Phase3OperationsAndCmsTest
  PASS  Tests\Feature\StorefrontTest

  Tests:    82 passed (378 assertions)
  Duration: ~15s

3.2 Run Specific Test Classes or Filters

Target individual feature areas during local development:

# Run only Admin tests
php artisan test --filter AdminTest

# Run only Storefront & Checkout tests
php artisan test --filter StorefrontTest

# Run Ghana compliance and ERP tests
php artisan test --filter Phase25ErpAndGhanaComplianceTest

# Run a specific single test method
php artisan test --filter test_catering_inquiry_can_be_converted_to_official_order

4. Continuous Integration Pipeline (GitHub Actions)

Every pull request and push to the main branch automatically triggers the automated CI/CD pipeline defined in .github/workflows/ci.yml:

graph TD
    A[Push / PR to main] --> B[GitHub Actions Runner: ubuntu-latest]
    B --> C[Setup PHP 8.4 with required extensions]
    B --> D[Setup Node.js 20 with npm cache]
    C --> E[composer install --prefer-dist --optimize-autoloader]
    D --> F[npm ci && npm run build]
    E --> G[Copy .env.example & Generate Key]
    F --> G
    G --> H[php artisan test --colors=always]
    H -->|All 82 Tests Pass| I[Production Render Deployment Trigger]
    H -->|Any Failure| J[Halt & Reject Deployment]

CI Requirements:

• PHP Version: 8.4 (matching production runtime and Symfony 8.1 dependencies).
• PHP Extensions: mbstring, xml, ctype, iconv, intl, pdo, pdo_sqlite, pdo_pgsql, bcmath, gd, zip.
• Node.js: 20.x compiling Tailwind v3 and Vite bundles.
• Coverage: Fast execution without xdebug overhead (coverage: none).