Arrays.fill(dataBuffer, (byte) 0xAB);

            TestCreateContextResponse contextResponse = new TestCreateContextResponse(nameBytes);

            // Simulate decode call
            int dataOffset = 100;
            int dataLength = 200;
            contextResponse.decode(dataBuffer, dataOffset, dataLength);

            // Verify

import okio.BufferedSource
import okio.ByteString

/**
 * A socket connection to a remote peer. A connection hosts streams which can send and receive
 * data.
 *
 * Many methods in this API are **synchronous:** the call is completed before the method returns.
 * This is typical for Java but atypical for HTTP/2. This is motivated by exception transparency:
 * an [IOException] that was triggered by a certain caller can be caught and handled by that caller.

        facetQueryView.init();
        int firstSize = facetQueryView.getQueryMap().size();
        int firstQueriesCount = testFacetInfo.getAddedQueries().size();

        // Call init again
        facetQueryView.init();

        // Size should remain the same
        assertEquals(firstSize, facetQueryView.getQueryMap().size());

            doNothing().when(spyHandle).sendrecv(any(DcerpcMessage.class));

            // When: Binding the handle
            spyHandle.bind();

            // Then: Should call sendrecv with bind message
            verify(spyHandle).sendrecv(any(DcerpcMessage.class));
        }

        @Test
        @DisplayName("Should propagate IOException during bind")

* <a href="https://github.com/swagger-api/swagger-ui" class="external-link" target="_blank"><strong>Swagger UI</strong></a>, with interactive exploration, call and test your API directly from the browser.

![Swagger UI interaction](https://fastapi.tiangolo.com/img/index/index-03-swagger-02.png)

   * implementation of iterator() to define its contents, and methods like contains() are
   * implemented in terms of that method (though they will likely be overridden by subclasses for
   * performance reasons).) This means that a call to this method have can different behavior in GWT
   * and non-GWT environments UNLESS subclasses are careful to always override all methods
   * implemented in terms of sortedDelegate (except comparator()).
   */

        try {
            final NdrBuffer buf = encodeMessage(msg, out);
            final int off = sendFragments(msg, out, buf);

            // last fragment gets written (possibly) using transact/call semantics
            final int have = doSendReceiveFragment(out, off, msg.length, inB);

            if (have != 0) {
                final NdrBuffer hdrBuf = new NdrBuffer(inB, 0);

        List<FileNotifyInformation> notifications = Arrays.asList(mockNotifyInfo1, mockNotifyInfo2);
        MockNotifyResponse response = new MockNotifyResponse(notifications);

        // Call getNotifyInformation multiple times
        List<FileNotifyInformation> result1 = response.getNotifyInformation();
        List<FileNotifyInformation> result2 = response.getNotifyInformation();

	readers         atomic.Int32
	writers         atomic.Int32
	lastCleanup     atomic.Pointer[time.Time]
	locksOverloaded atomic.Int64
}

// getMutex will lock the mutex.
// Call the returned function to unlock.
func (l *localLocker) getMutex() func() {
	l.waitMutex.Add(1)
	l.mutex.Lock()
	l.waitMutex.Add(-1)
	return l.mutex.Unlock
}

func (l *localLocker) String() string {

        // This is actually good security practice - closed authenticators cannot be accessed

        // Verify multiple closes don't cause issues
        auth.close(); // Should be safe to call again
        assertTrue(auth.isClosed());
    }

    /**
     * Test AutoCloseable implementation
     */
    @Test
    @DisplayName("Test AutoCloseable implementation with try-with-resources")