This PR adds an integration suite for Telemetry. There is an added complexity that has been introduced via the authorization provider, in that starting of the telemetry logic happens further, once all the auth checks have been performed and QuestDB provider is set up correctly (i.e. rest token is set for all API requests).
The spec sheet tests the following:
Fetching the Telemetry system config and the correctness of it
When Telemetry is disabled by the user, no request to API should be performed
When Telemetry is enabled, it should contact the lambda API endpoint, sending out the correct payload.
Side changes:
Added cy.interceptQuery(query, alias, response?) utility method for intercepting a given query with an optional response replacing the server one (this takes both a StaticResponse object or a function that can mutate the real server output from origin)
Set up the default command timeout on the config level, which prevents spurious test failures due to slow test execution on the CI level.
Adjusted the node CI console runner script to support settings endpoint proxing.
Removed the unnecessary drop table sqls and speed up autocomplete tests in return
This PR adds an integration suite for Telemetry. There is an added complexity that has been introduced via the authorization provider, in that starting of the telemetry logic happens further, once all the auth checks have been performed and QuestDB provider is set up correctly (i.e. rest token is set for all API requests).
The spec sheet tests the following:
Side changes:
cy.interceptQuery(query, alias, response?)utility method for intercepting a given query with an optional response replacing the server one (this takes both a StaticResponse object or a function that can mutate the real server output from origin)