Subterfuge-Revived / Remake-Backend

Server side validation and API

Creative Commons Zero v1.0 Universal

10 stars 1 forks source link

WIP: Feature/unit tests #40

Open griendt opened 3 years ago

griendt commented 3 years ago

Description

Automated unit tests. These can be run from PhpStorm or through the Laravel CLI via:

docker-compose exec app php artisan test

Type of change

Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update
New dependencies/packages

Testing

[x] I have created automated tests for any new features (that's the point of this PR)
[x] All automated tests pass
[x] I have performed manual tests

Checklist:

[x] I have performed a self-review of my own code
[x] I have commented my code
[x] I have documented any new API endpoints in the postman collection
[x] I have added examples in postman for all status codes.
[x] I have made corresponding changes to the README (if required)
[x] My changes generate no new warnings and do not break existing endpoints

To Do

[x] Tests for the Goals API
[ ] Tests for the Rooms API
[ ] Tests for the Room Groups API
[ ] Tests for the Messages API
[ ] Tests for the Events API
[ ] Tests for the leave/join/start room APIs
[ ] Tests for custom middleware:
- [ ] Setting session in the Controller class
- [ ] Response headers (Accept)
- [ ] Validation on REST URIs with multiple (nested) resources
[ ] Add running the tests to a Github Action for CI/CD purposes
Questions / Discussion