void release_invokedOnce() throws Exception {
        // Arrange: no setup needed; we verify interaction only

        // Act: call release
        handle.release();

        // Assert: verify one invocation and no more
        verify(handle, times(1)).release();
        verifyNoMoreInteractions(handle);
    }

    @Test

        int apply(FileEntry e);
    }

    private interface LongGetter {
        long apply(FileEntry e);
    }

    // --- Mockito-based interaction tests ---

    @Test
    @DisplayName("Mocked FileEntry returns stubbed values and verifies interactions")
    void mockedEntry_happyPath_and_interactions() {
        // Arrange: stub all methods with representative values

A downside of this structure is that it is difficult to do focused work on the Gradle UI.

## Decision

Introduce a "UI" architecture module to the core platform, and move the user interaction services to this new module.

This includes:

- Logging and progress services.
- Problem generation services (aka the "problems API").
- User prompting services.
- Build options infrastructure.

        wrapper.release();

        // Assert: delegate interactions occur when usage transitions happen
        verify(delegate, times(1)).acquire();
        verify(delegate, times(1)).release();
    }

    @Test
    @DisplayName("finalize() invokes checkRelease exactly once")
    void finalize_invokes_checkRelease() throws Throwable {
        // Arrange: spy to verify internal interaction with checkRelease()

        assertEquals(url, file.getURL(), "Returned SmbFile should wrap the given URL");
        assertSame(mockCtx, file.getContext(), "SmbFile must use the provided CIFSContext");
        verify(mockCtx, atLeastOnce()).getConfig(); // interaction with dependency
    }

    @Test
    @DisplayName("openConnection with null URL throws NullPointerException")
    void testOpenConnection_NullInput() {
        // Arrange

        // Test interface method
        byte level = mockFileInfo.getFileInformationLevel();
        assertEquals(FileInformation.FILE_BASIC_INFO, level);

        // Verify interaction
        verify(mockFileInfo).getFileInformationLevel();
    }

    /**
     * Test FileInformation as Decodable
     */
    @Test
    @DisplayName("Test FileInformation decode method")

            if (tc == null) {
                throw new NullPointerException("tc");
            }
            // Exercise interaction with dependency for verification purposes
            // These methods do not throw and allow interaction checks.
            tc.getConfig();
            tc.getCredentials();

            // Minimal behavior: return a mock SSPContext with lenient stubbing

//
// You should have received a copy of the GNU Affero General Public License
// along with this program.  If not, see <http://www.gnu.org/licenses/>.

package main

// This programs mocks user interaction against Dex IDP and generates STS
// credentials. It is for MinIO testing purposes only.
//
// Run like:
//
// $ MINIO_ENDPOINT=http://localhost:9000 go run gen-oidc-sts-cred.go

import (
	"context"
	"fmt"

                Arguments.of(-1, -2L, -3L, -4L, -5L) // negative values
        );
    }

    // --- Mockito interaction: verify each getter is invoked and returns stubbed values ---
    @Test
    void mockitoMock_verifiesGetterInteractions() {
        // Arrange: mock and stub each getter with distinct values

 * methods (writing parameters and handling empty wire formats) and an
 * informative {@link NtTransQuerySecurityDesc#toString()}. The tests
 * exercise normal behaviour, boundary values, and the interaction with
 * the underlying wire‑format helpers.
 */
@ExtendWith(MockitoExtension.class)
class NtTransQuerySecurityDescTest {

    /**
     * Helper that mimics the write logic used by