dsccommunity / dsccommunity/ComputerManagementDsc
ScheduledTask: Add Test to cover 'StopExisting' value in MultipleInstances Parameter
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 338
- Forks
- 80
- PR merge metrics
- No merged PRs in 30d
Description
The StopExisting value in the MultipleInstances parameter must be handled in a special way because it is missing from the ENUM used by the underlying cmdlets/objects.
We don't have unit tests that specifically cover the use of this, so either extract the handling into a function that can be mocked and/or add an integration test.
See https://github.com/dsccommunity/ComputerManagementDsc/pull/335
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 reviewing PR #335 and the ScheduledTask handling of the MultipleInstances parameter, focusing on the special StopExisting value and its interaction with the underlying cmdlets or objects. Add focused coverage, either around an extracted mockable function or through an integration test, and confirm the StopExisting case is handled correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- operating-systems, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100