feat(mongodb-atlas): use async DocumentStore mixin tests

[SyedShahmeerAli12]

Related Issues

• closes Use async DocumentStore mixin tests in MongoDB Atlas #3048

Proposed Changes

Updates integrations/mongodb_atlas/tests/test_document_store_async.py to inherit the async mixin test classes from haystack.testing.document_store_async, removing duplicate test code that is now covered by the shared mixins.

Mixin classes added:

• CountDocumentsAsyncTest
• WriteDocumentsAsyncTest
• DeleteDocumentsAsyncTest
• DeleteAllAsyncTest
• DeleteByFilterAsyncTest
• FilterDocumentsAsyncTest
• UpdateByFilterAsyncTest
• CountDocumentsByFilterAsyncTest
• CountUniqueMetadataByFilterAsyncTest
• GetMetadataFieldsInfoAsyncTest
• GetMetadataFieldMinMaxAsyncTest
• GetMetadataFieldUniqueValuesAsyncTest

Tests removed (now covered by mixins):

• test_write_documents_async
• test_count_documents_async
• test_filter_documents_async
• test_delete_documents_async
• test_delete_by_filter_async
• test_update_by_filter_async
• test_delete_all_documents_async
• test_delete_all_documents_async_empty_collection
• test_count_documents_by_filter_async
• test_count_unique_metadata_by_filter_async
• test_get_metadata_fields_info_async
• test_get_metadata_field_min_max_async
• test_get_metadata_field_unique_values_async

Tests kept (MongoDB Atlas-specific):

• test_write_blob_async — binary/ByteStream document handling
• test_delete_all_documents_async_with_recreate_collection — MongoDB-specific recreate_collection=True parameter

Overrides added:

• test_count_not_empty_async base class uses @staticmethod which breaks fixture injection
• test_write_documents_async MongoDB raises DuplicateDocumentError on duplicate with FAIL policy

How did you test it?

Unit tests (TestEnsureConnectionSetupAsync, TestMongoDBDocumentStoreAsyncUnit) run without requiring a live MongoDB connection. Integration tests require MONGO_CONNECTION_STRING.

Notes for the reviewer

Followed the same pattern as the Elasticsearch async test refactor. The @pytest_asyncio.fixture decorator is used for the document_store fixture, consistent with other 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 added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: feat:

[github-actions]

Heads-up for maintainers

This PR is from a fork and touches integrations whose integration tests require API keys.
Those tests are skipped in CI because fork PRs don't have access to repo secrets for security reasons.

Affected integrations:

• mongodb_atlas

Please run the integration tests locally (hatch run test:integration inside each folder) before approving.

[github-actions]

Coverage report (mongodb_atlas)

This PR does not seem to contain any modification to coverable code.

[SyedShahmeerAli12]

Hey @davidsbatista this PR is ready for review. Unit tests are passing in CI; integration tests require MONGO_CONNECTION_STRING which isn't available in fork PRs. Could you run them locally when you get a chance?

[davidsbatista]

Looks good! Thanks!