don't special case test functions now that pytest is more robust

Author: jakkdl

flake8_async/visitors/visitor91x.py

@@ -123,16 +123,11 @@ def leave_FunctionDef(
             and not self.has_await
             and not func_empty_body(original_node)
             and not func_has_decorator(original_node, "overload")
-            # skip functions named 'text_xxx' with params, since they may be relying
-            # on async fixtures. This is esp bad as sync funcs relying on async fixtures
-            # is not well handled: https://github.com/pytest-dev/pytest/issues/10839
-            # also skip funcs with @fixture and params
+            # skip functions with @fixture and params since they may be relying
+            # on async fixtures.
             and not (
                 original_node.params.params
-                and (
-                    original_node.name.value.startswith("test_")
-                    or func_has_decorator(original_node, "fixture")
-                )
+                and func_has_decorator(original_node, "fixture")
             )
             # ignore functions with no_checkpoint_warning_decorators
             and not fnmatch_qualified_name_cst(

tests/eval_files/async124.py

@@ -69,9 +69,9 @@ async def foo_empty_pass():
     pass
 
 
-# See e.g. https://github.com/agronholm/anyio/issues/803 for why one might want an async
-# test without awaits.
-async def test_async_fixture(  # ASYNC910: 0, "exit", Statement("function definition", lineno)
+# this was previously silenced, but pytest now gives good errors on sync test + async
+# fixture; so in the rare case that it has to be async the user will be able to debug it
+async def test_async_fixture(  # ASYNC124: 0  # ASYNC910: 0, "exit", Statement("function definition", lineno)
     my_async_fixture,
 ):
     assert my_async_fixture.setup_worked_correctly