return response_map.size();
        }
    }

    @BeforeEach
    void setUp() {
        transport = new TestableTransport();
    }

    @Nested
    @DisplayName("Static utility method tests")
    class StaticMethodTests {

        @Test
        @DisplayName("readn should read specified number of bytes")
        void shouldReadSpecifiedBytes() throws IOException {

También incluye qué cambió, cómo las validaciones ahora son más correctas y estrictas, posibles consideraciones, etc.

Puedes leerla para entender mejor qué cambió.

## Tests { #tests }

Asegúrate de tener [tests](../tutorial/testing.md){.internal-link target=_blank} para tu app y de ejecutarlos en integración continua (CI).

Así podrás hacer la actualización y asegurarte de que todo sigue funcionando como esperas.

import static org.junit.jupiter.api.Assertions.assertTrue;

/**
 * Tests {@link ArtifactUtils}.
 *
 */
class ArtifactUtilsTest {

    private Artifact newArtifact(String aid) {
        return new DefaultArtifact("group", aid, VersionRange.createFromVersion("1.0"), "test", "jar", "tests", null);
    }

    @Test
    void testIsSnapshot() {
        assertFalse(ArtifactUtils.isSnapshot(null));

You should add tests for your app.

With **FastAPI** it's very easy (thanks to Starlette), check the docs: [Testing](../tutorial/testing.md){.internal-link target=_blank}

After you have tests, then you can upgrade the **FastAPI** version to a more recent one, and make sure that all your code is working correctly by running your tests.

                        "All Cross-Version Tests for ${stage.stageName.stageName}",
                        "Stage_${stage.stageName.id}_CrossVersionTests",
                        model,
                        crossVersionTests + previousCrossVersionTests,
                    ),
                )
            }

            // in gradleBuildSmokeTest, most of the tests are for using the configuration cache on gradle/gradle

          "name": "TestDistribution"
        }
      },
      {
        "subprojects": [
          "execution-e2e-tests",
          "file-collections",
          "ide",
          "ide-plugins",
          "kotlin-dsl-integ-tests",
          "platform-native",
          "version-control"
        ],
        "parallelizationMethod": {
          "name": "TestDistribution"

Probablemente quieras probar el proveedor externo una vez, pero no necesariamente llamarlo para cada test que se realice.

En este caso, puedes sobrescribir la dependencia que llama a ese proveedor y usar una dependencia personalizada que devuelva un usuario de prueba, solo para tus tests.

            // JavaExecDebugIntegrationTest.debug session fails without debugger might cause JVM crash
            // Some soak tests produce OOM exceptions
            // There are also random worker crashes for some tests.
            // We have test-retry to handle the crash in tests
            javaCrash = false
        }
    })

fun getTestTaskName(
    testCoverage: TestCoverage,

        group = ciGroup
    }

    register("platformTest") {
        description = "Run all unit, integration and cross-version (against latest release) tests in forking execution mode"
        group = ciGroup
    }

    register("quickFeedbackCrossVersionTest") {
        description = "Run cross-version tests against a limited set of versions"

| <<<test-jar>>>        | <<<tests>>>   | <<<jar>>>  | java      | classes, patch module |                       |
*-----------------------+---------------+------------+-----------+-----------------------+-----------------------+
| <<<modular-jar>>> *   | <<<tests>>>   | <<<jar>>>  | java      | modules               |                       |