test-kitchen/kitchen-pester

Name: kitchen-pester

Owner: Test Kitchen

Description: Pester verifier

Created: 2015-04-03 21:24:28.0

Updated: 2018-02-09 04:55:47.0

Pushed: 2017-06-19 13:24:23.0

Homepage: null

Size: 37

Language: Ruby

GitHub Committers

User	Most Recent Commit	# Commits

Other Committers

User	Email	Most Recent Commit	# Commits

README

Kitchen::Pester

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

Usage

Either

install kitchen-pester

or include

'kitchen-pester'

in your Gemfile.

In your .kitchen.yml include

fier:
me: 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