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

[Field Display and Filtering] TESTID-69: Filtering #8945

Open
LDrago27 opened this issue Nov 27, 2024 · 1 comment · May be fixed by #9047
Open

[Field Display and Filtering] TESTID-69: Filtering #8945

LDrago27 opened this issue Nov 27, 2024 · 1 comment · May be fixed by #9047
Assignees
@ArgusLi
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
Loading

Objective

Verify filtering functionality in discover table works correctly across different data sources and query languages.

What to test

Test field filtering through:

  1. Filter for/out buttons in table field

  2. Document expansion filtering options


Data type:

  1. Index Patterns

  2. Indexes

  3. S3 Connections

  4. Cloudwatch

  5. Security Lake

Language:

  1. DQL

  2. Lucene

  3. PPL

  4. SQL


Test suite: filter actions in table field

Dataset Steps Expected Results
Index Pattern
  • Select an index pattern/index with DQL/Lucene.
  • Locate a field cell in the results.
  • Click "Filter for value" (+ button).
  • Verify the filter appears in the filter bar.
  • Check the updated results.
  • Repeat with "Filter out value" (- button).
  • Verify the filter in the filter bar.
  • Check updated results.
  • Switch to PPL and verify that no "Filter for value" (+ button) and no "Filter out value" (- button) are visible on the table field.
  • Filter buttons should be visible with DQL/Lucene.
  • Filter buttons should not be visible with SQL and PPL.
  • Filters should be added to the filter bar.
  • Results should update correctly.
  • Filter pills should be removable.
Index
  • Same steps as Index Pattern but select an index instead.
  • Same expected results as Index Pattern.

Test suite: filter actions in expanded table

Dataset Steps Expected Results Notes
Index Pattern
  • Select an index pattern/index with DQL/Lucene.
  • Expand a document row.
  • Locate a field.
  • Click "Filter for value" (+ button).
  • Verify the filter appears in the filter bar.
  • Check updated results.
  • Repeat with "Filter out value" (- button).
  • Verify the filter in the filter bar.
  • Check updated results.
  • Click "Toggle column in table."
  • Verify the selected field appears in the sidebar.
  • Click "Filter for field exist."
  • Verify the filter in the filter bar.
  • Switch to PPL and SQL, and verify that "Filter for value" (+ button), "Filter out value" (- button), and "Filter for field exist" are not clickable.
  • Click "Toggle column in table" and verify the selected field appears in the sidebar.
  • For DQL/Lucene:
  • Filter buttons should be visible after expanding a document row.
  • Results should update correctly after a filter action is clicked.
  • "Toggle column in table" should add the field to the sidebar.
  • "Filter for value" (+ button), "Filter out value" (- button), and "Filter for field exist" should update the filter bar accordingly.
  • Filter pills and sidebar fields should be removable.
  • Results should update correctly.
  • For SQL/PPL:
  • "Filter for value" (+ button), "Filter out value" (- button), and "Filter for field exist" should not be clickable.
  • "Toggle column in table" should add the field to the sidebar.
  • Sidebar fields should be removable.
  • Results should update correctly.
  • Filter buttons are visible after expanding a document with DQL/Lucene/SQL/PPL.
Index
  • Same steps as Index Pattern but select an index instead.
  • Same expected results as Index Pattern.

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
@ananzh ananzh moved this from Todo to In Progress in Discover 2.0 Testing Nov 27, 2024
@ArgusLi
Copy link
Contributor

ArgusLi commented Nov 27, 2024

Could I please take this task?

@ArgusLi ArgusLi linked a pull request Dec 12, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ArgusLi ArgusLi

Labels
discover_2.0-test Issues that are specific to the Discover 2.0 testing initiative
Projects
Discover 2.0 Testing
Status: In Progress
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[Discover 2.0 Testing] TestId-69: Filtering ArgusLi/OpenSearch-Dashboards
2 participants
@LDrago27 @ArgusLi