[Query Testing] TESTID-17: Test scenario

[LDrago27]

Objective

What are we testing

What to test

Permutations to consider (only if they apply)

Data type:

1. Index Patterns

2. Indexes

3. S3 Connections

4. Cloudwatch

5. Security Lake

Language:

1. DQL

2. Lucene

3. PPL

4. SQL

2.1. Test DQL queries with various complexity levels

2.1.1 - Need most popular DQL used to add to the testing plan

2.2. Test SQL queries with different operations (SELECT, JOIN, etc.)

2.2.1 - SQL Support across data sources

2.3. Test PPL queries with different commands and functions

2.3.1 - PPL Support within data sources (JOIN/Lookup/SUBQUERY from Spark PPL)

Scenario	Steps	Expected result	Notes
Example (See below)
PPL/SQL/DQS/S3	Make a query (add more details here)Expand a rowSee if flilters are disabled	Filters are disabled
DQL/Lucene & Index patterns	Make a query (add more details here)Expand a rowAdd a filter by clicking on the filter action	Filtering from the table works
DQL	Choose an index pattern with timestampSend a DQL query: response:400	Results should be within the time rangeresponse field should all equal to 400; any other rows are filtered outresponse: 400 should be highlighted
DQL	Choose an index pattern without timestampSend a DQL query: response:400	time range should not matter since we do not have time fieldresponse field should all equal to 400; any other rows are filtered outresponse: 400 should be highlighted
Advanced setting: ignoreFiltersIfValid is on	Turned on the advanced settingAdd a filter to a field, and pinned the filterSwitch to another index pattern that does not have that filter	Since the field are not present in the new dataset & ignoreFiltersIfValid is on, the pinned filter will be disabled
Advanced setting: ignoreFiltersIfValid is off	Turned on the advanced settingAdd a filter to a field, and pinned the filterSwitch to another index pattern that does not have that filter	Since the field are not present in the new dataset & ignoreFiltersIfValid is off, the pinned filter will still be applied
Advanced setting: sample size	Go to advanced setting and set sample size to 20Go back to discover	only 20 rows should be rendered
Histogram	Choose DQL, and choose auto on the histogram interval, read the histogram and count the # of intervalsChoose PPL, and also choose auto on the histogram, count the # of intervals	If DQL shows 12 bars each year in histogram interval; then we should see 12 intervals for PPL toobuckets might appear slightly different, since PPL only supports a specific time stamp format
Advanced setting:ConcurrentBatch is off
Advanced setting:ConcurrentBatch is on
SQL(default)	Select SQL	default query string should be displaying: SELECT * FROM opensearch_dashboards_sample_data_ecommerce LIMIT 10 time picker should not be showed
PPL(default)	Select PPL	default query string should be displaying: source = opensearch_dashboards_sample_data_ecommercetime picker & histogram should be showed

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

[angle943]

i will take this

[kavilla]

might need some error testing

[ananzh]

@angle943 Sample size has an update:
#9356

[ananzh]

Make a query (add more details here)Expand a rowSee if flilters are disabled and Make a query (add more details here)Expand a rowAdd a filter by clicking on the filter action are tested in other project

[ananzh]

Default query is also tested in multiple places, ex autocomplete_switch, dataset_selector and etc. There is a utility function

export const getDefaultQuery = (datasetName, language) => {
  switch (language) {
    case QueryLanguages.DQL.name:
      return '';
    case QueryLanguages.Lucene.name:
      return '';
    case QueryLanguages.PPL.name:
      return `source = ${datasetName}`;
    case QueryLanguages.SQL.name:
      return `SELECT * FROM ${datasetName} LIMIT 10`;
  }
};

and these tests used this function to verify the default query.

[ananzh]

Ignore Histogram for now since it requires interaction with canvas in cypress. Will create another issue for it.
Ignore Advanced setting:ConcurrentBatch as it requires to verify to use msearch in network tab. Better to manually verify it.