Skip to content

Remove Mock fallthrough #2654

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
nohwnd wants to merge 1 commit into
base: main
Choose a base branch
from
+37 −78

Mock fallthrough

20b9cdd
Select commit
Loading
Failed to load commit list.
Draft

Remove Mock fallthrough #2654

Mock fallthrough
20b9cdd
Select commit
Loading
Failed to load commit list.
Azure Pipelines / Pester PR (Test PS7_Windows_Server2019) failed Jul 3, 2025 in 4m 25s

Test PS7_Windows_Server2019 failed

28 errors / 3 warnings

Annotations

Check failure on line 3252 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR (Test PS7_Windows_Server2019)

Build log #L3252 

 [-] <ScriptBlock> failed with:

Check failure on line 3841 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR (Test PS7_Windows_Server2019)

Build log #L3841 

 [-] When calling Mock on existing function without matching bound params.Should throw because not mock matched the invocation 17ms (16ms|1ms)

Check failure on line 3849 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR (Test PS7_Windows_Server2019)

Build log #L3849 

 [-] When calling Mock on existing function without matching unbound arguments.Should throw because not mock matched the invocation 28ms (26ms|2ms)

Check failure on line 3857 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR (Test PS7_Windows_Server2019)

Build log #L3857 

 [-] When calling Mock on a module-internal function..Using Mock -ModuleName "ModuleName" "CommandName" syntax.Should only call mocks within the same module 15ms (14ms|1ms)

Check failure on line 3861 in Build log

See this annotation in the file changed.

@azure-pipelines azure-pipelines / Pester PR (Test PS7_Windows_Server2019)

Build log #L3861 

 [-] When calling Mock on a module-internal function..Using Mock -ModuleName "ModuleName" "CommandName" syntax.Should work even if the function is weird and steps on the automatic $ExecutionContext variable. 8ms (7ms|1ms)
View more details on Azure Pipelines