1.7 KiB
1.7 KiB
16. TESTING AND DEPLOYMENT GUIDE
Current Testing State
E2E Auth Flow Test (PASSED - 2026-04-01)
We have successfully executed the complete Identity & Onboarding E2E test inside the sf_api container.
Prerequisites Configuration
Before the test run, SSoT configuration values were injected into system.system_parameters:
auth_remember_me_days: 30auth_refresh_default_days: 1auth_password_strict: True
Executed Scenarios & Results
-
LITE REGISTRATION TEST - PASSED
- Successfully registered
test_architect@example.comwith a complex password. - Database confirmed
is_active=Falsefor both User and Twin Person.
- Successfully registered
-
EMAIL VERIFICATION TEST - PASSED
- Token retrieved from
identity.verification_tokens. - Endpoint
POST /auth/verify-emailprocessed the token. - Fixed an architectural bug where
is_activewas not updated correctly upon token validation. It now updates the status toTruesuccessfully.
- Token retrieved from
-
REMEMBER ME / COOKIE TEST - PASSED
- Performed
POST /auth/loginwithremember_me=true. - Fixed missing
Set-Cookieheader logic. The API now correctly returnsrefresh_tokenas anHttpOnly,Secure,SameSite=laxcookie withMax-Agealigned to SSoT (30 days).
- Performed
-
SOFT DELETE / ANONYMIZATION TEST - PASSED
- Verified that
AuthService.soft_delete_useranonymizes the email prefixing withdeleted_. - Record
is_activeset toFalseandis_deletedset toTrue.
- Verified that
Deployment Checklist (API)
- Database Sync Engine verifies SSoT variables.
- SSoT configurations drive
auth_serviceparameters. - Hybrid authentication token delivery works per specification.