Downloads:

148,668

Downloads of v 3.0.0-beta:

369

Last Update:

6/25/2014

Package Maintainer(s):

Software Author(s):

  • Pester Team

Tags:

powershell unit testing bdd tdd mocking

Pester

This is a prerelease version of Pester.

3.0.0-beta | Updated: 6/25/2014

Downloads:

148,668

Downloads of v 3.0.0-beta:

369

Maintainer(s):

Software Author(s):

  • Pester Team

Tags:

powershell unit testing bdd tdd mocking

Pester 3.0.0-beta

This is a prerelease version of Pester.

All Checks are Unknown

2 Test of Unknown Status

Hide Checks
Hide Checks

Validation Testing Unknown

Verification Testing Unknown

To install Pester, run the following command from the command line or from PowerShell:

>

To upgrade Pester, run the following command from the command line or from PowerShell:

>

To uninstall Pester, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade pester -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade pester -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure pester installed
  win_chocolatey:
    name: pester
    state: present
    version: 3.0.0-beta
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'pester' do
  action    :install
  version  '3.0.0-beta'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: pester,
    Version: 3.0.0-beta,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller pester
{
   Name     = 'pester'
   Ensure   = 'Present'
   Version  = '3.0.0-beta'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'pester':
  provider => 'chocolatey',
  ensure   => '3.0.0-beta',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install pester version="3.0.0-beta" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 1/20/2015.

Description

Pester provides a framework for running BDD style Tests to execute and validate PowerShell commands inside of PowerShell and offers a powerful set of Mocking Functions that allow tests to mimic and mock the functionality of any command inside of a piece of powershell code being tested. Pester tests can execute any command or script that is accesible to a pester test file. This can include functions, Cmdlets, Modules and scripts. Pester can be run in ad hoc style in a console or it can be integrated into the Build scripts of a Continuous Integration system.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Pester 4.9.0 2493 Sunday, September 8, 2019 Approved
Pester 4.8.1 7925 Saturday, May 11, 2019 Approved
Pester 4.8.0 896 Wednesday, May 1, 2019 Approved
Pester 4.7.3 3269 Saturday, March 23, 2019 Approved
Pester 4.7.2 1201 Friday, March 8, 2019 Approved
Pester 4.7.1 431 Tuesday, March 5, 2019 Approved
Pester 4.7.0 249 Sunday, March 3, 2019 Approved
Pester 4.4.1 8788 Thursday, September 20, 2018 Approved
Pester 4.4.0 4815 Friday, July 20, 2018 Approved
Pester 4.4.0-beta2 102 Sunday, July 8, 2018 Approved

This package has no dependencies.

Discussion for the Pester Package

Ground Rules:

  • This discussion is only about Pester and the Pester package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Pester, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus