* Prüfen und lesen Sie den Code, fragen Sie sich, ob er Sinn macht, **führen Sie ihn lokal aus** und testen Sie, ob er das Problem tatsächlich löst.

* Schreiben Sie dann einen **Kommentar** und berichten, dass Sie das getan haben. So weiß ich, dass Sie ihn wirklich überprüft haben.

/// info | Info

Leider kann ich PRs, nur weil sie von mehreren gutgeheißen wurden, nicht einfach vertrauen.

            }
            classDoc.classProperties.each { propertyDoc ->
                linkMetaData.addPropertyAccessorMethod(propertyDoc.name, propertyDoc.metaData.getter ?: propertyDoc.metaData.setter)
            }
        } catch (Exception e) {
            throw new DocGenerationException("Failed to generate documentation for class '$classDoc.name'.", e)
        }
    }

        }

        @Override
        public Collection<Part> getParts() throws IOException, ServletException {
            return null;
        }

        @Override
        public Part getPart(String name) throws IOException, ServletException {
            return null;
        }

        @Override

        @DisplayName("Should initialize remaining to zero")
        void testInitialRemainingValue() {
            assertEquals(0, response.getRemaining());
        }
    }

    @Nested
    @DisplayName("Getter Tests")
    class GetterTests {

        @Test
        @DisplayName("Should get count value")
        void testGetCount() {
            // Initial value should be 0
            assertEquals(0, response.getCount());

        // Data should still be accessible
        assertEquals("Should still have 1 word", 1, suggester.getAllWordsNum());
    }

    // ============================================================
    // Tests for getter methods
    // ============================================================

    @Test
    public void test_getIndex() throws Exception {
        Suggester suggester = createSuggester();

        ntlmConnection.disconnect();

        // Assert
        verify(mockConnection).disconnect();
        // Connection should be closed after disconnect
    }

    /**
     * Test simple getter methods that should trigger the handshake.
     * We mock a simple 200 OK response to test the handshake is called.
     * @throws IOException
     */
    @Test
    void testGettersTriggerHandshake() throws IOException {

        // Get the specific log
        response = checkMethodBase(searchBody).get(API_PATH + "/log/" + logId).asString();
        Map<String, Object> log = JsonPath.from(response).getMap("response.log");

        logger.info("Job log detail: {}", log);
        assertEquals(logId, log.get("id").toString());
        assertTrue(log.containsKey("job_name"), "Log should have job_name field");

        }
    }

    @Test
    void testConstructorAndGettersWithValidTicket() throws IOException, GeneralSecurityException, PACDecodingException {
        // Test successful instantiation and getter methods with a valid ticket
        byte[] validToken = createTestTicketBytes(new BigInteger(KerberosConstants.KERBEROS_VERSION), SERVER_REALM, SERVER_PRINCIPAL_NAME,
                ENCRYPTION_TYPE, ENCRYPTED_DATA, null);

The Gradle codebase has evolved over time and has a mixture of simple getter/setter methods, Provider API and things in between.  It can be hard to follow best practices because Gradle provided types are reused in unexpected ways and extended by third party plugins.

     * @param key The key to look up
     * @return The nested Map, or null if the key doesn't exist or value is not a Map
     */
    @SuppressWarnings("unchecked")
    public static Map<String, Object> getMap(final Map<String, Object> map, final String key) {
        final Object value = map.get(key);
        if (value instanceof Map) {
            return (Map<String, Object>) value;
        }
        return null;
    }