Chore/Create mock solution for reusability of unittest mocks and data #448
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.
Description
This PR rips the Mock and Mock-data parts out of the test project and establishes a new project solution 'Mocks'. Mocks is then used by Tests for unit testing as previously, but can now also be reused during runtime in Dev whenever UseMockData is set in appsettings.Development.json
This can be benefitial when developing frontend code for backend endpoints that are not yet created, or are for some reason unavailable or broken. It also lessens the need for setup (souch as Database setup and policy files in Azure) before a developer can begin coding in frontend.
Related Issue(s)
Verification
Documentation