Cluster: Integration test is missing for this resource

[johlju]

Details of the scenario you tried and the problem that is occurring:
We should add an integration test for this resource. And make sure that integration tests are only run in AppVeyor since it evolves setting up a Active Directory Domain Controller.

if ($env:APPVEYOR -eq $true)

And provide instructions how to run the integration tests on a local lab server.

The DSC configuration that is using the resource (as detailed as possible):
n/a

Version of the Operating System and PowerShell the DSC Target Node is running:
n/a

Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev

[johlju]

See rundown of the options to make this happen here dsccommunity/SqlServerDsc#186 (comment).

[johlju]

I looking at using Hyper-V (which comes bundled with Windows 10) and provision (deploy) the necessary infrastructure using DSC with, for example, LabBuilder or Lability. I'm open to other lab frameworks.
I'm currently looking at LabBuilder because that has sample infrastructure configurations already available that can be reused. But the below I'm hoping can be used regardless of lab framework with minor adjustments.

Happy to get comments on this.

How I see this could work.

It should be two configurations, one integration test script, one cleanup script and finally a "remove"-script.

Configurations:

• First configuration deploys the necessary infrastructure (DC, CA, DHCP, SAN etc).
• Second configuration deploys two nodes prepared with the Failover Clustering features enabled.

Test script:
After the second configuration is deployed, the integration tests script is run. The test script runs the normal integrations test, and those integration tests are based on the templates provided by DscResources repository.

Cleanup:
If the integration tests fail, then I'm thinking about a clean up script. The clean up script reverts the changes the integration tests did, and removed the configuration of the second script. This could also be used to be able to run a second test after new code changes. I'm seeing that the the steps are repeated from the second configuration script, to be able to run integration tests multiple times on the same host.

Remove script:
This removes the entire testing infrastructure from the Hyper-V host. But it should try to leave any other servers or networks intact.

[johlju]

It is possible to create a cluster without a domain. So maybe we can use that simplify the integration tests. Although we could not test all aspects of the resource.

#147