```Python
app.dependency_overrides = {}
```

/// tip | Consejo

Si quieres sobrescribir una dependencia solo durante algunos tests, puedes establecer la sobrescritura al inicio del test (dentro de la función del test) y restablecerla al final (al final de la función del test).

package org.gradle.test.sub;

public class SubClass {

    protected ArtifactRepository badLocalRepository() throws Exception {
        String path = "target/test-repositories/" + component() + "/bad-local-repository";

        File f = new File(getBasedir(), path);

        f.createNewFile();

        return artifactRepositoryFactory.createArtifactRepository(
                "test", "file://" + f.getPath(), repoLayout, null, null);
    }

    protected String getRepositoryLayout() {

 */

package gradlebuild.basics.testing

import org.gradle.api.tasks.testing.Test


enum class TestType(val prefix: String, val executers: List<String>) {
    INTEGRATION("integ", listOf("embedded", "forking", "noDaemon", "parallel", "configCache", "isolatedProjects")),
    CROSSVERSION("crossVersion", listOf("embedded", "forking"))
}


fun Test.includeSpockAnnotation(fqcn: String) {

    <groupId>org.apache.maven.its.mng3899</groupId>
    <artifactId>parent</artifactId>
    <version>0.1</version>
  </parent>

  <artifactId>child</artifactId>

  <name>Maven Integration Test :: MNG-3899</name>
  <description>
    Test that build extensions are properly merged during inheritance.
  </description>

  <build>
    <!-- project extensions should precede inherited extensions -->
    <extensions>
      <extension>

import com.fasterxml.jackson.module.kotlin.registerKotlinModule
import java.io.File

val ignoredSubprojects =
    listOf(
        "soak", // soak test
        "distributions-integ-tests", // build distribution testing
        "architecture-test", // sanity check
    )

interface GradleSubprojectProvider {
    val subprojects: List<GradleSubproject>

/**
 * Verifies the correct behavior of a feature, as opposed to just a small unit of code.
 * Usually referred to as 'functional tests' in literature, but our code base has historically
 * been using the term 'integration test'.
 */
@CacheableTask
abstract class IntegrationTest : DistributionTest() {

    override val prefix = if (name.contains("CrossVersion")) "crossVersion" else "integ"

    @InputDirectory

			if err != nil && testCase.success {
				t.Fatalf("Test %d: unexpected error: %v", i+1, err)
			}
			_, _, err = createServerEndpoints(testCase.serverAddr, srvCtxt.Layout.pools, srvCtxt.Layout.legacy)
			if err != nil && testCase.success {
				t.Errorf("Test %d: Expected success but failed instead %s", i+1, err)
			}
			if err == nil && !testCase.success {
				t.Errorf("Test %d: Expected failure but passed instead", i+1)
			}
		})
	}

        }
    })

class FlakyTestQuarantineProject(
    model: CIBuildModel,
    stage: Stage,
    val os: Os,
) : Project({
        id("${model.projectId}_FlakyQuarantine_${os.asName()}")
        name = "Flaky Test Quarantine - ${os.asName()}"

        model.stages
            .filter { it.stageName <= StageName.READY_FOR_RELEASE }
            .flatMap { it.functionalTests }

            "tags": [],
            "tax": None,
        },
    ]


def test_create_item(client: TestClient):
    item_data = {
        "name": "Test Item",
        "description": "A test item",
        "price": 10.5,
        "tax": 1.5,
        "tags": ["test", "item"],
    }
    response = client.post("/items/", json=item_data)
    assert response.status_code == 200, response.text
    assert response.json() == item_data