README.md in vagrant-ovirt4-1.2.0 vs README.md in vagrant-ovirt4-1.2.1

@@ -119,9 +119,28 @@
   1. `cloud_init` => The cloud-init data to pass. Must be properly formatted as yaml. [Docs here](http://cloudinit.readthedocs.io/en/latest/topics/examples.html)
   1. `affinity` =>  The affinity to use. [See this for possible uses](http://www.rubydoc.info/gems/ovirt-engine-sdk/OvirtSDK4/VmAffinity). Optional. Invalid will cause a `RuntimeError`
   1. `placement_host` => The host to start the VM on. Optional.
 
 
+## Testing
+
+Currently pull-requests are tested via [test-kitchen using kitchen-vagrant](https://github.com/test-kitchen/kitchen-vagrant).
+See [Jenkinsfile](Jenkinsfile) for more information. 
+If you'd like to run them yourself, however, they make not work in all setups. For example they assume `192.168.2.0/24`, host pinning will probably not have a host that's in all set ups, and the template names might not match.
+
+To run Unit tests: `bundle install; bundle exec rspec`
+
+To run acceptance tests:
+
+```bash
+export OVIRT_URL='https://yoururl/ovirt-engine/api''
+export OVIRT_USERNAME='yourname@internal'
+export OVIRT_PASSWORD='yourpassword!'
+gem build *.gemspec
+vagrant plugin install *.gem
+bundle exec kitchen test all
+```
+
 ## Contributing
 
 1. Fork it
 2. Create your feature branch (`git checkout -b my-new-feature`)
 3. Commit your changes (`git commit -am 'Add some feature'`)