-
-
Notifications
You must be signed in to change notification settings - Fork 176
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
test: unit tests for pg_search #573
Conversation
@Lilit0x is attempting to deploy a commit to the ParadeDB Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Ignored Deployment
|
@philippemnoel, is there anything else I need to do to run the tests for
|
You need to run |
Thanks! |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## dev #573 +/- ##
===========================================
- Coverage 80.61% 50.40% -30.22%
===========================================
Files 30 29 -1
Lines 3663 2706 -957
===========================================
- Hits 2953 1364 -1589
- Misses 710 1342 +632
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
Thank you for doing this, always amazing seeing your contributions :) |
Ticket(s) Closed
pg_bm25
andpg_search
#257What
Unit Tests for
pg_search
Why
Adding unit test suites to pg_search to increase the code coverage
How
Tests