5. **Resources**: Test resources are properly managed and cleaned up

## Contributing

When adding new tests:
1. Follow the existing naming convention: `test_<method>_<scenario>_<expectedResult>`
2. Add clear JavaDoc comments explaining the test purpose
3. Ensure tests are independent and can run in any order
4. Clean up resources in finally blocks or use try-with-resources

 * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
 */
package jcifs;

import java.util.Iterator;

/**
 * An iterator that implements AutoCloseable to allow resource cleanup.
 * This interface combines Iterator functionality with automatic resource management.
 *
 * @param <T> the type of elements returned by this iterator
 * @author mbechler
 */

     */
    public UserInfoService() {
        // Default constructor
    }

    /**
     * Deletes user information records older than the specified number of days.
     * This method is used for data cleanup and maintenance operations.
     *
     * @param days the number of days to keep user information records
     */
    public void deleteBefore(final int days) {
        userInfoBhv.queryDelete(cb -> {

 * documents and converting them into a key-value structure.
 *
 * <p>This interface extends {@link java.io.Closeable}, so implementations
 * should also handle resource cleanup when the {@link #close()} method is called.</p>
 */
public interface DocumentReader extends Closeable {
    /**
     * Reads a document and returns its contents as a map.
     *

        tryDrainReferenceQueues();
        return null;
      }

      return value;
    }

    /**
     * Performs routine cleanup following a read. Normally cleanup happens during writes, or from
     * the cleanupExecutor. If cleanup is not observed after a sufficient number of reads, try
     * cleaning up from the read thread.
     */
    void postReadCleanup() {

 * <p>Thread Safety: This class is thread-safe. Each evaluate() call creates
 * a new GroovyShell instance to ensure thread isolation.</p>
 *
 * <p>Resource Management: GroovyClassLoader instances are properly managed
 * and cleaned up after script evaluation to prevent memory leaks.</p>
 */
public class GroovyEngine extends AbstractScriptEngine {
    private static final Logger logger = LogManager.getLogger(GroovyEngine.class);

    /**

   * @param queue that should finalize the referent
   */
  protected FinalizableWeakReference(@Nullable T referent, FinalizableReferenceQueue queue) {
    super(referent, queue.queue);
    queue.cleanUp();
  }

### Other (Cleanup or Flake)

- Adds additional testing to ensure that udp pods conntrack are cleaned up ([#90180](https://github.com/kubernetes/kubernetes/pull/90180), [@JacobTanenbaum](https://github.com/JacobTanenbaum)) [SIG Architecture, Network and Testing]

    }

    /**
     * Deletes all crawling sessions and their parameters except for the specified active sessions.
     * This is a cleanup operation that removes inactive session data while preserving active ones.
     *
     * @param activeSessionId a set of session IDs to preserve during the cleanup operation
     */
    public void deleteOldSessions(final Set<String> activeSessionId) {
        final List<CrawlingInfo> activeSessionList =

    @DisplayName("parseURL: fragment is moved into path and ref cleared")
    void testParseURL_FragmentMovedToPath() throws MalformedURLException {
        // Arrange & Act
        Handler handler = newHandler();
        URL url = new URL(null, "smb://server/share#frag", handler);

        // Assert: ref is moved into path by Handler.parseURL
        assertNull(url.getRef(), "Ref must be cleared by Handler");