Using Minitest for "Other" Resources


#1

Sorry if this is a dumb question, but I’m not having much luck in finding an
answer.

I’ve been using minitests for a short while now in my recipes, so I have a
basic understanding of how it works. What I’m trying to figure out is how to
test a resource that is not one of the pre-defined ones here:

Specifically what I’m trying to do is something like:
chef_gem(“blah”).must_be_installed

Whats the best/proper way to be able to that? I tried the above, and it of
course didn’t work. I was also trying to see if I could use the pre-defined
package resource and specify the provider, like you might do in a recipe,
without success.


#2

Any chance, someone has any advice for me on this? I’ve restored to doing a
system call and gem list as a totally hack workaround, given
the multitude of ways it could not work right, but my ruby skillz are not
top notch, and I’m struggling to understand how I might expose the resource
for testing like shown below.

Any advice at all would be greatly appreciated.
Thanks

On Wed, Oct 31, 2012 at 11:36 AM, davidpetzel@gmail.com wrote:

Sorry if this is a dumb question, but I’m not having much luck in finding
an
answer.

I’ve been using minitests for a short while now in my recipes, so I have a
basic understanding of how it works. What I’m trying to figure out is how
to
test a resource that is not one of the pre-defined ones here:

https://github.com/calavera/minitest-chef-handler/blob/master/lib/minitest-chef-handler/resources.rb#L31

Specifically what I’m trying to do is something like:
chef_gem(“blah”).must_be_installed

Whats the best/proper way to be able to that? I tried the above, and it of
course didn’t work. I was also trying to see if I could use the
pre-defined
package resource and specify the provider, like you might do in a recipe,
without success.


#3

erm, how about this for resource “foo”?

require ‘minitest/chef’ # or require ‘minitest-chef’ ??
MiniTest::Chef::Resources.register_resource(:foo)

or if that doesn’t work, re-opening the module

module MiniTest
module Chef
module Resources
register_resource(:foo)
end
end
end

just an idea

On Thu, Nov 1, 2012 at 10:34 PM, David Petzel davidpetzel@gmail.com wrote:

Any chance, someone has any advice for me on this? I’ve restored to doing a
system call and gem list as a totally hack workaround, given the multitude
of ways it could not work right, but my ruby skillz are not top notch, and
I’m struggling to understand how I might expose the resource for testing
like shown below.

Any advice at all would be greatly appreciated.
Thanks

On Wed, Oct 31, 2012 at 11:36 AM, davidpetzel@gmail.com wrote:

Sorry if this is a dumb question, but I’m not having much luck in finding
an
answer.

I’ve been using minitests for a short while now in my recipes, so I have a
basic understanding of how it works. What I’m trying to figure out is how
to
test a resource that is not one of the pre-defined ones here:

https://github.com/calavera/minitest-chef-handler/blob/master/lib/minitest-chef-handler/resources.rb#L31

Specifically what I’m trying to do is something like:
chef_gem(“blah”).must_be_installed

Whats the best/proper way to be able to that? I tried the above, and it of
course didn’t work. I was also trying to see if I could use the
pre-defined
package resource and specify the provider, like you might do in a recipe,
without success.


#4

I’ve used something similar to the following in the past:
https://gist.github.com/3996907

If I were to do this often, I would probably send a pull request adding chef_gem to minutest-chef.

John

On Thursday, November 1, 2012 at 2:53 PM, Bryan Berry wrote:

erm, how about this for resource “foo”?

require ‘minitest/chef’ # or require ‘minitest-chef’ ??
MiniTest::Chef::Resources.register_resource(:foo)

or if that doesn’t work, re-opening the module

module MiniTest
module Chef
module Resources
register_resource(:foo)
end
end
end

just an idea

On Thu, Nov 1, 2012 at 10:34 PM, David Petzel <davidpetzel@gmail.com (mailto:davidpetzel@gmail.com)> wrote:

Any chance, someone has any advice for me on this? I’ve restored to doing a
system call and gem list as a totally hack workaround, given the multitude
of ways it could not work right, but my ruby skillz are not top notch, and
I’m struggling to understand how I might expose the resource for testing
like shown below.

Any advice at all would be greatly appreciated.
Thanks

On Wed, Oct 31, 2012 at 11:36 AM, <davidpetzel@gmail.com (mailto:davidpetzel@gmail.com)> wrote:

Sorry if this is a dumb question, but I’m not having much luck in finding
an
answer.

I’ve been using minitests for a short while now in my recipes, so I have a
basic understanding of how it works. What I’m trying to figure out is how
to
test a resource that is not one of the pre-defined ones here:

https://github.com/calavera/minitest-chef-handler/blob/master/lib/minitest-chef-handler/resources.rb#L31

Specifically what I’m trying to do is something like:
chef_gem(“blah”).must_be_installed

Whats the best/proper way to be able to that? I tried the above, and it of
course didn’t work. I was also trying to see if I could use the
pre-defined
package resource and specify the provider, like you might do in a recipe,
without success.


#5

This doesn’t address the minitest question, but it’s a handy way to check for a required gem. It doesn’t narrow the possibilities down to a specific version, but it can be a quick sanity check.

Simply try requiring the gem, wrapped inside a begin/rescue block:

begin
require 'httparty’
rescue LoadError
Chef::Log.warn(“Missing gem ‘httparty’”)
chef_gem ‘httparty’ ## go ahead and install the gem once you’ve found it’s missing.
require ‘httparty’ ## then require it again
end

Dang H. Nguyen

On 11/1/12 2:34 PM, “David Petzel” <davidpetzel@gmail.commailto:davidpetzel@gmail.com> wrote:

Any chance, someone has any advice for me on this? I’ve restored to doing a system call and gem list as a totally hack workaround, given the multitude of ways it could not work right, but my ruby skillz are not top notch, and I’m struggling to understand how I might expose the resource for testing like shown below.

Any advice at all would be greatly appreciated.
Thanks

On Wed, Oct 31, 2012 at 11:36 AM, <davidpetzel@gmail.commailto:davidpetzel@gmail.com> wrote:
Sorry if this is a dumb question, but I’m not having much luck in finding an
answer.

I’ve been using minitests for a short while now in my recipes, so I have a
basic understanding of how it works. What I’m trying to figure out is how to
test a resource that is not one of the pre-defined ones here:

Specifically what I’m trying to do is something like:
chef_gem(“blah”).must_be_installed

Whats the best/proper way to be able to that? I tried the above, and it of
course didn’t work. I was also trying to see if I could use the pre-defined
package resource and specify the provider, like you might do in a recipe,
without success.


#6

On Thu, Nov 1, 2012 at 5:59 PM, John Dewey john@dewey.ws wrote:

I’ve used something similar to the following in the past:
https://gist.github.com/3996907

erm, how about this for resource “foo”?

require ‘minitest/chef’ # or require ‘minitest-chef’ ??
MiniTest::Chef::Resources.register_resource(:foo)

Some really great answers!!

John, Your approach was uber simple and directly addressed the specific use
case I provided, and did the trick.

Bryan, Your answer addressed my wider question of “other resources”. I
couldn’t get the exact code you gave me working, however it made things
click for me, so I was able to get the following working:

require 'minitest-chef-handler’
MiniTest::Chef::Resources.register_resource(:chef_gem)
describe_recipe ‘my_recipe::default’ do
it “installs the gem with the proper version” do
chef_gem(“foo”).must_be_installed.with(:version, “0.1.0”)
end
end

Thanks again!!