mockBhv.setTestData(testData);

        int count = relatedQueryHelper.load();
        assertEquals(1, count); // One virtual host key (empty)

        String[] results = relatedQueryHelper.getRelatedQueries("java");
        assertEquals(3, results.length);
        assertEquals("programming", results[0]);

    }

    @Test
    public void test_load_simpleTerms() {
        List<RelatedContent> testData = new ArrayList<>();
        testData.add(createRelatedContent("java", "Java Programming", ""));
        testData.add(createRelatedContent("python", "Python Programming", ""));
        mockBhv.setTestData(testData);

        int count = relatedContentHelper.load();
        assertEquals(1, count); // One virtual host key (empty)

        // assertEquals(0, result.size()); // Commented out due to variable scope
    }

    @Test
    public void test_buildQuery_withVariousKeywords() {
        List<String> keywordList = Arrays.asList("java", "programming", "search", "");
        List<FilterFunctionBuilder> functionBuilders = new ArrayList<>();

        try {
            keyMatchHelper.buildQuery(keywordList, functionBuilders);
        } catch (Exception e) {

American English was chosen for the following reasons:

* **Current predominance**: The majority of existing Gradle code and documentation already uses American English
* **Industry standard**: Most widely used programming languages, frameworks, and tools (Java, Kotlin, JavaScript, etc.) use American English in their APIs and documentation
* **Consistency with dependencies**: Gradle's ecosystem and dependencies predominantly use American English