// Setup test script engine
        scriptEngineFactory.add("test", testScriptEngine);

        // Execute script
        String scriptType = "test";
        String script = "test script content";
        Object result = scriptExecutor.execute(scriptType, script);

        // Verify result
        assertEquals("processed: test script content", result);

    }

    /**
     * Evaluates a Groovy script template with the provided parameters.
     *
     * <p>This method caches compiled Script classes per script text.
     * Each evaluation creates a new Script instance to ensure thread-safe binding isolation.
     * The DI container is automatically injected into the binding map as "container".</p>
     *
     * @param template the Groovy script to evaluate (null-safe, returns null if empty)

        final Map<String, Object> params = new HashMap<>();
        final String script = "def map = [name: 'Alice', age: 30]; return map.name + ' is ' + map.age";
        assertEquals("Alice is 30", groovyEngine.evaluate(script, params));
    }

    // ===== Multi-line Script Tests =====

    /**
     * Test that multi-line scripts work
     */
    @Test
    public void test_evaluate_multilineScript() {

```

</div>

### Docs Structure

The documentation uses [MkDocs](https://www.mkdocs.org/).

And there are extra tools/scripts in place to handle translations in `./scripts/docs.py`.

/// tip

You don't need to see the code in `./scripts/docs.py`, you just use it in the command line.

///

All the documentation is in Markdown format in the directory `./docs/en/`.

Dieses Dokument testet, ob das <abbr title="Large Language Model – Großes Sprachmodell">LLM</abbr>, das die Dokumentation übersetzt, den <abbr title="General Prompt – Allgemeiner Prompt">`general_prompt`</abbr> in `scripts/translate.py` und den sprachspezifischen Prompt in `docs/{language code}/llm-prompt.md` versteht. Der sprachsspezifische Prompt wird an `general_prompt` angehängt.

////

//// tab | Windows PowerShell

<div class="termy">

```console
$ .venv\Scripts\Activate.ps1
```

</div>

////

//// tab | Windows Bash

Ou si vous utilisez Bash pour Windows (par exemple [Git Bash](https://gitforwindows.org/)) :

<div class="termy">

```console
$ source .venv/Scripts/activate
```

</div>

////

/// tip | Astuce

# Archivo de prueba de LLM { #llm-test-file }

Este documento prueba si el <abbr title="Large Language Model - Modelo de lenguaje grande">LLM</abbr>, que traduce la documentación, entiende el `general_prompt` en `scripts/translate.py` y el prompt específico del idioma en `docs/{language code}/llm-prompt.md`. El prompt específico del idioma se agrega al final de `general_prompt`.

# Fichier de test LLM { #llm-test-file }

Ce document teste si le <abbr title="Large Language Model - Grand modèle de langage">LLM</abbr>, qui traduit la documentation, comprend le `general_prompt` dans `scripts/translate.py` et l’invite spécifique à la langue dans `docs/{language code}/llm-prompt.md`. L’invite spécifique à la langue est ajoutée à la fin de `general_prompt`.

Les tests ajoutés ici seront visibles par tous les concepteurs d’invites spécifiques à chaque langue.

# Arquivo de teste de LLM { #llm-test-file }

Este documento testa se o <abbr title="Large Language Model - Modelo de Linguagem de Grande Porte">LLM</abbr>, que traduz a documentação, entende o `general_prompt` em `scripts/translate.py` e o prompt específico do idioma em `docs/{language code}/llm-prompt.md`. O prompt específico do idioma é anexado ao `general_prompt`.

Os testes adicionados aqui serão vistos por todos os designers dos prompts específicos de idioma.

# LLM test file { #llm-test-file }

This document tests if the <abbr title="Large Language Model">LLM</abbr>, which translates the documentation, understands the `general_prompt` in `scripts/translate.py` and the language specific prompt in `docs/{language code}/llm-prompt.md`. The language specific prompt is appended to `general_prompt`.

Tests added here will be seen by all designers of language specific prompts.

Use as follows: