test: add delete_all_documents, delete_by_filter and update_by_filter generic tests to haystack.testing.document_store

[davidsbatista]

Related Issues

• fixes #2811

Proposed Changes:

• New tests for:
  • delete_all_documents(): normal behaviour, empty store, and optional recreate_index (True/False).
  • delete_by_filter(): matching docs, no matches, and AND/OR filters.
  • UpdateByFilterTest for update_by_filter(): basic update, no matches, multiple fields, and AND/OR filters.
• Tests that don’t need self are now @staticmethod;
• DocumentStoreBaseTests includes UpdateByFilterTest

How did you test it?

• Locally run the full (existing plus these new ones) for all of our document stores in haystack-core-integrations and made sure all passed
• New tests use pytest.skip() when a store doesn’t implement delete_all_documents, delete_by_filter, or update_by_filter, or when recreate_index isn’t supported.

NOTE:

This needs to be merged before deepset-ai/haystack-core-integrations#2812 is merged into haystack-core-integrations

Checklist

• I have read the contributors guidelines and the code of conduct.
• I have updated the related issue with new insights and changes.
• I have added unit tests and updated the docstrings.
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I have documented my code.
• I have added a release note file, following the contributors guidelines.
• I have run pre-commit hooks and fixed any issue.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
haystack-docs	Ignored	Preview	Feb 5, 2026 3:22pm

[coveralls]

Pull Request Test Coverage Report for Build 21717270304

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.01%) to 92.562%

---

Files with Coverage Reduction	New Missed Lines	%
core/pipeline/async_pipeline.py	2	66.67%

Totals
Change from base Build 21715008796:	-0.01%
Covered Lines:	14884
Relevant Lines:	16080

---

💛 - Coveralls

[anakin87]

It's looking good.

I left a few minor comments.

[anakin87]

Thanks for all the adjustments!