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

App Platform
,
1

I have just updated an app to FDK 9 but when I run my unit tests with fdk-test I get the following response for each. These worked under FDK8.

{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
3

Hi Rob,

Is this error coming from any API or FDK when running the tests?
Could you give me a direction on how to quickly replicate it on my end?

4

Hi Raviraj,

I think its coming from FDK. See below for the test runner results.

  App Events Tests - onTicketCreate
    ✔ Event blocking test (277ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔ Event blocking test (150ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔ Event blocking test 2 (328ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔ No target match (219ms)
    ✔ Opinyin API Key (200ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔  TP detection (214ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔  TP detection (210ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔ TP detection (171ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔ TP detection (185ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔ Opinyin Submit Fail (169ms)

  App Events Tests - OnTicketUdpate
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔ Ticket updated that is newly assigned to configured group (145ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔ Ticket updated that is newly assigned to configured group (191ms)
    ✔ Ticket updated that is newly assigned to configured group (185ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔ Ticket updated that is not newly assigned to the group (174ms)
    ✔ Changes mmissing (190ms)

  App Events Tests - onAppInstall/onAppUninstall
    ✔ App install (189ms)
    ✔ App uninstall (119ms)

  App Events Tests - onScheduledEvent
    ✔ resend for analysis (168ms)
    ✔ no action type (167ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}
    ✔ send description (183ms)
{
  status: 502,
  headers: {},
  response: 'Error in establishing connection',
  errorSource: 'APP'
}


  20 passing (6s)
5

I couldn’t exactly guess where it was coming from.

Could you check one of the passing cases manually locally and see if the error appears? If so, could you add more logs and see which functionality throws this error?

If it’s not thrown if tested manually and only occurs with the test framework, I can get the app privately and test it at our end.

6

OK. I am on something else at the moment but as soon as I get back on to the app I will try this out.

8

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