Cada `dict` específico del ejemplo en los `examples` puede contener:

* `summary`: Descripción corta del ejemplo.
* `description`: Una descripción larga que puede contener texto Markdown.
* `value`: Este es el ejemplo real mostrado, e.g. un `dict`.
* `externalValue`: alternativa a `value`, una URL que apunta al ejemplo. Aunque esto puede no ser soportado por tantas herramientas como `value`.

Puedes usarlo así:

		inlineConds      []interface{}
	)

	if rel.JoinTable != nil {
		var (
			joinForeignFields    = make([]*schema.Field, 0, len(rel.References))
			joinRelForeignFields = make([]*schema.Field, 0, len(rel.References))
			joinForeignKeys      = make([]string, 0, len(rel.References))
		)

		for _, ref := range rel.References {
			if ref.OwnPrimaryKey {

// specified by the developer. The purpose is to simulate errors
// that are hard to simulate in practice like DiskNotFound.
// Programmed errors are stored in errors field.
type naughtyDisk struct {
	// The real disk
	disk StorageAPI
	// Programmed errors: API call number => error to return
	errors map[int]error
	// The error to return when no error value is programmed
	defaultErr error
	// The current API call number

     */
    @Test
    @DisplayName("Test FileInformation implementation with spy")
    void testFileInformationWithSpy() throws SMBProtocolDecodingException {
        // Create spy on real object
        FileEndOfFileInformation realObject = new FileEndOfFileInformation(4096L);
        FileEndOfFileInformation spy = Mockito.spy(realObject);

        // Call methods

            // This test focuses on the logic based on the URL structure.
            SmbFile file = new SmbFile("smb1://server/share/file.txt");
            // Without a real connection, getType relies on path parsing.
            // getUncPath0() will result in a path > 1, so it should be TYPE_FILESYSTEM
            assertEquals(SmbFile.TYPE_FILESYSTEM, file.getType());
        }

			}
			// check the doc https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html
			// For metadata values like "ö", "ÄMÄZÕÑ S3", and "öha, das sollte eigentlich
			// funktionieren", tested against a real AWS S3 bucket, S3 may encode incorrectly. For
			// example, "ö" was encoded as =?UTF-8?B?w4PCtg==?=, producing invalid UTF-8 instead
			// of =?UTF-8?B?w7Y=?=. This mirrors errors like the ä½ in another string.
			//

            this.realm = p.getProperty("jcifs.http.basicRealm");
            this.netbiosLookupRespLimit = Config.getInt(p, "jcifs.netbios.lookupRespLimit", 3);
            this.netbiosCacheTimeout = Config.getInt(p, "jcifs.netbios.cachePolicy", 60 * 10) * 60; /* 10 hours */

            if (this.realm == null) {
                this.realm = "jCIFS";
            }

        }
    }

    // Integration test with actual MD5 to verify HMAC calculation logic
    @Test
    void testHMACT64WithActualMD5() throws NoSuchAlgorithmException {
        // This test uses a real MD5 instance to verify the HMAC calculation logic
        // HMACT64 is a modified HMAC-MD5 where the key is truncated at 64 bytes
        // instead of being hashed when it exceeds the block size.

For this simple example, we are going to just be completely insecure and return the same `username` as the token.

/// tip

In the next chapter, you will see a real secure implementation, with password hashing and <abbr title="JSON Web Tokens">JWT</abbr> tokens.

But for now, let's focus on the specific details we need.

///

    private NetShareEnum netShareEnum;
    private Configuration realConfig;

    @BeforeEach
    void setUp() throws Exception {
        MockitoAnnotations.openMocks(this);
        // Use real configuration for most tests
        realConfig = new BaseConfiguration(false);
        // Mock configuration setup
        when(mockConfig.getTransactionBufferSize()).thenReturn(65535);
    }

    @Test