Testing a participant is gory-detail-stuff. You must know a lot about the internals of Ruote. Because; In order to 'test' a participant, we have to mimic the environment the participant lives and is executed in.
Since we are isolating the participant in our experiment^W... tests we have to prevent the participant from communicating with Ruote. In order to do so we have replace the #reply function with an own singleton.
| # -*- encoding: utf-8 -*- | |
| Gem::Specification.new do |s| | |
| s.name = "mcollective-client" | |
| s.version = "1.0.2" | |
| s.platform = Gem::Platform::RUBY | |
| s.authors = ["RI Pienaar"] | |
| s.email = ["ripienaar@puppetlabs.com"] | |
| s.homepage = "https://github.com/puppetlabs/marionette-collective" | |
| s.summary = %q{Mcollective client} | |
| s.description = %q{Interact with mcollective} |
| # | |
| # ElasticSearch config file | |
| # | |
| # | |
| # There's no call to see the full current config, but | |
| # modules dump their config variables on startup | |
| # | |
| cluster: |
| #!/usr/bin/env ruby | |
| # Example script to deploy a Rails application via Git post-receive hook | |
| # | |
| # INSTALL | |
| # | |
| # $ curl http://gist.github.com/442106.txt -o post-receive | |
| # $ mv post-receive path/to/to/your/repo.git/hooks/post-receive | |
| # $ chmod +x post-receive |