Skip to content

Address #2214 Remove BOD warnings from powershell unit tests#2275

Draft
jessco-ecs wants to merge 3 commits into
mainfrom
fix/2214-remove-bod-warnings-from-pester-tests
Draft

Address #2214 Remove BOD warnings from powershell unit tests#2275
jessco-ecs wants to merge 3 commits into
mainfrom
fix/2214-remove-bod-warnings-from-pester-tests

Conversation

@jessco-ecs

@jessco-ecs jessco-ecs commented Jul 8, 2026

Copy link
Copy Markdown
Collaborator

🗣 Description

💭 Motivation and context

🧪 Testing

✅ Pre-approval checklist

  • This PR has an informative and human-readable title.
  • PR targets the correct parent branch (e.g., main or release-name) for merge.
  • Changes are limited to a single goal - eschew scope creep!
  • Changes are sized such that they do not touch excessive number of files.
  • All future TODOs are captured in issues, which are referenced in code comments.
  • These code changes follow the ScubaGear content style guide.
  • Related issues these changes resolve are linked preferably via closing keywords.
  • All relevant type-of-change labels added.
  • All relevant project fields are set.
  • All relevant repo and/or project documentation updated to reflect these changes.
  • Unit tests added/updated to cover PowerShell and Rego changes.
  • Functional tests added/updated to cover PowerShell and Rego changes.
  • All automated checks (e.g., linting, static analysis, unit/smoke tests) passed.

✅ Pre-merge checklist

  • PR passed smoke test check.

  • PR/feature branch passes functional tests for relevant products, if applicable.

  • Feature branch has been rebased against changes from parent branch, as needed.

    Use Update branch button below or use this reference to rebase from the command line.

  • Resolved all merge conflicts on branch.

  • Squash all commits into one PR level commit using the Squash and merge button.

✅ Post-merge checklist

  • Feature branch deleted after merge to clean up repository.
  • Close issues resolved by this PR if the closing keywords did not activate.
  • Verified that all checks pass on parent branch (e.g., main or release-name) after merge.

@buidav buidav added the public-reported This issue is reported by the public users of the tool. label Jul 8, 2026
@dagarwal-ecs dagarwal-ecs removed the public-reported This issue is reported by the public users of the tool. label Jul 8, 2026
@FollyBeachGurl FollyBeachGurl marked this pull request as draft July 8, 2026 16:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants