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

Adds Integration Tests for Search Pipeline #16561

Merged
merged 2 commits into from
Nov 11, 2024

Conversation

owaiskazi19
Copy link
Member

Description

Adds Integration Tests for Search Pipeline

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

  • Functionality includes testing.
  • API changes companion pull request created, if applicable.
  • Public documentation issue/PR created, if applicable.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@owaiskazi19
Copy link
Member Author

@msfroh @dbwiddis @saratvemulapalli can you take a look?

@owaiskazi19 owaiskazi19 force-pushed the search-pipeline-IT branch 2 times, most recently from 1b84e5b to 53ae28a Compare November 5, 2024 01:25
Copy link
Contributor

github-actions bot commented Nov 5, 2024

❌ Gradle check result for 53ae28a: FAILURE

Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green. Is the failure a flaky test unrelated to your change?

Copy link
Contributor

github-actions bot commented Nov 5, 2024

✅ Gradle check result for 98dfb5b: SUCCESS

Copy link

codecov bot commented Nov 5, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.12%. Comparing base (0363aa7) to head (160611f).
Report is 17 commits behind head on main.

Additional details and impacted files
@@             Coverage Diff              @@
##               main   #16561      +/-   ##
============================================
+ Coverage     72.00%   72.12%   +0.11%     
- Complexity    65038    65104      +66     
============================================
  Files          5313     5313              
  Lines        303454   303469      +15     
  Branches      43910    43910              
============================================
+ Hits         218510   218876     +366     
+ Misses        67040    66672     -368     
- Partials      17904    17921      +17     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link
Member

@dbwiddis dbwiddis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yay more tests!

Copy link
Member

@andrross andrross left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for adding some tests! Apologies in advance for the nitpicking :)

Signed-off-by: Owais <[email protected]>
@owaiskazi19 owaiskazi19 requested a review from andrross November 5, 2024 21:00
Copy link
Collaborator

@msfroh msfroh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These tests are flexing core functionality (default pipelines, update configuration, etc). Do they belong in the integ tests for the search-pipeline-common module? Of course, testing that stuff from core is tricky, because there are no processors registered in core.

As @dbwiddis said, "Yay more tests!" -- while I'd love to see core functionality tested from core, I'm also happy to see integ tests for core functionality in this module (since that's a lot better than not having integ tests anywhere).

Copy link
Contributor

github-actions bot commented Nov 5, 2024

✅ Gradle check result for 160611f: SUCCESS

@owaiskazi19
Copy link
Member Author

These tests are flexing core functionality (default pipelines, update configuration, etc). Do they belong in the integ tests for the search-pipeline-common module? Of course, testing that stuff from core is tricky, because there are no processors registered in core.

Do you think this is not the right place to add these tests? The reason you mentioned above was the sole reason I added it in search-pipeline-common.

@owaiskazi19 owaiskazi19 requested a review from msfroh November 5, 2024 23:29
@msfroh msfroh merged commit 46ded36 into opensearch-project:main Nov 11, 2024
41 checks passed
@owaiskazi19 owaiskazi19 added the backport 2.x Backport to 2.x branch label Nov 11, 2024
opensearch-trigger-bot bot pushed a commit that referenced this pull request Nov 11, 2024
* Adds Integration Tests for Search Pipeline

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

* Addressed comments

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

---------

Signed-off-by: Owais <[email protected]>
(cherry picked from commit 46ded36)
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
owaiskazi19 pushed a commit that referenced this pull request Nov 12, 2024
* Adds Integration Tests for Search Pipeline



* Addressed comments



---------


(cherry picked from commit 46ded36)

Signed-off-by: Owais <[email protected]>
Signed-off-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport 2.x Backport to 2.x branch skip-changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants