Add unit tests for API login endpoint #83
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds unit tests for the login functionality in the API to verify the correct creation of a JWT token.
Implementation details:
AppVecinos.API.Tests
with xUnit, TestHost, and Moq dependenciesLogin_WithValidCredentials_ReturnsToken
: Verifies that a valid JWT token is returned when correct credentials are providedLogin_WithInvalidCredentials_ReturnsUnauthorized
: Verifies that an Unauthorized response is returned when invalid credentials are providedTesting strategy:
The tests use the TestHost to create an in-memory test server that simulates HTTP requests to the login endpoint. This approach ensures we're testing the actual endpoint behavior without needing to deploy the API.
The mock setup allows us to test both successful and unsuccessful authentication scenarios by controlling what the
NeighborService
returns.Fixes #82.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.