Feat: Add unit tests for GetGoalsForUser endpoint#89
Feat: Add unit tests for GetGoalsForUser endpoint#89ronaldfarnandis wants to merge 1 commit intofencer-so:mainfrom
Conversation
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| - | - | MongoDB Credentials | 10ed4ba | CommBank-Server/appsettings.json | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.
To avoid such incidents in the future consider
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.
Summary
This pull request introduces unit test coverage for the
GetGoalsForUsermethod in theGoalController. Adding these tests ensures the endpoint behaves as expected and prevents future regressions.Changes Made
200 OKresponse is returned when a user with existing goals is requested.404 Not Foundresponse is returned when the service cannot find a user or their goals.How to Verify
All new and existing tests in the suite pass successfully.