Testing framework (fdk-test) returns 502 errors with FDK9.7

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.

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.