Skip to content
This repository was archived by the owner on Dec 14, 2025. It is now read-only.
This repository was archived by the owner on Dec 14, 2025. It is now read-only.

Refactor test architecture #377

@JMyrtue

Description

@JMyrtue

Description

In the current version of the project there exist two testing projects, one for unit tests, and one for integration tests. However, the project concerning unit tests does not test isolated units, this is mainly because in the previous architecture of the web-api, functionality was placed in private methods on endpoints and on models, making it difficult to test.

The work performed on the web-api this semester, have created a new architecture for the repository, which have increased the separation of concerns. This makes it possible to restructure the test cases, to in fact create isolated test cases, thereby ensuring that the smaller units work as intended.

Possible Suggested Solution

  • Examine test cases in the unit-test project, and determine if they test a unit of not. If they do not, consider refactoring it to the integration test project, and replace it with a unit test.
    • If the functionality is already tested similarly in the integration test project, consider if the test case can be deleted to be replaced by a smaller unit test.
  • Cross-reference with the service project, to ensure that all units are correctly tested. If they are not, create unit tests for the functionality.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions