Sha256: 286f11515cd322092b98e2d7686f2f9c0503ca9174d7a9a82c2d6c3b7c0ccac5

Contents?: true

Size: 814 Bytes

Versions: 1

Compression:

Stored size: 814 Bytes

Contents

[![Gem Version](https://badge.fury.io/rb/kitchen-pester.svg)](http://badge.fury.io/rb/kitchen-pester)
# Kitchen::Pester

Execute [Pester](https://github.com/pester/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.

## 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

Version data entries

1 entries across 1 versions & 1 rubygems

Version Path
kitchen-pester-0.3.0 README.md