Pester verifier
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
lib added test and fix to ignore case Jun 19, 2017
spec/pester added test and fix to ignore case Jun 19, 2017
test/integration/default/pester add a real kitchen test to run locally and on appveyor Sep 25, 2016
.gitignore add a real kitchen test to run locally and on appveyor Sep 25, 2016
.kitchen.appveyor.yml add a real kitchen test to run locally and on appveyor Sep 25, 2016
.kitchen.yml add a real kitchen test to run locally and on appveyor Sep 25, 2016
Gemfile add a real kitchen test to run locally and on appveyor Sep 25, 2016
LICENSE
README.md Add Build Badge Sep 26, 2016
Rakefile Support for PowerShell 2 May 21, 2015
appveyor.yml
kitchen-pester.gemspec add a real kitchen test to run locally and on appveyor Sep 25, 2016
provision.ps1 add a real kitchen test to run locally and on appveyor Sep 25, 2016

README.md

Build status Gem Version

Kitchen::Pester

Execute Pester tests right from Test-Kitchen, without having to transit the Busser layer.

Usage

Either

gem install kitchen-pester

or include

gem 'kitchen-pester'

in your Gemfile.

In your .kitchen.yml include

verifier:
  name: pester

This can be a top-level declaration, a per-node declaration, or a per-suite declaration.

Options

  • restart_winrm - boolean, default is false. This is primarily to support powershell v2 scenarios. If Pester is not being found, enable this option.
  • test_folder - string, default is nil. test-folder allows you to specify a custom path (the default is ./test/integration/) for your integration tests. This can be an absolute path or relative to the root of the folder kitchen is running from. This path must exist.

Contributing

  1. Fork it ( https://github.com/[my-github-username]/kitchen-pester/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request