# Probando Dependencias con Overrides { #testing-dependencies-with-overrides }

## Sobrescribir dependencias durante las pruebas { #overriding-dependencies-during-testing }

Hay algunos escenarios donde podrías querer sobrescribir una dependencia durante las pruebas.

No quieres que la dependencia original se ejecute (ni ninguna de las sub-dependencias que pueda tener).

     * Disabled by default - enable with -Dwitness.integration.test=true
     */
    @Test
    void testWitnessEnvironmentConfiguration() throws Exception {
        // Test simulating real witness environment scenarios
        // This test validates integration patterns without requiring real cluster

        // Simulate witness service discovery
        InetAddress mockWitnessAddress = InetAddress.getByName("127.0.0.1");

# Testando Dependências com Sobreposições { #testing-dependencies-with-overrides }

## Sobrepondo dependências durante os testes { #overriding-dependencies-during-testing }

Existem alguns cenários onde você deseje sobrepor uma dependência durante os testes.

Você não quer que a dependência original execute (e nenhuma das subdependências que você possa ter).

In many cases it's not very obvious how environment variables would be useful and applicable right away. But they keep showing up in many different scenarios when you are developing, so it's good to know about them.

Dans de nombreux cas, il n'est pas évident de voir immédiatement en quoi les variables d'environnement seraient utiles et applicables. Mais elles réapparaissent dans de nombreux scénarios lorsque vous développez, il est donc bon de les connaître.

                long minTime = timings.stream().mapToLong(Long::longValue).min().orElse(0L);

                double variance = (maxTime - minTime) / avgTime;
                // JVM timing in concurrent scenarios is inherently variable
                // We verify implementation correctness rather than precise timing
                assertTrue(variance < 50.0,
                        String.format(

     *
     * In high performance mode, expensive regex operations are avoided by doing
     * fast string contains checks first. This significantly improves performance
     * for high-frequency logging scenarios.
     *
     * @param enable true to enable high performance mode
     */
    public void setHighPerformanceModeEnabled(boolean enable) {
        this.enableHighPerformanceMode = enable;

            assertEquals(defaultValue, mimeMap.getMimeType("notinmap", defaultValue));
        }
    }

    @Nested
    @DisplayName("Edge cases and special scenarios")
    class EdgeCases {

        @Test
        @DisplayName("Should handle multiple extensions for same mime type")
        void testMultipleExtensionsForSameMimeType() throws IOException {

            }
            return new GitInfo(revision, findOriginUrl(gitDir.resolve("config")));
        } catch (final IOException e) {
            // for now, do not be lenient until we have better understanding of real-world scenarios where this happens
            throw new GradleException("unable to read the git revision", e);
        }
    }


    private static String findOriginUrl(final Path configFile) throws IOException {

        item.setNewInput(newSpecialInput);
        assertEquals(newSpecialInput, item.toLineString());
    }

    @Test
    public void test_whitespaceHandling() {
        // Test with various whitespace scenarios
        ProtwordsItem item1 = new ProtwordsItem(1, "  word  ");
        assertEquals("  word  ", item1.getInput());
        assertEquals("  word  ", item1.toLineString());