BacLuc / ecamp3 / 36870427029

push

github

feat: add FormTestDatum singleton and API form component e2e tests

Add a shared, authenticated singleton entity plus a dev route so the
API-backed form components (ApiTextField, ApiCheckbox, ApiTimePicker, ...)
can be driven and asserted on with Playwright - including the two-tab
"change here, reload there" flow and end-to-end persistence through the
database.

api:
- FormTestDatum entity exposed via API Platform with Get / GetCollection
  / Patch, each secured with is_authenticated(). No create/delete, so the
  single row cannot be multiplied or removed; every authenticated user
  reads and writes that same row. Fields cover each form component type
  (text, multilineText, html, number, flag, color, date, time, language,
  languageMultiselect). Every property carries an ApiProperty example so
  the OpenAPI spec documents a representative value for each field.
- The `time` field is stored as a datetime (in UTC) and exchanged as an
  ISO 8601 string (e.g. "2024-01-15T09:30:00+00:00") via an explicit
  serializer context (DateTimeNormalizer::FORMAT_KEY), which the
  ApiTimePicker / ETimePicker read and write with their default
  valueFormat "YYYY-MM-DDTHH:mm:ssZ". This makes the time field
  updateable and persisted, with a clean API <-> DB round-trip.
- The single row is seeded in the schema migration (not via fixtures) so
  it exists in every environment, including production. Its id is fixed
  (0123456789ab). The migration is the newest schema migration, so its
  INSERT runs after the dev-data seeding (which truncates) and survives.

frontend:
- /api-form-test/:component (dev only, auth required) renders the named
  API component bound to the singleton (?path= chooses the field), shows
  the persisted value in [data-testid="api-form-test-value"], and offers
  a reload button to re-fetch the entity from the API.

e2e (in e2e/9-behavior-tests/components/form/api/):
- apiFormComponentTest: opens two tabs sharing one session, edits the
  field in tab A ... (continued)

837 of 4693 branches covered (17.84%)

Branch coverage included in aggregate %.

0 of 46 new or added lines in 2 files covered. (0.0%)

4691 of 10962 relevant lines covered (42.79%)

63.31 hits per line