But now that FastAPI 0.99.0 and above uses OpenAPI 3.1.0, that uses JSON Schema 2020-12, and Swagger UI 5.0.0 and above, everything is more consistent and the examples are included in JSON Schema.

### Swagger UI and OpenAPI-specific `examples` { #swagger-ui-and-openapi-specific-examples }

        @Test
        @DisplayName("getOpnum should be consistent across multiple calls")
        void testGetOpnumConsistency() {
            // When
            int opnum1 = bind.getOpnum();
            int opnum2 = bind.getOpnum();
            int opnum3 = bind.getOpnum();

            // Then
            assertEquals(opnum1, opnum2, "Opnum should be consistent");

        assertTrue(toStringResult.contains(message));
    }

    public void test_getMessage_consistency() {
        // Test that getMessage returns the same value consistently
        String message = "Consistent message";
        UnsupportedSearchException exception = new UnsupportedSearchException(message);

        String firstCall = exception.getMessage();
        String secondCall = exception.getMessage();

        loadBalancer.setStrategy(LoadBalancingStrategy.AFFINITY_BASED);

        Smb2ReadRequest readRequest = mock(Smb2ReadRequest.class);
        when(readRequest.getTreeId()).thenReturn(123); // Set consistent tree ID for affinity

        when(mockChannelManager.getHealthyChannels()).thenReturn(Arrays.asList(channel1, channel2));

        // Multiple calls with same file ID should return same channel

        // Then
        assertEquals(0, bytesRead);
    }

    @ParameterizedTest
    @ValueSource(ints = { 0, 10, 50, 100, 200 })
    @DisplayName("Should write consistent structure at different offsets")
    void testWriteBytesAtDifferentOffsets(int offset) {
        // Given
        Configuration mockConfig = mock(Configuration.class);

      assertTrue(item + " must be equivalent to itself", equivalence.equivalent(item, item));
      assertEquals(
          "the hash of " + item + " must be consistent",
          equivalence.hash(item),
          equivalence.hash(item));
    }
  }

 * equality for both keys and values. This may not be the desired behavior for map implementations
 * that use non-standard notions of key equality, such as the entry of a {@code SortedMap} whose
 * comparator is not consistent with {@code equals}.
 *
 * <p>The {@code standard} methods are not guaranteed to be thread-safe, even when all of the
 * methods that they depend on are thread-safe.
 *
 * @author Mike Bostock
 * @author Louis Wasserman

   * without grabbing the lock.
   *
   * <p>To update this field correctly the lock must be held to guarantee that the state is
   * consistent.
   */
  private volatile StateSnapshot snapshot = new StateSnapshot(NEW);

  /** Constructor for use by subclasses. */
  protected AbstractService() {}

  /**

        // Test hashCode consistency
        int metadataHashCode = SsoResponseType.METADATA.hashCode();
        int logoutHashCode = SsoResponseType.LOGOUT.hashCode();

        // Hash code should be consistent for the same object
        assertEquals(metadataHashCode, SsoResponseType.METADATA.hashCode());
        assertEquals(logoutHashCode, SsoResponseType.LOGOUT.hashCode());

            // from being reused. Otherwise we're still obligated to transmit the request body to
            // leave the connection in a consistent state.
            exchange.noNewExchangesOnConnection()
          }
        }
      } else if (!isUpgradeRequest) {
        exchange.noRequestBody()
      }