microsoft / microsoft/PowerShell-FeatureFlags
Add an end-to-end test of installation from PSGallery
Open
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 24
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
We should have a daily test where we install the cmdlets from PSGallery and run a simple test to verify that the most common user journey (download from PSGallery) works as expected.
Contributor guide
No contributing guide indexed for this repository
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 locating the repository's existing test and CI configuration, then identify how PowerShell modules are installed and published to PSGallery. Add a daily end-to-end check that installs the module from PSGallery and exercises the most common cmdlet journey; done means the installation and simple feature-flags test pass successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100