Mocking cmdlet with dynamic parameters not working

[abhinitmodi]

Hey,
I am trying to use an azure-commandlet which uses dynamic parameters. The commandlet is new-azureresourcegroupdeployment. I am mocking it in the following way

Mock New-AzureResourceGroupDeployment { throw "No appropriate mock called for New-AzureResourceGroupDeployment" }
Mock New-AzureResourceGroupDeployment -MockWith { return $validResourceGroupDeployment } -ParameterFilter{$Name -eq $validResourceGroupName -and $ResourceGroupName -eq $validResourceGroupName -and $TemplateFile -eq $validTemplatePath}

But when I run my tests, I get the exception:

Cannot retrieve the dynamic parameters for the cmdlet. Exception calling "GetDynamicParameters" with "0" argument(s): "Object reference not set to an instance of an object

Am I missing something. Could you please point me to an example where you have mocked a commandlet which has dynamic parameters. I was using the 3.3.6 version. I upgraded to 3.3.8 and tried again but was not successful.

Thanks

[dlwyatt]

I'll take a look at this later today when I have time. There have been a couple of instances of weird cmdlets that break the dynamic parameter mocking code (such as the AD module). Could be that there's something new happening in these Azure cmdlets that I need to support in Pester.

[abhinitmodi]

Thanks dave. That would be helpful

[dlwyatt]

I haven't been able to reproduce this yet. This code doesn't give me the error you reported:

Describe 'Test' {
    Mock New-AzureResourceGroupDeployment { throw "No appropriate mock called for New-AzureResourceGroupDeployment" }

    It 'Works' {
        { New-AzureResourceGroupDeployment -ResourceGroupName Test } | Should Throw
    }
}

I tested this with the latest version of the Azure module, which was just released.

In the code you posted, you had a second version of the mock with a parameter filter, but the variables that the mock depends on were not included. If you can provide the values that you were assigning to those variables, I can try to run that version of the mock and see if it fails.

[dlwyatt]

I mocked the command with a parameter filter as well; still no problems, using the latest AzureResourceManager module and Pester 3.3.8.

[abhinitmodi]

In my case the New-AzureResourceGroupDeployment cmdlet is used inside a function. And I am writing tests against that function mocking the behavior of the azure cmdlet. Would that make a difference?

[dlwyatt]

No, that shouldn't matter.

[alx9r]

Hi @dlwyatt,
I think I'm encountering this same problem. And I think I have a repro:

Get-Command New-AzureRmResourceGroupDeployment | % ModuleName
[string](Get-Module AzureRM.Resources).Version
Write-Host Pester
[string](Get-Module Pester).Version

Describe 'Describe' {
    Mock New-AzureRmResourceGroupDeployment

    It 'this throws Exception calling "GetDynamicParameters"' {
        New-AzureRmResourceGroupDeployment -ResourceGroupName Test -TemplateFile Test
    }
}

which yields

Are you able to reproduce this problem on your machine?

[autonomousit]

@alx9r that's the exact issue I'm seeing except I have Pester 3.4.0 The AzureRM.Resources module is 3.0.1, same as yours

@dlwyatt - I've got a Mock from AzureRM.Profiles for Add-AzureRmAccount that works fine but New-AzureRmResourceGroupDeployment cmdlet won't mock. I've tried both "Mock -ModuleName" & "InModuleScope -ModuleName" syntax with the same result. I haven't tried any other cmdlets yet

[adbertram]

I'm running into this problem now too.

[adbertram]

I'm running into this as well. I'm on 3.4.4. I'm receiving this error using the same command as referenced here. However, it has worked. I'm not sure what state I have to get this into to repro it. I'm using the latest AzureRM module (3.3.0) as well.

[alx9r]

I don't think this is Pester-version-dependent. I'm seeing the following results:

• 3.0.0, 3.0.1, 3.0.1.1 -- no error
• 3.0.2 and later -- error

Mocking dynamic parameters seems to have been implemented between 3.0.1.1 and 3.0.2.

Here is the repro code I'm using. It checks out each Pester version starting at 3.0.0 and tries to mock New-AzureRmResourceGroupDeployment.

[adbertram]

I have gotten it to work in 3.4.4. However, I'm unsure what state it was in when it did work.

…

On Thu, Jan 12, 2017 at 5:07 PM, alx9r ***@***.***> wrote: I don't think this is Pester-version-dependent. I'm seeing the following results: - 3.0.0, 3.0.1, 3.0.1.1 -- no error - 3.0.2 and later -- error Mocking dynamic parameters seems to have been implemented between 3.0.1.1 and 3.0.2 <3.0.1.1...3.0.2>. Here is the repro code <https://gist.github.com/alx9r/7749f3a0657941d0b5839128dcf19feb> I'm using. It checks out each Pester version starting at 3.0.0 and tries to mock New-AzureRmResourceGroupDeployment. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#339 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEG3-uPiBiTUIzk7fEvWVPl5De2PITUrks5rRrIlgaJpZM4EMnAx> .