void testInitialTotalBytesWrittenValue() {
            assertEquals(0, response.getTotalBytesWritten());
        }
    }

    @Nested
    @DisplayName("Getter Tests")
    class GetterTests {

        @Test
        @DisplayName("Should get chunksWritten value")
        void testGetChunksWritten() {
            // Initial value should be 0

Mais je vais vous montrer comment améliorer cela ensuite. 🤓

## IDs d’opération personnalisés et meilleurs noms de méthodes { #custom-operation-ids-and-better-method-names }

Vous pouvez **modifier** la façon dont ces operation IDs sont **générés** pour les simplifier et obtenir des **noms de méthodes plus simples** dans les clients.

  public void testFutureBash() {
    if (isWindows()) {
      return; // TODO: b/136041958 - Running very slowly on Windows CI.
    }
    CyclicBarrier barrier =
        new CyclicBarrier(
            6 // for the setter threads
                + 50 // for the listeners
                + 50 // for the blocking get threads,
                + 1); // for the main thread
    ExecutorService executor = newFixedThreadPool(barrier.getParties());

                    "Should throw DcerpcException for missing endpoint");
        }
    }

    @Nested
    @DisplayName("Getter Method Tests")
    class GetterTests {

        @Test
        @DisplayName("Should return correct transport context")
        void testGetTransportContext() throws Exception {

Try to avoid using bitter sarcasm or potentially passive-aggressive comments. If something is wrong, it's better to be direct (try to be gentle) than sarcastic.

Try to be as specific and objective as possible, avoid generalizations.

   * There is no need for a blocking lock; when the lock is not
   * available, threads try other slots (or the base).  During these
   * retries, there is increased contention and reduced locality,
   * which is still better than alternatives.
   *
   * Per-thread hash codes are initialized to random values.
   * Contention and/or table collisions are indicated by failed
   * CASes when performing an update operation (see method

            assertTrue(result.contains("referrals=["));
            assertFalse(result.contains("referrals=[]"));
        }
    }

    @Nested
    @DisplayName("Getter Methods Tests")
    class GetterTests {

        @BeforeEach
        void setupBuffer() {
            // Create buffer with 3 v1 referrals
            byte[] testBuffer = new byte[100];

Aber ich zeige Ihnen als Nächstes, wie Sie das verbessern können. 🤓

## Benutzerdefinierte Operation-IDs und bessere Methodennamen { #custom-operation-ids-and-better-method-names }

Sie können die Art und Weise, wie diese Operation-IDs **generiert** werden, **ändern**, um sie einfacher zu machen und **einfachere Methodennamen** in den Clients zu haben.

        when(response.getCommand()).thenReturn(command);
        response.setCommand(command);
        assertEquals(command, response.getCommand());

        // Test other setter methods
        doNothing().when(response).setUid(1000);
        response.setUid(1000);
        verify(response).setUid(1000);

        doNothing().when(response).setExtendedSecurity(true);

        // snapshot timestamp, or some other timestamp later encoded into the metadata.
        // TODO this needs to be repeated here so the merging doesn't interfere with the written metadata
        //  - we'd be much better having a pristine input, and an ongoing metadata for merging instead

        Map<ArtifactRepository, Metadata> previousMetadata = new HashMap<>();
        ArtifactRepository selected = null;