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.

Sign up for GitHub

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

Jump to bottom

[Results Display and Interaction in Table, Side panel] TESTID-140: Side bar #8946

Closed
LDrago27 opened this issue Nov 27, 2024 · 3 comments · May be fixed by #9386
Closed

[Results Display and Interaction in Table, Side panel] TESTID-140: Side bar #8946

LDrago27 opened this issue Nov 27, 2024 · 3 comments · May be fixed by #9386
Assignees
@ananzh
Labels
discover_2.0-test Issues that are specific to the Discover 2.0 testing initiative

Comments

@LDrago27
Copy link
Collaborator

LDrago27 commented Nov 27, 2024 •
edited by ananzh
Loading

Objective

  1. Verify that selected fields from the side panel persist in the discover table when switching between query languages (DQL, PPL, SQL)

  2. Verify that field filtering in side panel works correctly and filters down the available fields based on user input

  3. Verify that side panel collapse/expand functionality works

  4. Verify that nested fields are displayed and can be interacted with correctly in the side bar

What to test

Side bar related functionalities

Data type:

  1. Index Patterns

  2. Indexes

Language:

  1. DQL

  2. PPL

  3. SQL


Test suite 1: Add fields

Dataset Steps Expected Results Notes
Index Pattern Choose an index pattern with DQL language and verify _source is available as default selected fieldAdd multiple fields from side panel Verify fields appear in table columnsSwitch to PPL languageVerify previously selected fields remain in table columnsRemove some selected fieldsRemove all selected fieldsSend a PPL queryVerify fields still persist after query executionDo the same for SQL _source is the default field for DQLSelected fields appear as columns in DQLFields persist when switching to PPLCan remove or add field from side bar in PPLRemove all fields should show _source in PPLFields remain after executing PPL queryOriginal field order is maintained  
Index Same steps as Index Pattern, but select an index instead.    
S3 connection Same steps as Index Pattern, but select a S3 instead.    
Cloudwatch Same steps as Index Pattern, but use Cloudwatch instead.    
Security Lake Same steps as Index Pattern, but use Security lake instead.    
       

Test suite 2: filter fields

Dataset Steps Expected Results  
Index Pattern Choose an index patternOpen side panelType in field filter box (e.g., "catogery")Clear filterType partial field nameSwitch language to PPL/SQL and repeat steps 3-5 Only fields matching filter text are shownClearing filter shows all fields againPartial matches are shownFiltering works across language switches  
Index Same steps as Index Pattern, but select an index instead.    
S3 connection Same steps as Index Pattern, but select a S3 instead.    
Cloudwatch Same steps as Index Pattern, but use Cloudwatch instead.    
Security Lake Same steps as Index Pattern, but use Security lake instead.    
       

Test suite 3: side panel collapse/expand

Dataset Steps Expected Results  
Index Pattern Verify side panel is initially expandedClick collapse buttonClick expand buttonSwitch languageVerify panel state persists Panel starts expandedCollapses when clickedExpands when clicked againState persists across language switches  
Index Same steps as Index Pattern, but select an index instead.    
S3 connection Same steps as Index Pattern, but select a S3 instead.    
Cloudwatch Same steps as Index Pattern, but use Cloudwatch instead.    
Security Lake Same steps as Index Pattern, but use Security lake instead.    
       

Test suite 4: nested field

Dataset Steps Expected Results  
Index Pattern Choose an index pattern with nested fieldsVerify nested fields are indented and shown in the side barAdd nested field to tableRemove nested fieldSwitch languageRepeat steps 3-4 Nested fields show correct indentationCan add/remove nested fieldsBehavior consistent across languages  
Index Same steps as Index Pattern, but select an index instead.    
S3 connection Same steps as Index Pattern, but select a S3 instead.    
Cloudwatch Same steps as Index Pattern, but use Cloudwatch instead.    
Security Lake Same steps as Index Pattern, but use Security lake instead.    
       

Pre-requisites
What do we need to make sure the test can be written
Steps to setting up the scenario
Have at least 1 existing workspace with index patterns and indices
Known Issues
List of known issues to reference that could impact the results of this test case
@LDrago27 LDrago27 added enhancement New feature or request discover_2.0-test Issues that are specific to the Discover 2.0 testing initiative and removed enhancement New feature or request labels Nov 27, 2024
@ananzh ananzh moved this from Todo to In Progress in Discover 2.0 Testing Dec 17, 2024
@silvaf-dev silvaf-dev mentioned this issue Dec 26, 2024
Closed
7 tasks
@ananzh ananzh moved this from In Progress to Ready to Review in Discover 2.0 Testing Jan 6, 2025
@ananzh ananzh mentioned this issue Jan 8, 2025
Merged
7 tasks
@ananzh
Copy link
Member

ananzh commented Jan 15, 2025

Videos

Use Index Pattern DQL as example. Index and different languages show same result.

Add fields

add.fields.mp4

Filter fields

filter.fields.mp4

Collapse and Expand

collapse.mp4

@ananzh
Copy link
Member

ananzh commented Jan 23, 2025

Test suite 5: Top values

Dataset Steps Expected Results
Index Pattern Choose a regular aggregatable fieldClick showDetails buttonChoose a nested fieldClick showDetails buttonSwitch to SQL/PPLChoose any field and click showDetails button Aggregatable field should show top values and a visualize buttonClick the visualize button can route to a histogram visualizationNested field should show top values and a visualize buttonClick the visualize button can not route to any visualization and see an error warning. ex Saved field "personal.address.country" is invalid for use with the "Terms" aggregation. Please select a new field.For SQL/PPL, should show top values but no visualize button
Index Same steps as Index Pattern, but select an index instead.  
S3 connection Same steps as Index Pattern, but select a S3 instead.  
Cloudwatch Same steps as Index Pattern, but use Cloudwatch instead.  
Security Lake Same steps as Index Pattern, but use Security lake instead.  
     
