a32f34b408
Knife-Zero doesn't include Berkshelf support, so vendoring everything in the repo is convenient again
46 lines
1.2 KiB
Markdown
46 lines
1.2 KiB
Markdown
Testing
|
|
=======
|
|
|
|
Preparation
|
|
-----
|
|
|
|
$ bundle install
|
|
|
|
And then, to install all cookbooks:
|
|
|
|
$ bundle exec berks install
|
|
|
|
Local
|
|
-----
|
|
|
|
$ bundle exec rake
|
|
|
|
The above runs:
|
|
|
|
- rubocop lint
|
|
- Foodcritic lint
|
|
- Chefspec tests
|
|
|
|
Chefspec tests (the interesting part) are in `spec/`.
|
|
|
|
Integration
|
|
-----------
|
|
|
|
$ bundle exec kitchen test
|
|
|
|
See `.kitchen.yml` and `test/` directory for details.
|
|
|
|
It is important to check if the applied hostname and fqdn values remain the same
|
|
also after machine reboot. As it is impossible to reboot using kitchen, it has to
|
|
be done manually:
|
|
|
|
- run `kitchen converge` and `kitchen verify` to ensure your run is error-free,
|
|
- log in to the machine. If you're on a Debian-based system, you need to ensure
|
|
that the `/tmp` folder won't be deleted with rebooting, since that's where busser
|
|
resides. If `/tmp` is deleted, `kitchen verify` will fail after reboot even if a
|
|
manual check confirms that hostname, fqdn and dnsdomainname are correct. You can
|
|
preserve the `/tmp` folder by typing the following in your terminal:
|
|
`sudo find /etc/default/rcS -type f -exec sed -i 's/TMPTIME=0/TMPTIME=-1/g' {} \;`
|
|
- run `sudo reboot`,
|
|
- wait for the machine to reboot and run `kitchen verify` again.
|