test: Update test/others/test_utils.py

[sjrl]

Related Issues

• fixes N/A

Proposed Changes:

• Remove deepset Cloud specific tests
• Add mark unit test to appropriate tests
• Convert global variables to pytest fixtures

Notes for the reviewer

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:.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[sjrl]

Hey @bogdankostic, @silvanocerza and I were talking about these changes offline so he offered to review this PR

[coveralls]

Pull Request Test Coverage Report for Build 5462544132

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 83 unchanged lines in 2 files lost coverage.
• Overall coverage increased (+0.7%) to 44.607%

---

Files with Coverage Reduction	New Missed Lines	%
document_stores/search_engine.py	4	62.39%
document_stores/elasticsearch/es8.py	79	0%

Totals
Change from base Build 5453787062:	0.7%
Covered Lines:	10265
Relevant Lines:	23012

---

💛 - Coveralls

[sjrl]

Hey @silvanocerza before we merge, I'd like to double check with @tstadel that is okay for us to remove the dC tests or if it would be helpful to have them present until they can be moved (e.g. maybe into the new SDK).

[silvanocerza]

Ok for me even though I think it's not necessary. They weren't running and they will still be in the history if necessary. In any case I believe they must not be part of Haystack.

[tstadel]

I would highly recommend to keep tests (running) until the corresponding code has been removed. There is still functionality in the old SDK that is not yet part of the new SDK. Unless there is a good reason, we should stick to our usual deprecation process (for code and its corresponding tests).