test: replacing each DocumentStore specific tests and used the generalised ones from haystack.testing.document_store

[davidsbatista]

Related Issues

• fixes Avoid duplicating test code in DocumentStore integrations #2811

Proposed Changes:

• Use Haystack’s shared document store test mixins (DeleteDocumentsTest, UpdateByFilterTest, etc.) instead of custom duplicated tests across integrations.

Document store	# duplicated tests removed
Astra	3
Azure AI Search	6
Chroma	4
Elasticsearch	3
MongoDB Atlas	4
OpenSearch	3
pgvector	8
Pinecone	7
Qdrant	8
Weaviate	3

Total tests removed: 49, and 7 overrides tests added in Azure AI Search

• Bug fixes
  • Chroma: Guard delete_all_documents() so it doesn’t call delete(ids=[]) on an empty collection (avoids Chroma error when there are no docs).
  • Azure AI Search: Handle booleans in filter helpers _eq / _ne in filters.py (e.g. true/false in OData).
  • Azure AI Search: Conftest update_by_filter_and_wait updated to accept meta (and fields/kwargs) and pass the correct updates into update_by_filter.

How did you test it?

• Run each integration’s document store tests (e.g. pytest integrations/<name>/tests/test_document_store.py).
• Confirm no custom delete/update-by-filter tests remain except where overrides are required (e.g. parametrized metadata or backend-specific options).

Notes for the reviewer

• This PR must be merged only after test: add delete_all_documents, delete_by_filter and update_by_filter generic tests to haystack.testing.document_store haystack#10477 is merged in haystack
• Currently every pyproject.toml is using this branch test: add delete_all_documents, delete_by_filter and update_by_filter generic tests to haystack.testing.document_store haystack#10477 - before this PR is approved those need to be updated to point to the latest haystack release

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I 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:.

[anakin87]

Left some minor comments.

Also, I think we can maybe safely avoid increasing haystack-ai pin:

• we would not force users to update to a newer Haystack version when their document store can already work with previous versions (we just changed tests)
• in the CI, the latest stable version will run in any case
• if we avoid changing pins, we can keep everything in this PR and don't worry about releasing new versions.

WDYT?

[davidsbatista]

I'm probably missing something. If we don't increase the dependency on the latest haystack to at least 2.24, the tests will fail, since the new tests code is in this new release.

[anakin87]

I'm probably missing something. If we don't increase the dependency on the latest haystack to at least 2.24, the tests will fail, since the new tests code is in this new release.

By default, when pinning haystack-ai>=X.Y.Z, the latest stable version is installed (2.24.1) (unless other dependencies have conflicting dependencies), which is OK for the CI. You can try...

[anakin87]

I'm probably missing something. If we don't increase the dependency on the latest haystack to at least 2.24, the tests will fail, since the new tests code is in this new release.

By default, when pinning haystack-ai>=X.Y.Z, the latest stable version is installed (2.24.1) (unless other dependencies have conflicting dependencies), which is OK for the CI. You can try...

I was wrong because we also run unit tests with the lowest possible dependencies and this would make imports fail.

[anakin87]

Looks good.

Thank you for the standardization work!