[Discover Autocomplete] TESTID-80: Autocomplete Languages - DQL, SQL, PPL - Custom Written Logic

[LDrago27]

Objective

Cover remaining untested functions within PPL and SQL, ensuring that the suggestions are accurate. Tests should be written for "preferred rules", or in general areas where custom logic was written instead of relying on the grammar for these languages.

So far, this includes suggesting table names, suggesting aggregate functions for PPL and SQL.

What to test

Permutations to consider (only if they apply)

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)
PPL/SQL table name	For PPL, test with source =. For SQL, test with SELECT * FROM.	table name appears
PPL/SQL aggregate functions	Test PPL by writing in a command with stats, and the suggestions should appear as expected. All the aggregate functions include a 'snippet' which should allow for tabbing into the inside of the parentheses. Test SQL by putting in a WHERE clause, and verify that aggregate functions appear.	aggregate functions appear

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. 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