When you try to run unit tests with fdk-test you get a 502 connection error unless the fdk-run is executed first but if fdk run is operating it keeps resetting the coverage. Previously you didn’t need to have fdk-run executing.
I have seen this before but never got to find out why its happening as due to time pressures we ended up doing manual tests.