Fail tests with unexpected warnings

[ricardoV94]

Description

Some great maintenance work to cleanup warnings was done in #6067 and #6074 (probably more)

More recently, I started adding pytestmark = pytest.mark.filterwarnings("error"), as in #6407

Ideally, we would move to failing with warnings in the entire test suite, so that we don't regress and catch deprecation issues earlier on. The approach taken in #6407 might be a good start if there's too much going on.

https://docs.pytest.org/en/7.1.x/how-to/capture-warnings.html

[dikwickley]

hello @ricardoV94 I would like to work on this issue. Can you assign it to me?

[ricardoV94]

We have a policy of not assigning issues formally, just open a PR and it will count as being yours :)

[Raj-Parekh24]

Hey @ricardoV94,

I would like to ask that is this issue still open, or if PR has been raised for it.

If another member is not working I would like to take up this issue.

[Raj-Parekh24]

Hi @ricardoV94,

Based on my understanding, the issue is regarding the capture of the deprecation warning earlier on within the test suites. We have to avoid the capture of deprecation warning in the early stages.

To do this we can add filterwarnings under tool.pytest.ini_options in pyproject.toml.

Please, review the described solution so I can implement it and raise PR for it.

[Raj-Parekh24]

Hey @ricardoV94 ,

Any suggestion regarding this approach?