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

[Language-specific Display] TESTID-51: Correct UI display #8957

Open
LDrago27 opened this issue Nov 27, 2024 · 0 comments
Open

[Language-specific Display] TESTID-51: Correct UI display #8957

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

correct UI display

What to test

Permutations to consider (only if they apply)

Language:

  1. DQL

  2. Lucene

  3. PPL

  4. SQL

Scenario Steps Expected result Notes
Example (See below)   UI components that should be present:  
DQL
  • Select DQL.
  • Single line query editor.
  • Time picker.
  • Hit count & histogram.
  • Filter button: Located at the beginning of the query bar. Can add filter, pin filter, disable/enable filter.
  • Two buttons to the right of the query bar.
  • Language reference: A popover button that gives general information about the query language.
  • Saved query management: Located at the right of language reference button.
  • View single/surrounding doc: Can be accessed after expanding details for a doc.
 
Lucene
  • Select Lucene.
  • Single line query editor.
  • Time picker.
  • Hit count & histogram.
  • Filter button: Located at the beginning of the query bar. Can add filter, pin filter, disable/enable filter.
  • Two buttons to the right of the query bar.
  • Language reference: A popover button that gives general information about the query language.
  • Saved query management: Opens up a window box for saving query.
  • View single/surrounding doc: Can be accessed after expanding details for a doc.
 
PPL
  • Select PPL.
  • Multiline query editor (default query, can be toggled to collapse).
  • When expanded, footer should be present: line count, time field (if a time field is chosen at dataset explorer), query result. If valid, execution time is shown; if not valid, error and a popover appear.
  • Recent queries: Shows a list of recent queries that were ran.
  • Time picker.
  • Hit count & histogram.
  • Three buttons to the right of the query bar:
    • Language reference: A popover button that gives general information about the query language.
    • Toggle button.
    • Saved query management: Opens up a window box for saving query.
 
SQL
  • Select SQL.
  • Multiline query editor (default query, can be toggled to collapse).
  • When expanded, footer should be present: line count, time field (if a time field is chosen at dataset explorer), query result. If valid, execution time is shown; if not valid, error and a popover appear.
  • Recent queries: Shows a list of recent queries that were ran.
  • Three buttons to the right of the query bar:
    • Language reference: A popover button that gives general information about the query language.
    • Toggle button.
    • Saved query management: Opens up a window box for saving query.
 

Pre-requisites

What do we need to make sure the test can be written

Steps to setting up the scenario

  1. Have at least 1 existing workspace with index patterns

  2. Have one workspace without index patterns

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