Validation tests

Validation QC verifies that every form input enforces its documented constraints — type, length, format, range, required-ness, cross-field rules — and that the error states render in both EN and AR with clear, locale-correct messages. Validation defects are the second-most-common cause of admin pipeline breakage after referential integrity.

Per-input checklist

• Required fields: empty submit shows the inline error in both EN + AR; the submit button does not silently no-op.
• Text length: input over the documented max-length is truncated or rejected with a clear "max X characters" message (not generic "invalid input").
• Email format: standard RFC-compliant regex. "user@" + "user@domain" + "user@domain." all rejected. "user@domain.co.uk" + "user+tag@domain.com" accepted.
• URL format: must start with http:// or https://, must contain at least one dot in the host. Trailing whitespace is trimmed; otherwise no auto-correction.
• Date format: ISO 8601 only (YYYY-MM-DDTHH:mm:ss±HH:mm). Date pickers emit this format; manual entry rejects loose formats.
• Cross-field rules render at the correct moment: endDate < startDate flashes the error on endDate field (not at submit time only); applicationDeadline > startDate same treatment.
• Bilingual fields: missing AR variant of a required title fails just like missing EN. No fallback to "EN is enough".