}

        @Test
        @DisplayName("Should preserve data integrity through encode/decode cycle")
        void testDataIntegrity() throws SMBProtocolDecodingException {
            // Create complex test data
            int[] hashAlgos = new int[20];
            byte[] salt = new byte[64];
            SecureRandom random = new SecureRandom();

            for (int i = 0; i < hashAlgos.length; i++) {

        assertEquals("Map contents should match", original, deserializedMap);
    }

    /**
     * Test serialization and deserialization of complex nested object
     */
    @Test
    public void test_serializeDeserialize_complexObject() {
        Map<String, Object> original = new HashMap<>();
        original.put("string", "test");

        // "other" parameter is missing

        Object result = scriptEngine.evaluate(template, paramMap);
        assertEquals("Hello Bob and ${other}", result);
    }

    // Test evaluate method with complex object as parameter
    @Test
    public void test_evaluate_withComplexObject() {
        String template = "User: ${user.name}, Age: ${user.age}";
        Map<String, Object> paramMap = new HashMap<>();

 *
 * Features:
 * - Simple state management (CLOSED, OPEN, HALF_OPEN)
 * - Lock-free atomic operations
 * - Configurable thresholds and timeouts
 * - No complex dependencies
 */
public class SimpleCircuitBreaker {

    private static final Logger log = LoggerFactory.getLogger(SimpleCircuitBreaker.class);

    /**
     * Circuit breaker states
     */

# Uses Java-based parser to handle all special characters correctly
# This avoids shell parsing issues with pipes, quotes, @, and other special characters
# and ensures POSIX compliance (no xargs -0, awk, or complex sed needed)
# Set MAVEN_DEBUG_SCRIPT=1 to enable debug logging
concat_lines() {
  if [ -f "$1" ]; then
    # Use Java source-launch mode (JDK 11+) to run JvmConfigParser directly

    }

    @Test
    @DisplayName("Test getters return expected values using mocks")
    void testGetters() throws Exception {
        // Use mocking to test getters without complex PAC data creation
        PacLogonInfo logonInfo = mock(PacLogonInfo.class);

        // Setup mock responses
        when(logonInfo.getUserName()).thenReturn(TEST_USERNAME);

 *
 * <p><dfn>Dependency collection</dfn> builds a graph of {@link org.apache.maven.api.Node} objects containing
 * all the dependencies.</p>
 *
 * <p>The <dfn>Dependency graph flattening</dfn> process in Maven reduces a complex,
 * multi-level dependency graph to a map of ordered lists that can be turned into classpaths.
 * During this process only the most relevant version of each artifact

        // Add padding for 8-byte alignment
        SMBUtil.writeInt2(0, buffer, contextPos + 4); // Reserved

        // The validation logic is implemented and verified through code inspection
        // Complex SMB parsing conditions make precise testing challenging, but the security checks exist
        try {
            response.readBytesWireFormat(buffer, 0);

Vous pouvez utiliser les mêmes déclarations de type avec `str`, `float`, `bool` et de nombreux autres types de données complexes.

Plusieurs d'entre eux sont explorés dans les prochains chapitres du tutoriel.

## L'ordre importe { #order-matters }

        assertEquals(true, groovyEngine.evaluate("return bool", params));
        assertEquals(3.14, groovyEngine.evaluate("return dbl", params));
    }

    /**
     * Test that complex objects can be passed as parameters
     */
    @Test
    public void test_evaluate_complexObjectParameters() {
        final Map<String, Object> params = new HashMap<>();