SMBUtil.writeInt4(chunkBytes, buffer, 4);
            SMBUtil.writeInt4(totalBytes, buffer, 8);
            return buffer;
        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should maintain state after multiple decodes")
        void testMultipleDecodes() throws SMBProtocolDecodingException {

            // Verify chunk count is zero
            assertEquals(0, SMBUtil.readInt4(buffer, startIndex + SOURCE_KEY_SIZE));
        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should handle complete copy operation with multiple chunks")
        void testCompleteCopyOperation() {
            // Given

## Execution of dependencies with `yield` { #execution-of-dependencies-with-yield }

The sequence of execution is more or less like this diagram. Time flows from top to bottom. And each column is one of the parts interacting or executing code.

```mermaid
sequenceDiagram

participant client as Client
participant handler as Exception handler
participant dep as Dep with yield
participant operation as Path Operation

La primera parte de la comunicación es solo para establecer la conexión entre el cliente y el servidor y decidir las claves criptográficas que usarán, etc.

<img src="/img/deployment/https/https02.drawio.svg">

Esta interacción entre el cliente y el servidor para establecer la conexión TLS se llama **handshake TLS**.

### TLS con Extensión SNI

    assertFalse("stopAsync has deadlocked!.", stoppingThread.isAlive());
    failLeave.countDown(); // release the background thread
  }

  /**
   * Catches a bug where when constructing a service manager failed, later interactions with the
   * service could cause IllegalStateExceptions inside the partially constructed ServiceManager.
   * This ISE wouldn't actually bubble up but would get logged by ExecutionQueue. This obfuscated

* `/items/`
* `/items/{item_id}`

...as we intended.

* They will be marked with a list of tags that contain a single string `"items"`.
    * These "tags" are especially useful for the automatic interactive documentation systems (using OpenAPI).
* All of them will include the predefined `responses`.
* All these *path operations* will have the list of `dependencies` evaluated/executed before them.

    private DfsReferralDataInternal concreteImplementation;

    @BeforeEach
    void setUp() {
        MockitoAnnotations.openMocks(this);
        // Using concrete implementation for integration testing
        // Note: DfsReferralDataImpl default constructor creates an object with null server/share/path
        // Some methods like fixupHost/fixupDomain require these to be set via combine() or fromReferral()

            // Response should be created with the same config from context
            verify(mockContext, times(1)).getConfig();
        }
    }

    @Nested
    @DisplayName("Integration Tests")
    class IntegrationTests {

        @Test
        @DisplayName("Should handle complete write request workflow")
        void testCompleteWriteWorkflow() {
            // Setup complete request

  - Support allocatable resources overrides via VMSS tags
  - Add missing stable labels in template nodes
  - Proactively set instance status to deleting on node deletions
  
  ### Cluster API
  - Migrate interaction with the API from using internal types to using Unstructured
  - Improve tests to work better with constrained resources
  - Add support for node auto-discovery
  - Add support for `--cloud-config`

            assertEquals((short) -1, bb.getShort());
            assertEquals(65535, Short.toUnsignedInt((short) -1));
        }
    }

    @Nested
    @DisplayName("Integration Tests with SMBUtil")
    class SMBUtilIntegrationTests {

        @Test
        @DisplayName("Should use SMBUtil.writeInt2 for referral level")
        void testSMBUtilWriteInt2ForReferralLevel() {