Create a component that encapsulates the actual communication with the backend API.
The actual fetching of data from the API will not be implemented here, since the API is not created yet.
Create a description of input/output data for each public function.
The test client will only return hardcoded testdata, but the interface should be the same, so that we don't have to change the Content HUB client/app when the API is in place.
The test client should cover the following scenarios:
Errors from the backend (E.g: 500)
Slow network (e.g: 10 seconds to load from backend)
Large sets of search results (so that the paginator may be tested well)
This component is described here: