- For timestamp tests: use minimal delays (50-100ms)
- Clean only test-specific indices (not `_all` unless needed)
- Use `runner.refresh()` after index operations
- Test with realistic multilingual content

### Key Test Classes

- `SuggesterRefactoringTest` - Index lifecycle, alias management
- `SuggesterTest` - Core functionality
- `SuggestIndexerTest` - Indexing operations

        assertEquals("test_stackTracePresent", firstElement.getMethodName());
    }

    @Test
    public void test_multipleExceptionScenarios() {
        // Test multiple realistic exception scenarios

        // Scenario 1: Command not found
        CommandExecutionException cmdNotFound = new CommandExecutionException("Command 'xyz' not found");

        assertTrue(memory2 >= 0);
        // Memory usage should have changed (though we can't guarantee direction due to GC)
    }

    @Test
    public void test_integrationScenarios() {
        // Test realistic scenarios combining multiple methods
        String memoryLog1 = MemoryUtil.getMemoryUsageLog();

        // Create some objects and measure their sizes
        List<String> testData = new ArrayList<>();

    }

    // Additional tests for escapeWildcardQuery
    @Test
    public void testEscapeWildcardQueryWithMixedContent() {
        // Test with realistic query containing wildcards and regular text
        String query = "find*all?documents.pdf";
        String escaped = SuggestUtil.escapeWildcardQuery(query);
        assertEquals("find\\*all\\?documents.pdf", escaped);
    }

 *
 * <ol>
 *   <li>remove();
 *   <li>hasNext()
 *   <li>hasNext();
 *   <li>remove();
 *   <li>next();
 * </ol>
 *
 * <p>This particular order of operations may be unrealistic, and testing all 3^5 of them may be
 * thought of as overkill; however, it's difficult to determine which proper subset of this massive
 * set would be sufficient to expose any possible bug. Brute force is simpler.
 *

 *
 * <ol>
 *   <li>remove();
 *   <li>hasNext()
 *   <li>hasNext();
 *   <li>remove();
 *   <li>next();
 * </ol>
 *
 * <p>This particular order of operations may be unrealistic, and testing all 3^5 of them may be
 * thought of as overkill; however, it's difficult to determine which proper subset of this massive
 * set would be sufficient to expose any possible bug. Brute force is simpler.
 *