}

    @Nested
    @DisplayName("Wire Format Tests")
    class WireFormatTests {

        @Test
        @DisplayName("Should read parameters wire format")
        void testReadParametersWireFormat() {
            byte[] buffer = new byte[10];
            int result = response.readParametersWireFormat(buffer, 0, 2);
            assertEquals(2, result);
        }

        @Test
        @DisplayName("Should write setup wire format")

import org.jspecify.annotations.NullMarked;

/**
 * Tests serialization and deserialization of an object, optionally asserting that the resulting
 * object is equal to the original.
 *
 * <p><b>GWT warning:</b> Under GWT, both methods simply returns their input, as proper GWT
 * serialization tests require more setup. This no-op behavior allows test authors to intersperse

# Run specific test class
mvn test -Dtest=CurlTest
mvn test -Dtest=CurlRequestTest
mvn test -Dtest=CurlResponseTest
mvn test -Dtest=CurlExceptionTest

# Run I/O layer tests
mvn test -Dtest=ContentCacheTest
mvn test -Dtest=ContentOutputStreamTest
mvn test -Dtest=IOIntegrationTest
```

### Code Quality
```bash
# Format code
mvn formatter:format

# Check/update license headers
mvn license:check

        "Quick Feedback - Linux Only",
        "Run checks and functional tests (embedded executer, Linux)",
        "QuickFeedbackLinuxOnly",
    ),
    QUICK_FEEDBACK("Quick Feedback", "Run checks and functional tests (embedded executer, Windows)", "QuickFeedback"),
    PULL_REQUEST_FEEDBACK("Pull Request Feedback", "Run various functional tests", "PullRequestFeedback"),
    READY_FOR_NIGHTLY(
        "Ready for Nightly",

            **/build/git-checkout/build/distributions/*.zip => promote-build-distributions
            **/build/git-checkout/build/reports/integTest/** => distribution-tests
            **/build/releases-data-checkout/data/releases.xml
            **/smoke-tests/build/reports/tests/** => post-smoke-tests
            **/build/version-info.properties => version-info.properties
            """.trimIndent(),
        )

        dependencies {

...
BUILD SUCCESSFUL in 1m 30s
63 actionable tasks: 61 executed, 2 up-to-date

```

The benefit of a dedicated project for these tests are:
- `qa` projects are dedicated two specific usecases and easier to maintain
- It keeps the specific test logic separated from the common test logic.
- You can run those tests in parallel to other projects of the build.

#### Using test fixtures

Sometimes we want to share test fixtures to setup the code under test across multiple projects. There are basically two ways doing so.

def clusterCredentials = [
        username: providers.systemProperty('tests.rest.cluster.username')
                .forUseAtConfigurationTime()
                .getOrElse('test_admin'),
        password: providers.systemProperty('tests.rest.cluster.password')
                .forUseAtConfigurationTime()
                .getOrElse('x-pack-test-password')
]

tasks.withType(StandaloneRestIntegTestTask).configureEach {

Cuando necesitas que `lifespan` se ejecute en tus tests, puedes usar el `TestClient` con un statement `with`:

{* ../../docs_src/app_testing/tutorial004_py310.py hl[9:15,18,27:28,30:32,41:43] *}


Puedes leer más detalles sobre ["Ejecutar lifespan en tests en el sitio oficial de documentación de Starlette."](https://www.starlette.dev/lifespan/#running-lifespan-in-tests)

	if err != nil {
		t.Fatal(err)
	}
	for i, test := range utf8Tests {
		flags := r.File[i].Flags
		if flags != test.flags {
			t.Errorf("CreateHeader(name=%q comment=%q nonUTF8=%v): flags=%#x, want %#x", test.name, test.comment, test.nonUTF8, flags, test.flags)
		}
	}
}

func TestWriterTime(t *testing.T) {
	var buf bytes.Buffer
	h := &FileHeader{
		Name:     "test.txt",