test(integration): document why xfail uses strict=False for inbound traverse

polaz · polaz · commit df5f83d5d429 · 2026-04-13T00:35:17.000+03:00
XPASS means the server gained inbound support — that is good news, not
a CI failure. strict=True would break CI at exactly the moment the server
improves. The XPASS entry in pytest output is the signal to remove the marker.
diff --git a/tests/integration/test_sdk.py b/tests/integration/test_sdk.py
@@ -285,6 +285,9 @@ def test_traverse_returns_neighbours(client):
 
 @pytest.mark.xfail(
     strict=False,
+    # strict=False: XPASS is good news (server gained inbound support), not an error.
+    # strict=True would break CI exactly when the server improves, which is undesirable.
+    # The XPASS report in pytest output is the signal to remove this marker.
     reason="CoordiNode Traverse RPC does not yet support inbound direction — server returns empty result set",
 )
 def test_traverse_inbound_direction(client):

Original file line number	Diff line number	Diff line change
`@@ -285,6 +285,9 @@ def test_traverse_returns_neighbours(client):`
`285`	`285`
`286`	`286`	`@pytest.mark.xfail(`
`287`	`287`	`strict=False,`
	`288`	`+ # strict=False: XPASS is good news (server gained inbound support), not an error.`
	`289`	`+ # strict=True would break CI exactly when the server improves, which is undesirable.`
	`290`	`+ # The XPASS report in pytest output is the signal to remove this marker.`
`288`	`291`	`reason="CoordiNode Traverse RPC does not yet support inbound direction — server returns empty result set",`
`289`	`292`	`)`
`290`	`293`	`def test_traverse_inbound_direction(client):`