Update python test_add_frame catch to better reflect issues across different enviroments

Author: eicchen

pandas/tests/arrays/string_/test_string.py

@@ -278,9 +278,12 @@ def test_add_strings(dtype):
 
 @pytest.mark.xfail(reason="GH-28527")
 def test_add_frame(request, dtype):
-    # "str[python]" actually safely adds but with the wrong dtype
-    # result = <StringDtype(na_value=nan)>
-    # expected = <StringDtype(storage='python', na_value=nan)>
+    if dtype.storage == "python":
+        # Inconsistent behavior between different versions of the python engine.
+        # Some return correctly, some return but with the wrong dtype
+        # Others just fail, we are blanket failing all
+        mark = pytest.mark.xfail(reason="[XPASS(strict)] GH-28527")
+        request.node.applymarker(mark)
     arr = pd.array(["a", "b", np.nan, np.nan], dtype=dtype)
     df = pd.DataFrame([["x", np.nan, "y", np.nan]])
     assert arr.__add__(df) is NotImplemented