feat(browser-tests): add web console telemetry tests#298
Merged
Conversation
glasstiger
approved these changes
Jul 3, 2024
Vaibhav91one
pushed a commit
to Vaibhav91one/ui
that referenced
this pull request
Oct 28, 2025
* add telemetry tests * Update assertion for disabled telemetry * Adjust the telemetry config query * Clean up after merge * Update grid `beforeEach` hook * Fix intercept path * Adjust grid tests * Update grid tests questdb#2 * Roll back `typeQuery` changes * autocomplete hook change * Remove `typeQuery` from chaining * adjust the query insert method * OSS submodule update
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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)