}

        @Test
        @DisplayName("should handle strategy exceptions gracefully")
        void shouldHandleStrategyExceptionsGracefully() throws Exception {
            UpgradeContext context = createMockContext();
            Map<Path, Document> pomMap = Map.of(Paths.get("pom.xml"), mock(Document.class));

            // Mock first strategy to throw exception
            when(mockStrategies.get(0).isApplicable(context)).thenReturn(true);

{* ../../docs_src/handling_errors/tutorial002_py39.py hl[14] *}

## Install custom exception handlers { #install-custom-exception-handlers }

You can add custom exception handlers with <a href="https://www.starlette.dev/exceptions/" class="external-link" target="_blank">the same exception utilities from Starlette</a>.

Let's say you have a custom exception `UnicornException` that you (or a library you use) might `raise`.

            List<Exception> exceptions = result.getResolutionErrors(dependency);
            for (Exception e : exceptions) {
                msg.append("\t").append(e.getMessage()).append(System.lineSeparator());
            }
        }

        for (Exception exception : result.getCollectionErrors()) {
            msg.append(exception.getMessage()).append(System.lineSeparator());

            final String message = e.getMessage();
            assertNotNull("Exception message should not be null", message);
            assertFalse("Exception message should not be empty", message.trim().isEmpty());
            assertTrue("Exception message should mention 'inputstream'", message.toLowerCase().contains("inputstream"));
            assertTrue("Exception message should mention 'null'", message.toLowerCase().contains("null"));
        }

        }, "Should throw UnknownHostException for non-existent NetBIOS name with type");

        // Verify the exception message indicates name resolution failure
        assertTrue(exception.getMessage().contains("NONEXISTENT") || exception.getMessage().contains("unknown")
                || exception.getMessage().contains("not found"), "Exception message should indicate name resolution failure");
    }

    @Test

Wenn Sie eine Exception in einer Abhängigkeit mit `yield` abfangen, sollten Sie – sofern Sie nicht eine andere `HTTPException` oder Ähnliches auslösen – **die ursprüngliche Exception erneut auslösen**.

Sie können dieselbe Exception mit `raise` erneut auslösen:

{* ../../docs_src/dependencies/tutorial008d_an_py39.py hl[17] *}

    assertThat(Files.fileTraverser().breadthFirst(rootDir)).containsExactly(rootDir);
  }

  public void testFileTraverser_nonExistingFile() throws Exception {
    File file = new File(rootDir, "file-that-doesnt-exist");

    assertThat(Files.fileTraverser().breadthFirst(file)).containsExactly(file);
  }

  public void testFileTraverser_file() throws Exception {
    File file = newFile("some-file");

    protected void createLocalArtifact(Artifact artifact) throws Exception {
        createArtifact(artifact, localRepository());
    }

    protected void createRemoteArtifact(Artifact artifact) throws Exception {
        createArtifact(artifact, remoteRepository());
    }

    protected void createArtifact(Artifact artifact, ArtifactRepository repository) throws Exception {
        String path = repository.pathOf(artifact);

    }

    @AfterClass
    public static void afterClass() throws Exception {
        runner.close();
        runner.clean();
    }

    @Before
    public void setUp() throws Exception {
        converter = new AnalyzerConverter(client, settings);
    }

    private static void createTestIndex() throws Exception {
        // Create index with custom analyzers

     *
     * @param level the severity level of the message
     * @param message the message to be logged
     * @param error the associated exception, or null if not applicable
     */
    void log(@Nonnull Level level, @Nonnull String message, @Nullable Throwable error);

    /**
     * Logs a debug message without an associated exception.
     *