///

## Advanced User Guide { #advanced-user-guide }

There is also an **Advanced User Guide** that you can read later after this **Tutorial - User guide**.

The **Advanced User Guide** builds on this one, uses the same concepts, and teaches you some extra features.

But you should first read the **Tutorial - User Guide** (what you are reading right now).

$(document).ready(function(){
  openPage("home.html");
  setEventHandlers();
});

function setEventHandlers(){
  $('#info').click(function(){ openPage("info.html") } );
  $('#home').click(function(){ openPage("home.html") } );
}

function openPage(page){
  $('#content').load(page);
  location.hash = page;
}

function addFooter(msg){
  $('#footer').html($('#footer').html() + "<p>FOOTER: " + msg + "</p>");

        byte[] smallOutputBuffer = new byte[5];
        TransCallNamedPipeResponse smallResponse = new TransCallNamedPipeResponse(mockConfig, smallOutputBuffer);

        byte[] buffer = new byte[100];

        // Try to read more data than output buffer can hold
        SMBProtocolDecodingException exception =
                assertThrows(SMBProtocolDecodingException.class, () -> smallResponse.readDataWireFormat(buffer, 0, 10));

        bufferIndex += 2;

        // Read flags
        this.flags = SMBUtil.readInt4(buffer, bufferIndex);
        bufferIndex += 4;

        // Validate remaining buffer size for algorithms
        if (len < 8 + (compressionCount * 2)) {
            throw new SMBProtocolDecodingException("Buffer too small for compression algorithms");
        }

        // Read compression algorithms

// Read is never called with an empty buffer.
type testNonEmptyReader struct{ io.Reader }

func (r testNonEmptyReader) Read(b []byte) (int, error) {
	if len(b) == 0 {
		return 0, errors.New("unexpected empty Read call")
	}
	return r.Reader.Read(b)
}

func TestFileReader(t *testing.T) {
	type (
		testRead struct { // Read(cnt) == (wantStr, wantErr)
			cnt     int

type diskHealthWrapper struct {
	tracker *healthDiskCtxValue
	r       io.Reader
	w       io.Writer
}

func (d *diskHealthWrapper) Read(p []byte) (int, error) {
	if d.r == nil {
		return 0, fmt.Errorf("diskHealthWrapper: Read with no reader")
	}
	n, err := d.r.Read(p)
	if err == nil || err == io.EOF && n > 0 {
		d.tracker.logSuccess()
	}
	return n, err
}

            assertArrayEquals(originalBuffer, buffer);
        }
    }

    @Nested
    @DisplayName("Read Bytes Wire Format Tests")
    class ReadBytesWireFormatTests {

        @Test
        @DisplayName("Should read valid structure size of 4")
        void testReadBytesWireFormatValid() throws SMBProtocolDecodingException {
            byte[] buffer = new byte[1024];

# Test Client - `TestClient`

You can use the `TestClient` class to test FastAPI applications without creating an actual HTTP and socket connection, just communicating directly with the FastAPI code.

Read more about it in the [FastAPI docs for Testing](https://fastapi.tiangolo.com/tutorial/testing/).

You can import it directly from `fastapi.testclient`:

```python
from fastapi.testclient import TestClient
```

// ReadMultipleReq contains information of multiple files to read from disk.
type ReadMultipleReq struct {
	Bucket       string   `msg:"bk"`           // Bucket. Can be empty if multiple buckets.
	Prefix       string   `msg:"pr,omitempty"` // Shared prefix of all files. Can be empty. Will be joined to filename without modification.
	Files        []string `msg:"fl"`           // Individual files to read.

It would also mean that if you get data from the `Request` object directly (for example, read the body) it won't be validated, converted or documented (with OpenAPI, for the automatic API user interface) by FastAPI.