if result.Pets[i-1].Name > result.Pets[i].Name {
				t.Fatalf("Preload user %v pets not ordered correctly, last %v, cur %v", result.Name, result.Pets[i-1], result.Pets[i])
			}
		}
		for i := 1; i < len(result.Pets); i++ {
			if result.Pets[i-1].Name > result.Pets[i].Name {
				t.Fatalf("Preload user %v friends not ordered correctly, last %v, cur %v", result.Name, result.Pets[i-1], result.Pets[i])
			}
		}
	}
}

/// note | Nota Técnica

Pero si declaras un response model o un tipo de retorno, eso se usará directamente para serializar los datos a JSON, y se devolverá directamente un response con el media type correcto para JSON, sin usar la clase `JSONResponse`.

Esta es la forma ideal de obtener el mejor rendimiento.

///

### `RedirectResponse` { #redirectresponse }

        assertEquals(1, includePatterns.size());
        assertEquals(1, excludePatterns.size());

        // Verify patterns work correctly
        assertTrue(includePatterns.get(0).matcher("http://example.com/page").matches());
        assertTrue(excludePatterns.get(0).matcher("http://example.com/admin/users").matches());

        assertNotNull(dependencies, "dependencies element should be created");

        String xmlOutput = DomUtils.toXml(doc);

        // Verify elements are created and positioned correctly
        int versionIndex = xmlOutput.indexOf("<version>1.0.0</version>");
        int propertiesIndex = xmlOutput.indexOf("<properties>");
        int dependenciesIndex = xmlOutput.indexOf("<dependencies>");

        assertEquals(20, bytesRead);
        assertNotNull(response.getInfo());
    }

    @Test
    void testInformationLevelConstants() {
        // Verify information level constants are correctly used
        assertEquals((byte) -1, FileSystemInformation.SMB_INFO_ALLOCATION);
        assertEquals((byte) 3, FileSystemInformation.FS_SIZE_INFO);
        assertEquals((byte) 7, FileSystemInformation.FS_FULL_SIZE_INFO);

If you generate a client for a FastAPI app using tags, it will normally also separate the client code based on the tags.

This way, you will be able to have things ordered and grouped correctly for the client code:

<img src="/img/tutorial/generate-clients/image06.png">

In this case, you have:

* `ItemsService`
* `UsersService`

### Client Method Names { #client-method-names }

        }
    }

    @Nested
    @DisplayName("State Management Tests")
    class StateManagementTests {

        @Test
        @DisplayName("Should reset state correctly")
        void testReset() {
            // Set initial state
            response.received();
            assertTrue(response.isReceived());

            // Reset
            response.reset();

        } finally {
            concurrentLimiter.close();
        }
    }

    @Test
    public void testAutoCloseableInterface() throws Exception {
        // Test that rate limiter implements AutoCloseable correctly
        try (AuthenticationRateLimiter autoLimiter = new AuthenticationRateLimiter()) {
            assertTrue(autoLimiter.checkAttempt("user", "192.168.1.13"));
        }
        // Should auto-close without issues

/// info | Informação

Como você verá abaixo, isso é muito semelhante ao comportamento antes da versão 0.106.0, mas com várias melhorias e correções de bugs para casos extremos.

///

#### Casos de uso com código de saída antecipado { #use-cases-with-early-exit-code }

                return process.exitValue();
            } catch (final Exception e) {
                logger.error("Could not destroy a process correctly.", e);
            }
        }
        return -1;
    }

    /**
     * Gets the set of session IDs for all currently running processes.
     *
     * @return set of session IDs for running processes