[go: up one dir, main page]
Skip to content
This repository has been archived by the owner on Jul 26, 2023. It is now read-only.

Latest commit

 

History

History
58 lines (43 loc) · 1.85 KB

TESTING.md

File metadata and controls

58 lines (43 loc) · 1.85 KB
Raw

Test Wazuh Chef cookbooks

Global prerequisistes

There are two ways of creating a chef environment and tests cookbooks depending on what driver to use:

Kitchen-vagrant

Prerequisites

bundle config set --local without 'dokken'
bundle install

Kitchen-dokken

Prerequisites

bundle config set --local without 'vagrant'
bundle install

How to use?

Once you select the driver and install all the dependencies, you can create your first node by running the following Kitchen CI commands:

  1. kitchen list: list all kitchen instances in the form of <suite_name>-<platform_name>
  2. kitchen create <suite_name>-<platform_name>: create a <platform_name> node without cookbooks
  3. kitchen converge <suite_name>-<platform_name>: run cookbooks declared in <suite_name> inside <platform_name> node
  4. kitchen verify <suite_name>-<platform_name>: run tests in specified instance
  5. kitchen destroy <suite_name>-<platform_name>: destroy specified instance
  6. kitchen login <suite_name>-<platform_name>: log in to specified instance

By defaul, kitchen will look for a [.]kitchen.y[a]ml file.

In case you want to use dokken as your driver, you need to specify kitchen.dokken.yml file as the default kitchen configuration file by overriding KITCHEN_YAML env variable, e.g.:

KITCHEN_YAML="kitchen.dokken.yml" kitchen list