From a27d894da5d1b45137a20d2eeecdcb0b36722532 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Armando=20Rodr=C3=ADguez?= <127134616+armando-rodriguez-cko@users.noreply.github.com> Date: Wed, 7 Oct 2026 13:05:30 +0200 Subject: [PATCH] test: reword test comments that pointed at internal files Comments now describe what the test covers instead of referring to internal tracking and tooling files. --- .../com/checkout/balances/BalancesSerializationTest.java | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/src/test/java/com/checkout/balances/BalancesSerializationTest.java b/src/test/java/com/checkout/balances/BalancesSerializationTest.java index c9a63bd2d..780be7427 100644 --- a/src/test/java/com/checkout/balances/BalancesSerializationTest.java +++ b/src/test/java/com/checkout/balances/BalancesSerializationTest.java @@ -19,7 +19,7 @@ *

Covers the top-up instructions response * (GET /entities/{entityId}/currency-accounts/{currencyAccountId}/top-up-instructions) and the * entity balances response (GET /balances/{id}). Every value is taken from the field-level - * {@code example} values in shared/swagger-latest.json; neither response schema carries a + * {@code example} values in the API reference; neither response schema carries a * top-level example. * *

The spec is explicit that neither funding rail is guaranteed: TopUpBankDetails declares no @@ -273,9 +273,8 @@ void shouldOmitUnsetOptionalFundingFields() { // ------------------------------------------------------------------------ // BalancesResponse / CurrencyAccountBalance / Balances / CollateralBreakdown // - // Added when Balance.operational was found missing from the SDK during the INT-1692 review; - // review-integrity.mdc section 9 requires a serialization test for a new field on an - // existing class. + // Covers every property, including Balance.operational, so a field missing from the model + // fails here instead of being silently dropped. // ------------------------------------------------------------------------ @Test