But in acceptance tests, we use a pretender. We would return proper JSON and it would pass. But the problem that this PR and the previous one are fixing is the lack of information that the server returns.
An acceptance test wouldn’t catch this bug.
I can add an acceptance test though, but anyway we should decide if we want to leave these pretty weird server tests in the code base. I agree that they are pretty weird, that’s why I didn’t add tests in the beginning.
I would leave them, cause they do the job and document current implementation.
Then later we can move this logic to the server.