Add unit test coverage for GetForUser goal controller route#279
Add unit test coverage for GetForUser goal controller route#2791Dhairyak wants to merge 1 commit into
Conversation
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| - | - | MongoDB Credentials | ed9f374 | CommBank-Server/Secrets.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
Adds xUnit test coverage for the
GetForUserendpoint onGoalController, completing the test cases for goal retrieval by user.Changes
GetForUsertest inGoalControllerTests.csIdandNamevalues, following the existing pattern used inGetAllandGetdotnet test: 11/11 tests passing, no regressionsTesting
Ran
dotnet testlocally — all tests pass.