Skip to content
This repository
branch: master

Jun 28, 2014

  1. Update changelog for PR 147

    nohwnd authored
  2. Merge pull request #147 from dmonger/print-exception-source

    When PesterThrow catches an unexpected exception, record the source of the exception into the exception message
    nohwnd authored

Jun 27, 2014

  1. dmonger

    When PesterThrow catches an unexpected exception, record the source

    of the exception into the exception message
    dmonger authored

Jun 24, 2014

  1. Fixing TestName

    nohwnd authored

Jun 15, 2014

  1. marking the 2.1.0 release

    nohwnd authored
  2. Enable latest strict mode when running all tests

    Pester.bat is used locally to test the whole suite in clean environment
    and on server to integrate with Team City. This way we can make sure the
    module is kept strict mode compatible.
    nohwnd authored
  3. Merge branch 'dlwyatt-MockSafety'

    nohwnd authored
  4. Dave Wyatt

    Fully-qualified commands

    Fixes #73
    Several calls to built-in PowerShell commands are now module-qualified, making Pester behave properly internally, even if the caller has mocked these commands.
    dlwyatt authored nohwnd committed
  5. Update Mock help to reflect ModuleName parameter

    nohwnd authored

Jun 11, 2014

  1. Dave Wyatt

    Validation of Assertion Method in Should

    Loosely related to the fix in the Issue76 branch, this update validates user input to the Should function.  Instead of producing the stock command not found exception, Should will now produce an error of "'BeNulOrEmpty' is not a valid Should operator." (where the user had misspelled BeNullOrEmpty, in this case.)
    dlwyatt authored nohwnd committed
  2. Merge branch 'dlwyatt-StrictModeFixes'

    nohwnd authored
  3. Dave Wyatt

    Initialize $PesterException

    "It" initializes $PesterException for Strict Mode compatibility.
    Fixes #75
    dlwyatt authored nohwnd committed

Jun 08, 2014

  1. Dave Wyatt

    Fix Parse-ShouldArgs in PowerShell strict mode

    Parse-ShouldArgs now works properly if StrictMode has been enabled, performing bounds checking on the $shouldArgs array before indexing.  It also throws an error if no AssertionMethod was passed (ie, ( | Should ) or ( | Should not )).
    Fixes #76
    dlwyatt authored nohwnd committed
  2. Fix internal module support to work on PowerShell 2

    Also fixing the TC build again
    nohwnd authored
  3. Fix Team City builds

    the & made the nUnit.xml impossible to parse. quick-fixing this. There
    is #122 issue for this.
    nohwnd authored
  4. Add more links to further reading and resources

    nohwnd authored

Jun 07, 2014

  1. alebrun7

    Fix error message in Testdrive Cleanup

    Sort the folders before deleting to avoid error
    Fixes #128
    alebrun7 authored nohwnd committed
  2. skataben

    Added support for mocking:

    * internal module methods
    * alias commands
    * application commands
    * filter commands
    Added partial mocking support for:
    * fully-qualified command names (fully qualified cmdlet invocations are not supported)
    * external script commands
      The only supported scenarios are when the script is invoked using one of the following methods:
        & scriptName.ps1
        . scriptName.ps1
    Added corresponding unit tests.
    skataben authored nohwnd committed

May 17, 2014

  1. Describe throw if no fixture

    If fixture is not specified, typically when you start the script block
    on next line, an exception is thrown from Describe. Fixing #132
    nohwnd authored

May 05, 2014

  1. Scott Muc

    updating CHANGELOG for pester.bat execution policy

    scottmuc authored
  2. Scott Muc

    Merge pull request #131 from nfisher/master

    [fixes #130] Changed ExecutionPolicy to Bypass to avoid failure.
    scottmuc authored

Apr 30, 2014

  1. Nathan Fisher

    [fixes #130] Changed ExecutionPolicy to Bypass to avoid failure.

    It would appear combining the flags -ExecutionPolicy Unrestricted and
     -NonInteractive causes the following error;
    Import-Module : File E:\Pester\Pester.psm1 cannot be loaded. The file
    E:\Pester\Pester.psm1 is not digitally signed. The script will not execute
    on the system. Please see "get-help about_signing" for more details..
    See the following TechNet article for details on ExecutionPolicy settings;
    nfisher authored

Apr 19, 2014

  1. skataben

    Fix Should Throw filtering by exception message

    skataben authored nohwnd committed

Apr 12, 2014

  1. Process It in memory

    Instead of creating the Temp.ps1 script in TestDrive the It blocks are
    processed directly in memory. Fixes #123
    nohwnd authored

Mar 10, 2014

  1. Fixing hash signs in Describe name

    Fixing issue introduced in 605ee37.
    Hash tags placed around Describe name in auto-generated test files.
    nohwnd authored
  2. Scott Muc

    updating docs to use latest should syntax

    scottmuc authored

Mar 09, 2014

  1. Scott Muc

    marking the 2.0.4 release

    scottmuc authored
  2. Fix tag filter

    Fix the tag filter that I broke. We really need a test for this.
    nohwnd authored
  3. Move New-Fixture out of Pester.psm1

    - Moved New-Fixture and Create-File to separate script file
    - Discarded Write-UsageForNewFixture. Usage can be looked up by
    Get-Help, so inline help becomes the only place to update if interface
    nohwnd authored
  4. New-Fixture standardized

    - Accept and resolve paths on input as other cmdlets do.
    - Output standard objects.
    - Using only Name parameter you can create fixture in the current
    directory .
    - If file exists Warning is issued.
    - Numerous internal amendments to make the function easier to read.
    - Adding Tests
    - not moving the function out of Pester.psm1 to make the changes easier
    to track.
    nohwnd authored
  5. Scott Muc

    Merge branch 'fix_exceptions_in_new-fixture'

    scottmuc authored
  6. Fixes Bug #114: New-Fixture raises exception when using $pwd directly…

    … as -Path parameter.
    Restricts parameters to [string] instead of letting powershell decide which datatype to use
    Administrator authored scottmuc committed

Mar 03, 2014

  1. Add PassThru option to Invoke-Pester

    When called with -PassThru the Invoke-Pester returns object on exit. The
    object contains information about the whole run and about each test.
    nohwnd authored
  2. Make output better structured

    Moving the margin before the [+] in the test output. This makes for a
    tree-like structure in which it is easier to see what tests are in
    Describe and what are in Context
    nohwnd authored
  3. Clean up Invoke-Pester interface

    Standard PowerShell cmdlets use singular nouns for their Parameters and
    standardized set of parameter names like 'Path'. Changing Invoke-Pester
    interface to reflect this. To keep backwards compatibility the changed
    parameters are aliased.
    nohwnd authored
Something went wrong with that request. Please try again.