# Extractor Implementation Tests

This directory contains comprehensive tests for the Extractor implementations, focusing on the improvements made to resource management, error handling, and input validation.

## Test Files Overview

### 1. ExtractorResourceManagementTest.java
**Purpose**: Verify proper resource management in Extractor implementations.

**Key Test Areas**:
- Resource closure on successful extraction (MS Office extractors)

        } catch (final IOException e) {
            throw new DictionaryException("Failed to parse " + path, e);
        }
    }

    /**
     * Returns the simple file name (without directory path) of this mapping file.
     *
     * @return the file name without the full path
     */
    public String getSimpleName() {
        return new File(path).getName();
    }

    /**

                false), FILE_EXISTS("File already exists", ErrorCategory.FILE_SYSTEM, false), DIRECTORY_NOT_EMPTY("Directory not empty",
                        ErrorCategory.FILE_SYSTEM, false), DISK_FULL("Disk full", ErrorCategory.RESOURCE,
                                false), QUOTA_EXCEEDED("Quota exceeded", ErrorCategory.RESOURCE, false),

                if (!canonicalPath.startsWith(baseCanonicalPath)) {
                    throw new IllegalArgumentException("File path is outside allowed directory");
                }
            }
        } catch (final IOException e) {
            throw new IllegalArgumentException("Invalid file path", e);
        }
    }

    /**

        } catch (Exception e) {
            // Ignore cleanup errors
        }
        suggester.shutdown();
    }

    /**
     * Test that resource files can be loaded successfully.
     * This indirectly tests getDefaultMappings and getDefaultIndexSettings.
     */
    @Test
    public void testResourceLoading_viaIndexCreation() throws Exception {

            throw new IllegalArgumentException("Path exceeds maximum length: " + path.length());
        }
        if (PATH_TRAVERSAL.matcher(path).find()) {
            throw new IllegalArgumentException("Path contains directory traversal sequences: " + path);
        }
        if (INVALID_PATH_CHARS.matcher(path).find()) {
            throw new IllegalArgumentException("Path contains invalid characters: " + path);
        }
    }

        // These tests validate current behavior where problematic paths are caught by other checks

        // Test invalid server name with dots - caught by directory traversal check
        assertThrows(SmbException.class, () -> {
            validator.validatePath("\\\\..\\share");
        });

        // Test invalid characters in paths - caught by null byte check

        assertNotNull(buffer, "Buffer should not be null");
        assertTrue(buffer.capacity() >= 2048, "Buffer should be at least requested size");
        assertTrue(buffer.isDirect(), "Buffer should be direct");
    }

    @Test
    public void testReleaseBuffer() {
        ByteBuffer buffer = bufferManager.allocateBuffer(1024);

        // Release should not throw exception

 * to interact with SMB resources.
 *
 * <p>
 * This client supports authentication, content retrieval, and metadata extraction from SMB files.
 * It handles file access, directory listing, and access control entries (ACEs) processing.
 * </p>
 *
 * <p>
 * The class provides methods to:
 * </p>
 * <ul>
 *   <li>Initialize the client with SMB authentication details.</li>

import jcifs.internal.util.SMBUtil;
import jcifs.util.Hexdump;

/**
 * SMB2 Create response message. This response contains the file ID and attributes
 * of the created or opened file or directory.
 *
 * @author mbechler
 *
 */
public class Smb2CreateResponse extends ServerMessageBlock2Response implements SmbBasicFileInfo {