- **[DPE University Free Courses](https://dpeuniversity.gradle.com/app/catalog)**: A collection of hands-on courses for learning Gradle, complete with project-based tasks to improve real-world skills.
- **[Gradle Community Resources](https://community.gradle.org/resources/)**: Discover a range of resources, tutorials, and guides to support your Gradle journey, from foundational concepts to advanced practices.

---

        // When: Request another connection
        // Note: Real SmbTransportImpl will report as disconnected without actual socket
        SmbTransportImpl second = testPool.getSmbTransport(ctx, address, 445, false);

        // Then: Will create new connection since real transport has no socket
        assertNotSame(first, second, "Should create new connection when first is disconnected");

 * These tests verify end-to-end behavior with real strategy implementations.
 */
@DisplayName("Upgrade Workflow Integration")
class UpgradeWorkflowIntegrationTest {

    @TempDir
    Path tempDir;

    private Apply applyGoal;
    private Check checkGoal;

    @BeforeEach
    void setUp() {
        // Create real strategy instances for integration testing

        mocks = MockitoAnnotations.openMocks(this);

        when(context.getConfig()).thenReturn(config);
        when(config.isDirectoryNotificationsEnabled()).thenReturn(false);

        // Create real lease manager for integration testing
        baseLeaseManager = new LeaseManager(context);
        directoryLeaseManager = new DirectoryLeaseManager(context, baseLeaseManager);
    }

    @AfterEach

                try {
                    // Note: Actual SMB2 Change Notify implementation would go here
                    // For now, this is a placeholder that simulates monitoring

                    // In a real implementation, we would:
                    // 1. Send SMB2 Change Notify request
                    // 2. Wait for response
                    // 3. Process changes
                    // 4. Notify the lease manager

Si integras tu API con un proveedor OAuth2, podrás autenticarte y regresar a la documentación de la API con las credenciales adquiridas. E interactuar con ella usando la autenticación real de OAuth2.

Swagger UI lo manejará detrás de escena para ti, pero necesita este auxiliar de "redirección".

///

### Crea una *path operation* para probarlo { #create-a-path-operation-to-test-it }

Se você integrar sua API com um provedor OAuth2, você poderá autenticar e voltar para a documentação da API com as credenciais adquiridas. E interagir com ela usando a autenticação OAuth2 real.

Swagger UI lidará com isso nos bastidores para você, mas ele precisa desse auxiliar de "redirecionamento".

///

### Criar uma *operação de rota* para testar { #create-a-path-operation-to-test-it }

        assertEquals(capacity, mockAllocInfo.getCapacity());
    }

    /**
     * Null pointer scenario – calls on a null reference should raise
     * {@link NullPointerException}. This test is defensive; in real code it
     * would likely be handled elsewhere.
     */
    @Test
    @DisplayName("calling getters on null reference throws NPE")
    void testNullReference() {
        AllocInfo nullRef = null;

    27.0, depends on
    listenablefuture-9999.0-empty-to-avoid-conflict-with-guava. The 9999.0-...
    version number is enough for some build systems (notably, Gradle) to select
    that empty artifact over the "real" listenablefuture-1.0 -- avoiding a
    conflict with the copy of ListenableFuture in guava itself. If users are
    using an older version of Guava or a build system other than Gradle, they

		// of such a bucket. This is needed here as we identify such
		// buckets here while listing buckets. As part of regular
		// globalBucketMetadataSys.Init() call would get a valid
		// buckets only and not the quourum lost ones like this, so
		// explicit call
		for bktName, count := range bucketsMap {
			if count < quorum {
				// Queue a bucket heal task