test: reorganize docstore test suite to isolate dataframe tests

[anakin87]

Related Issues

• related to Investigate the possibility of removing dataframe field from Document #8627

Proposed Changes:

To initiate the removal of the dataframe field from Document, the first step would be to remove its support across all Document Stores.

Currently, most Document Stores test suites (in core-integrations) inherit from DocumentStoreBaseTests in Haystack.

In this PR, I'm isolating dataframe filter tests by removing them from FilterDocumentsTest (a part of DocumentStoreBaseTests) and grouping them into a new utility class, FilterDocumentsTestWithDataframe. This new class is not included in DocumentStoreBaseTests.

What will change after a Haystack release including this PR?

• All Document Stores which inherit from DocumentStoreBaseTests or FilterDocumentsTest won't automatically test Documents containing dataframe.
• To test dataframe functionality, one can inherit from FilterDocumentsTestWithDataframe.
• This approach simplifies the eventual removal of dataframe support from Document Stores, avoiding the need to manually skip dataframe-specific test cases for each integration (a lot of manual work)

How did you test it?

(CI)
Manually updated the InMemoryDocumentStore tests to inherit from both FilterDocumentsTestWithDataframe and DocumentStoreBaseTests. All tests, including dataframe-related ones, executed as expected.

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: and added ! in case the PR includes breaking changes.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 12672868712

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 increased (+0.01%) to 91.024%

---

Files with Coverage Reduction	New Missed Lines	%
utils/callable_serialization.py	2	95.0%

Totals
Change from base Build 12598899410:	0.01%
Covered Lines:	8569
Relevant Lines:	9414

---

💛 - Coveralls

[Amnah199]

Looks good! 👍