dsccommunity / dsccommunity/ActiveDirectoryDsc
ActiveDirectoryDsc: Document how to run manual integration tests
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 388
- Forks
- 141
- PR merge metrics
- No merged PRs in 30d
Description
As part of the PR #170 integration tests are introduced. THose integration tests cannot be run in AppVeyor as the unit test are, because of the limitation on the AppVeyor build worker.
We should provide a simple guide to how to run the integration tests so they build a lab (when prerequisites are meet).
I suggest we start with Hyper-V and assume there are clean VM's that can be used. Mostly because I have that environment available, and it's part of Windows 10. 🙂
We could add other environments to manual integration tests, like Test-Kitchen, LabBuilder, Lability, etc., and clouds like Azure, AWS, GCP.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading PR #170 and locating the introduced integration tests and their prerequisites. Document the Hyper-V workflow using clean VMs, including how to build the lab and run the tests; the work is done when a contributor can follow the guide without relying on AppVeyor.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- documentation, testing
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100