Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update README.md to reflect test/recipes structure #96

Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ verifier:

### Directory Structure

By default `kitchen-inspec` expects test to be in `test/integration/%suite%` directory structure (we use Chef as provisioner here):
By default `kitchen-inspec` expects tests to be in the `test/recipes/%suite%` directory structure (we use Chef as provisioner here):

```
.
Expand All @@ -52,7 +52,7 @@ By default `kitchen-inspec` expects test to be in `test/integration/%suite%` dir
│   ├── default.rb
│   └── nginx.rb
└── test
└── integration
└── recipes
└── default
└── web_spec.rb
```
Expand All @@ -71,7 +71,7 @@ A complete profile is used here, including a custom inspec resource named `gordo
│   ├── default.rb
│   └── nginx.rb
└── test
└── integration
└── recipes
└── default
├── controls
│   └── gordon.rb
Expand All @@ -80,6 +80,8 @@ A complete profile is used here, including a custom inspec resource named `gordo
└── gordon_config.rb
```

**Note:** If `kitchen-inspec` doesn't find a `test/recipes/%suite%` directory structure, it will look in `test/integration/%suite%`.

### Combination with other testing frameworks

If you need support with other testing frameworks, we recommend to place the tests in `test/integration/%suite%/inspec`:
Expand Down