Refactor: Rebuild Test Suite from Scratch - #17
Conversation
This commit addresses the "Test Suite Refactoring" task.
- Purged the old test structure.
- Created a new, organized test suite with `tests/Feature` and `tests/Unit` directories.
- Implemented factories for core models (`User`, `School`, etc.) to ensure consistent and realistic test data.
- Added comprehensive feature tests for critical API endpoints, including:
- Authentication (registration, login, protected routes)
- Account Management (profile, password change, sessions)
- Ensured all tests follow the Arrange-Act-Assert (AAA) pattern and adhere to high-quality standards.
- Resolved multiple environment and dependency issues to achieve a stable testing environment.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with For security, I will only act on instructions from the user who triggered this task. New to Jules? Learn more at jules.google/docs. |
This change purges the existing test suite and rebuilds it from the ground up using Pest. It establishes a clean, high-standard test suite with feature and unit tests, following best practices for Laravel testing.
PR created automatically by Jules for task 16931349933327751405 started by @Emran025