Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Discover Autocomplete] TESTID-80: Autocomplete Languages - DQL, SQL, PPL - Verify field names appear in valid contexts #8965

Open
LDrago27 opened this issue Nov 27, 2024 · 0 comments
Labels
discover_2.0-test Issues that are specific to the Discover 2.0 testing initiative

Comments

@LDrago27
Copy link
Collaborator

Objective

Each language has a place or places where field names are expected to appear. This differs from how keywords are generated based on the language, and so is a potential point of failure. This test ensures that the field names are being delivered properly as well as appear in the right places.

What to test

Data type:

  1. Index Patterns

  2. Indexes

  3. S3 Connections (future)

  4. Cloudwatch

  5. Security Lake

Language:

  1. DQL

  2. PPL

  3. SQL

Scenario Steps Expected result Notes
Example (See below)
DQL
  • Click into the query editor
  • The very first suggestions should contain field names
  • The suggestions should be the same as the fields that appear in the sidebar, i.e. the fields for the selected dataset
  • The datasets contain duplicate fields which get filtered out, that appear with .keyword appended. Tests should include these types of datasets.
PPL
  • Start forming the query `source =
to get all basic PPL commands.</li><li>Write inwhere.</li><li>Verify that the next suggestions include all the fields in the current dataset.</li><li>Repeat 2-3 for eval, grok, parse, patterns`.
  • The suggestions should be the same as the fields that appear in the sidebar, i.e. the fields for the selected dataset
SQL
  • Write SELECT and check that field names appear in the suggestion window.
  • Write a new query SELECT * FROM <table> to get all basic SQL commands.
  • Write in WHERE.
  • Verify that the next suggestions include all the fields in the current dataset.
  • Repeat 3-4 for HAVING, ORDER BY, and other cases where an expression might appear.
  • The suggestions should be the same as the fields that appear in the sidebar, i.e. the fields for the selected dataset.
  • The datasets contain duplicate fields which get filtered out, that appear with .keyword appended. Tests should include these types of datasets.

Pre-requisites

Steps to setting up the scenario

  1. Have at least 1 existing workspace with index patterns

  2. Turn query enhancements on

  3. Select the index pattern

  4. Select the language for the test

Known Issues

List of known issues to reference that could impact the results of this test case

@LDrago27 LDrago27 added the discover_2.0-test Issues that are specific to the Discover 2.0 testing initiative label Nov 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discover_2.0-test Issues that are specific to the Discover 2.0 testing initiative
Projects
Status: Todo
Development

No branches or pull requests

1 participant