top-field-sidebar.mp4

@ananzh
Copy link
Member

ananzh commented Jan 24, 2025 •
edited
Loading

Test suite 6: filtering fields by type

Dataset Steps Expected Results
Index Pattern Click toggleFieldFilterButton Select "yes" under aggregatable filterSelect "yes" under searchable filterSelect specific type from dropdown (e.g. "string")Toggle "Hide missing fields" switchMake a combine Select "yes" for AggregatableSelect "string" for TypeEnable Hide Missing Fields Only aggregatable fields appear in available fields list when select "yes" under aggregatable filterShould see a 1 by the side of toggleFieldFilterButton.Only searchable fields appear in available fields list when select "yes" under searchable filterShould see a 1 by the side of toggleFieldFilterButton.Only fields matching selected type appear in available fields list when select a type (string) Should see a 1 by the side of toggleFieldFilterButton.Fields with 0% occurrence should be hidden when toggle "Hide missing fields" switchOnly string fields that are aggregatable and have values should showShould see a 2 by the side of toggleFieldFilterButton.
Index Same steps as Index Pattern, but select an index instead.  
S3 connection Same steps as Index Pattern, but select a S3 instead.  
Cloudwatch Same steps as Index Pattern, but use Cloudwatch instead.  
Security Lake Same steps as Index Pattern, but use Security lake instead.  
  • Video is only about index pattern DQL. It is the same for index and other languages.
toggleFieldfilter.mp4
  • Note: hide missing field would require inject an index with a field of some empty value given the time range. will update the video later.

ananzh added a commit to ananzh/OpenSearch-Dashboards that referenced this issue Jan 27, 2025
@ananzh
Refactor TESTID 140 and resolve TESTID 46,47,49
c42e778 
Issue Resolved
Partially opensearch-project#8946
opensearch-project#8954
opensearch-project#8952
opensearch-project#8953

Signed-off-by: Anan <[email protected]>
ananzh added a commit to ananzh/OpenSearch-Dashboards that referenced this issue Jan 27, 2025
@ananzh
Refactor TESTID 140 and resolve TESTID 46,47,49
98f25c0 
Issue Resolved
Partially opensearch-project#8946
opensearch-project#8954
opensearch-project#8952
opensearch-project#8953

Signed-off-by: Anan <[email protected]>
ananzh added a commit to ananzh/OpenSearch-Dashboards that referenced this issue Jan 28, 2025
@ananzh
Refactor TESTID 140 and resolve TESTID 46,47,49
38fb073 
Issue Resolved
Partially opensearch-project#8946
opensearch-project#8954
opensearch-project#8952
opensearch-project#8953

Signed-off-by: Anan <[email protected]>
ananzh added a commit to ananzh/OpenSearch-Dashboards that referenced this issue Jan 28, 2025
@ananzh
Refactor TESTID 140 and resolve TESTID 46,47,49
44819bf 
Issue Resolved
Partially opensearch-project#8946
opensearch-project#8954
opensearch-project#8952
opensearch-project#8953

Signed-off-by: Anan <[email protected]>
ananzh added a commit to ananzh/OpenSearch-Dashboards that referenced this issue Jan 29, 2025
@ananzh
Refactor TESTID 140 and resolve TESTID 46,47,49
c5e094a 
Issue Resolved
Partially opensearch-project#8946
opensearch-project#8954
opensearch-project#8952
opensearch-project#8953

Signed-off-by: Anan <[email protected]>
ananzh added a commit to ananzh/OpenSearch-Dashboards that referenced this issue Jan 29, 2025
@ananzh
Refactor TESTID 140 and resolve TESTID 46,47,49
c4193be 
Issue Resolved
Partially opensearch-project#8946
opensearch-project#8954
opensearch-project#8952
opensearch-project#8953

Signed-off-by: Anan <[email protected]>
ananzh added a commit to ananzh/OpenSearch-Dashboards that referenced this issue Jan 29, 2025
@ananzh
Refactor TESTID 140 and resolve TESTID 46,47,49
b1378d4 
Issue Resolved
Partially opensearch-project#8946
opensearch-project#8954
opensearch-project#8952
opensearch-project#8953

Signed-off-by: Anan <[email protected]>
ananzh added a commit that referenced this issue Jan 30, 2025
@ananzh @opensearch-changeset-bot
[Cypress Test] Add and Refactor TESTID-140 sidebar spec and TESTID-46…
a50e0c7 
…,47,49 sharing spec (#9154)

* Refactor TESTID 140 and resolve TESTID 46,47,49

Issue Resolved
Partially #8946
#8954
#8952
#8953

Signed-off-by: Anan <[email protected]>

* Changeset file for PR #9154 created/updated

---------

Signed-off-by: Anan <[email protected]>
Co-authored-by: opensearch-changeset-bot[bot] <154024398+opensearch-changeset-bot[bot]@users.noreply.github.com>
@ananzh ananzh self-assigned this Jan 30, 2025
@ananzh ananzh moved this from Ready to Review to Done in Discover 2.0 Testing Jan 30, 2025
@ananzh ananzh closed this as completed by moving to Done in Discover 2.0 Testing Jan 30, 2025
@ArgusLi ArgusLi mentioned this issue Feb 13, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ananzh ananzh

Labels
discover_2.0-test Issues that are specific to the Discover 2.0 testing initiative
Projects
Discover 2.0 Testing
Status: Done
Milestone
No milestone
3 participants
@LDrago27 @ananzh and others