Book Controller Integration Tests

[GaProgMan]

Description

Currently, all controllers are tested using unit tests. This is useful, as we can ensure that the controller action methods when instantiating an instance of the controller class do indeed work. However, we have no way of actually knowing, in a programmatic way, whether HTTP calls through to the routes described on those controllers actually work correctly.

As such, add a set of integration tests for both of the GET endpoints on the BookController controller class.

High-Level Proposed Solution

• Create a test csproj for integration tests
• Ensure that we are using the WebApplicationFactory of Startup from the BookApi csproj
• Write integration tests which test the following scenarios:
  • api/Book/GET returns a 200 OK response when the provided GUID is valid
  • api/Book/GET returns a 400 Bad Request response when the provided GUID is invalid
  • api/Book/GET returns a 404 Not Found response when no GUID is provided
  • api/Book/GetPaged returns a 200 OK response when the provided POCO is valid
  • api/Book/GetPaged returns a 400 Bad Request response when the provided POCO is invalid
  • api/Book/GetPaged returns a 404 No Found response when the provided POCO is not present
  • This is not an exhaustive list
  • Also include tests on the returned data (if applicable)

Considerations

• We will need to ensure that the best practices and advice from the documentation on Integration tests in ASP .NET Core are followed.
• All tests should complete successfully before committing any code.
• GitHub Action should be monitored when commits have been made

Requirements

• An integration tests project is created (perhaps called bookApi.IntegrationTests)
  • Potentially rename the existing bookApi.Tests to bookApi.UnitTests, or similar
• Integration tests for both of the GET endpoints are created
• All tests pass