feat: implement CMS for content management (WEB-02/03/04/06)
Introduces Filament management for site settings, services, portfolio cases, and testimonials with admin-only policies, validated media uploads, and deterministic seeding. Includes comprehensive design and task documentation for the implementation. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
@@ -0,0 +1,16 @@
|
||||
## ADDED Requirements
|
||||
|
||||
### Requirement: Local feature tests use PostgreSQL
|
||||
|
||||
The system SHALL configure `phpunit.xml` so that the Feature test suite uses PostgreSQL with the same connection parameters as CI (`DB_CONNECTION=pgsql`, host, port, database `amare_test`, credentials). Local feature tests MUST NOT default to SQLite `:memory:`.
|
||||
|
||||
#### Scenario: Developer runs feature tests locally
|
||||
|
||||
- **WHEN** a developer runs `composer test:feature` with PostgreSQL available
|
||||
- **THEN** tests MUST execute against PostgreSQL
|
||||
- **AND** MUST NOT silently fall back to SQLite
|
||||
|
||||
#### Scenario: Feature tests exercise PostgreSQL-specific types
|
||||
|
||||
- **WHEN** feature tests persist records with jsonb columns (e.g., `social_links`)
|
||||
- **THEN** migrations and constraints MUST be validated against PostgreSQL semantics
|
||||
Reference in New Issue
Block a user