[codex] Add auth page component coverage#277
Conversation
|
@barry01-hash is attempting to deploy a commit to the Emmanuel Dorcas' projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@barry01-hash Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
|
@barry01-hash resolve conflicts |
|
This PR has merge conflicts. Please rebase on latest |
2 similar comments
|
This PR has merge conflicts. Please rebase on latest |
|
This PR has merge conflicts. Please rebase on latest |
|
Please merge |
|
This PR has merge conflicts. Please rebase on latest |
|
This PR has extensive merge conflicts with |
Closes #238
Summary
Why
The auth routes are high-traffic entry points and previously had no component-level regression coverage on v2. The pages were still placeholders, so the requested behaviors also required implementing the corresponding forms and API integration.
Impact
Users now have functional, accessible auth forms on v2. Future changes to authentication behavior are protected by 25 focused component tests, with every request intercepted through MSW.
Validation
npm run test- 5 files, 25 tests passednpm run lint- passednpm run build- passed