*/
@NullUnmarked
public class ToStringHelperBenchmark {

  @Param({"0", "1", "5"})
  int dataSize;

  @Param({"false", "true"})
  boolean omitNulls;

  enum Dataset {
    SMALL {
      @Override
      void addEntries(MoreObjects.ToStringHelper helper) {
        helper
            .add(SHORT_NAME, 10)
            .addValue(10L)
            .add(SHORT_NAME, 3.14f)
            .addValue(3.14d)

    }

    @Test
    @DisplayName("Test invalid buffer size for decoding")
    public void testInvalidBufferSize() {
        byte[] smallBuffer = new byte[4]; // Too small

        assertThrows(SMBProtocolDecodingException.class, () -> {
            context.decode(smallBuffer, 0, smallBuffer.length);
        });
    }

    @Test
    @DisplayName("Test algorithm name resolution")

    protected void doReceiveFragment(final byte[] buf, final boolean isDirect) throws IOException {
        int off, flags, length;

        if (buf.length < max_recv) {
            throw new IllegalArgumentException("buffer too small");
        }

        if (isStart && !isDirect) { // start of new frag, do trans
            off = in.read(buf, 0, 1024);
        } else {
            off = in.readDirect(buf, 0, buf.length);
        }

Keep in mind that this means that the whole contents will be stored in memory. This will work well for small files.

But there are several cases in which you might benefit from using `UploadFile`.

## File Parameters with `UploadFile` { #file-parameters-with-uploadfile }

Define a file parameter with a type of `UploadFile`:

 * interaction with {@link NdrBuffer}.  All public behaviour is exercised.
 */
@ExtendWith(MockitoExtension.class)
class NdrShortTest {

    /**
     * A small reusable buffer for encode/decode tests.
     */
    private byte[] raw;
    private NdrBuffer buf;

    @BeforeEach
    void setUp() {
        // 10 bytes is more than enough for the 2-byte short

import jcifs.CIFSContext;
import jcifs.CIFSException;
import jcifs.Credentials;

/**
 * Tests for SmbRenewableCredentials interface.
 *
 * Since this file is an interface with a single method, we provide small
 * helper implementations to exercise expected interaction patterns and edge cases.
 */
@ExtendWith(MockitoExtension.class)
public class SmbRenewableCredentialsTest {

        assertEscaping(xmlEscaper, "\uFFFD", ch);
      }
    }

    // Test _all_ allowed characters (including surrogate values).
    for (char ch = 0x20; ch <= 0xFFFD; ch++) {
      // There are a small number of cases to consider, so just do it manually.
      if (ch == '&') {
        assertEscaping(xmlEscaper, "&amp;", ch);
      } else if (ch == '<') {
        assertEscaping(xmlEscaper, "&lt;", ch);

        assertSame(purgeThumbnailJob, result);
        // Test value was not changed
        assertEquals(originalExpiry, purgeThumbnailJob.getExpiry());
    }

    // Test expiry setter with small positive value
    public void test_expiry_smallPositiveValue() {
        PurgeThumbnailJob result = purgeThumbnailJob.expiry(1L);

        // Test method chaining
        assertSame(purgeThumbnailJob, result);

        });
    }

    @Test
    @DisplayName("Interaction: consumer is invoked for each found mapping")
    void interactionWithConsumerIsAsExpected() {
        // Arrange: choose a small set of known DOS codes
        List<Integer> inputs = Arrays.asList(0x00000000, 0x00050001, 0x007b0001, 0x0BADF00D);
        @SuppressWarnings("unchecked")
        BiConsumer<Integer, Integer> consumer = mock(BiConsumer.class);

**FastAPI** provides several tools to help you deal with **Security** easily, rapidly, in a standard way, without having to study and learn all the security specifications.

But first, let's check some small concepts.

## In a hurry? { #in-a-hurry }

If you don't care about any of these terms and you just need to add security with authentication based on username and password *right now*, skip to the next chapters.