diff options
author | chris <chris@opscodes-macbook-pro-2.local> | 2009-09-23 22:08:41 +0000 |
---|---|---|
committer | chris <chris@opscodes-macbook-pro-2.local> | 2009-09-23 22:11:01 +0000 |
commit | 480938b0faf62ea264b33d4140ca11561a8235b1 (patch) | |
tree | 2c50a349f117f2dbdd3d968ec876b19670331721 /features/cookbooks | |
parent | 8ae8a64b8564d19123600434dafc3bf4adfeb9ff (diff) | |
download | chef-480938b0faf62ea264b33d4140ca11561a8235b1.tar.gz |
Adding embedded resources inside providers and some re-factoring in the core. There are cucumber tests for the new functionality, but unit tests are not included in this commit.
Diffstat (limited to 'features/cookbooks')
-rw-r--r-- | features/cookbooks/lightweight_resources_and_providers.feature | 18 |
1 files changed, 17 insertions, 1 deletions
diff --git a/features/cookbooks/lightweight_resources_and_providers.feature b/features/cookbooks/lightweight_resources_and_providers.feature index 908d7a129a..1c567906fd 100644 --- a/features/cookbooks/lightweight_resources_and_providers.feature +++ b/features/cookbooks/lightweight_resources_and_providers.feature @@ -19,8 +19,15 @@ Feature: Light-weight resources and providers | provider_is_a_symbol | Provider is a symbol | | provider_is_a_class | Provider is a class | + @solo + Scenario: Chef solo properly handles providers that invoke resources in their action definitions + Given a local cookbook repository + When I run chef-solo with the 'lwrp::provider_invokes_resource' recipe + Then the run should exit '0' + And a file named 'lwrp_touch_file.txt' should exist + @client @api - Scenario Outline: Chef client handles light-weight resources and providers + Scenario Outline: Chef-client handles light-weight resources and providers Given a validated node And it includes the recipe 'lwrp::<recipe>' When I run the chef-client @@ -37,3 +44,12 @@ Feature: Light-weight resources and providers | provider_is_a_string | Provider is a string | | provider_is_a_symbol | Provider is a symbol | | provider_is_a_class | Provider is a class | + + @client @api + Scenario: Chef-client properly handles providers that invoke resources in their action definitions + Given a validated node + And it includes the recipe 'lwrp::provider_invokes_resource' + When I run the chef-client + Then the run should exit '0' + And a file named 'lwrp_touch_file.txt' should exist + |