Pester

I am using below code , and seeing error , please advice and correct me. Thanks in advance. Import-

I've been able to mock a PSSession like this: [System.Runtime.Serialization.FormatterServices]::

Hi, this snippet works very well. May you help me with the same but for the powershell Desktop (5.1)?

Your helper functions were dot-sourced into the test script, but your mock exists in the psTwillo

Hi Craig! You can be interested to follow the issue Support `-Timeout` for test cases #983. Wojciech

Ah that's great - thanks Chris! I obviously misunderstood how the parameter filter worked. On

Awesome! Thanks again. I'm reading this now for my lunch break. On Monday, March 20, 2017 at 4:09

Just a quick touch base to my thread here to say I am really, really happy that "-Pending"

I know that BeforeAll fires once for all tests in a given Command.Test.ps1 file. Is there a way to

Let's assume they belong in the same set of tests from the Context perspective. It doesn't

Hi, you can use tests described http://www.lazywinadmin.com/2016/05/using-pester-to-test-your-comment

Well, you could mock Read-Host and then use Assert-MockCalled to ensure that it was called, for

I asked a similar question on StackOverflow: Compare the properties of two PsCustomObjects. On Friday

I resolved that issue by moving part of code to a separate function. Then a mocked that function.

Thanks, Chris. This was indeed exactly what was triggering the tests to run on import. I added a -

Thanks, Dave. This is probably what we'll end up doing. For now I've moved on to other,

Hi, I'm supporter of Format-Pester project. Format-Pester is Powershell module for documenting

Makes sense. Thanks for the help. On Wednesday, June 1, 2016 at 2:23:42 PM UTC-5, Chris Dent wrote:

Just a quick correction; this proof: $list.GetType() -isnot [System.Collections.ArrayList] Should

Hmm, Ok that would be a way to do it, but I don't think that would be the best way for the cmdlet

Thanks Dave, Let me try that. On Wednesday, May 18, 2016 at 6:54:21 PM UTC+5:30, Dave Wyatt wrote:

excellent news, thanks Dave. When is v4 due? (No rush, just interested to know) On Tuesday, 10 May

ErrorId is in now. Adds quite a lot of handling code to PesterThrow to achieve that, may or may not

Is it that you need to expose the methods? If you're not constrained by type you can create: Mock

Not yet, but that would be pretty easy to add as a feature, and wouldn't even bloat the interface

Err sorry my example has some redundant variable definition. Here is a cleaned up version that also

Cool, that make sense. Thanks! On Wednesday, December 9, 2015 at 2:22:06 AM UTC+1, Dave Wyatt wrote:

You might call it MatchValues and use Compare-Object instead of –contains which will likely simplify

Thanks Dave, Linking my blog post around the topic to here. I have few other questions and will be

Sorry the comments still say load the dummy AD Module :) The code sample is from my tests. On