import static org.mockito.Mockito.verify;
import static org.mockito.Mockito.when;

/**
 * Unit tests for the {@link Apply} goal class.
 * Tests the Apply-specific functionality including file modification behavior.
 */
@DisplayName("Apply")
class ApplyTest {

    private Apply applyGoal;
    private StrategyOrchestrator mockOrchestrator;

    @BeforeEach
    void setUp() {

      render: java
    validations:
      required: true

  - type: textarea
    attributes:
      label: Current Behavior
      description: What does the feature currently do?
    validations:
      required: true

  - type: textarea
    attributes:
      label: Desired Behavior
      description: What do you want it to do instead?
    validations:
      required: true

  - type: markdown
    attributes:

  To request this behaviour, your client software must enable the `WatchListClient` client-go feature gate. Additionally, streaming is only available if supported by the cluster; the API server that you connect to must also support streaming.

        Provide a brief summary of the issue in the title above
  - type: textarea
    id: expected-behavior
    attributes:
      label: Expected Behavior
      description: Tell us how it should work
    validations:
      required: true
  - type: textarea
    id: current-behavior
    attributes:
      label: Current Behavior (optional)
      description: Is there a way to achieve the same or similar outcome today?
    validations:

    validations:
      required: true
  - type: textarea
    id: actual-behavior
    attributes:
      label: "What did you see happen?"
    validations:
      required: true
  - type: textarea
    id: expected-behavior
    attributes:
      label: "What did you expect to see?"
    validations:
      required: true
  - type: textarea

## Expected Behavior
<!--- If you're describing a bug, tell us what should happen -->
<!--- If you're suggesting a change/improvement, tell us how it should work -->

## Current Behavior
<!--- If describing a bug, tell us what happens instead of the expected behavior -->
<!--- If suggesting a change/improvement, explain the difference from current behavior -->

## Possible Solution

    // Mocking MsrpcLsarOpenPolicy2 and MsrpcLsarClose is tricky because they are created inside the constructor/method.
    // We need to use ArgumentCaptor or a custom Answer to control their behavior.
    // For now, let's assume we can mock their behavior through the sendrecv method of DcerpcHandle.

    @BeforeEach
    void setUp() {
        // MockitoAnnotations.openMocks(this); // Not needed with @ExtendWith(MockitoExtension.class)
    }

    - [CSI Health Monitoring](#csi-health-monitoring)
  - [Known Issues](#known-issues)
    - [<code>TopologyAwareHints</code> feature falls back to default behavior](#topologyawarehints-feature-falls-back-to-default-behavior)
  - [Urgent Upgrade Notes](#urgent-upgrade-notes)
    - [(No, really, you MUST read this before you upgrade)](#no-really-you-must-read-this-before-you-upgrade)

This behavior was reverted in 0.118.0, to make the exit code after `yield` be executed after the response is sent.

/// info

As you will see below, this is very similar to the behavior before version 0.106.0, but with several improvements and bug fixes for corner cases.

///

    }

    /**
     * Parameterized version of testActivatedDefaultProfileBySource that demonstrates
     * cross-platform path behavior using JIMFS to simulate both Windows and Unix file systems.
     * This test shows how the path separator expectations differ between platforms.
     */
    @ParameterizedTest(name = "testActivatedDefaultProfileBySource[{0}]")