Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
Browse files

Removing cruft from features dir.

  • Loading branch information...
commit 7e978750144724dadca387182806ad43a91aa660 1 parent 0a8a1f4
@haus haus authored
View
16 features/modules/apt/basics.feature
@@ -1,16 +0,0 @@
-Feature: source_files
- In order to have effective package management
- As an intern
- I want source files to be in place
-
- Scenario: basic necessities for cucumber
- Given a node named "default"
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
-
- Scenario: basic necessities for Ubuntu
- Given a node of class "apt"
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
View
9 features/modules/apt/disable_keys.feature
@@ -1,9 +0,0 @@
-Feature: bar
- In order to win at life
- As a intern
- I want the apt module to be tested
-
- Scenario: basic test
- Given a node of class "apt"
- When I compile the catalog
- Then the node should have "disable_keys" set to "false"
View
19 features/modules/apt/file.feature
@@ -1,19 +0,0 @@
-Feature: source_files
- In order to have effective package management
- As an intern
- I want source files to be in place
-
- Scenario: get cucumber to find a file
- Given a node of class "apt"
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
-
- Scenario: get cucumber to find a file
- Given a node of class "apt"
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
- And there should be a file "sources.list" with "mode" of "0644"
- And there should be a directory "sources.list.d"
- And there should be a directory "sources.list.d" with "mode" of "0755"
View
48 features/modules/apt/force.feature
@@ -1,48 +0,0 @@
-Feature: apt force.pp
- In order to have effective package management
- The apt class needs to have a subclass params
- The force define should be able to force a specific version and release
-
- Scenario: Default instantiation with no parameters passed
- Given a node of class "apt"
-
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
-
- Scenario: Apt::Force define of name "testing" with no parameters
- Given a node named "default"
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
-
- And there should be a resource "Apt::Force[testing]"
- And the resource should have a "release" of "testing"
- And the resource should have "version" set to "false"
-
- Scenario: Apt::Force define of name "withVersion" with version parameter passed
- Given a node named "default"
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
-
- And there should be a resource "Apt::Force[withVersion]"
- And the resource should have a "release" of "testing"
- And the resource should have a "version" of "12"
-
- And there should be a resource "Exec[/usr/bin/aptitude -y -t testing install withVersion]"
- And the resource should have an "unless" that includes "12"
-
- Scenario: Apt::Force define of name "withRelease" with release parameter passed
- Given a node named "default"
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
-
- And there should be a resource "Apt::Force[withRelease]"
- And the resource should have a "release" of "stable"
- And the resource should have "version" set to "false"
-
- And there should be a resource "Exec[/usr/bin/aptitude -y -t stable install withRelease]"
-
- And print everything please
View
15 features/modules/apt/params.feature
@@ -1,15 +0,0 @@
-Feature: apt params.pp
- In order to have effective package management
- The apt class needs to have a subclass params
- The params subclass needs to define some defaults
-
- Scenario: Basic class instance with disable_keys set to rue
- Given a node of class "apt::params"
-
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
- And print everything please
-
- # How do this?
- # And there should be a resource "apt::params[root]"
View
13 features/modules/apt/paramterizedclasses.feature
@@ -1,13 +0,0 @@
-Feature: source_files
- In order to have effective package management
- As an intern
- I want source files to be in place
-
- Scenario: verify local vars
- Given a node of class "apt" with parameters:
- | name | value |
- | disable_keys | true |
- | always_apt_update | false |
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
View
18 features/modules/apt/private.feature
@@ -1,18 +0,0 @@
-Feature: source_files
- In order to have effective package management
- As an intern
- I want source files to be in place
-
- Scenario: compile catalog correctly
- Given a node named "testnode"
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
- And there should be a file "testing"
-
- Scenario: verify local vars
- Given a node named "testnode"
- When I compile the catalog
- Then compilation should succeed
- And all resource dependencies should resolve
- And print everything please
View
10 features/modules/apt/testcase.feature
@@ -1,10 +0,0 @@
-Feature: test case
-
- Scenario: test
- Given a node of class "test"
- When I compile the catalog
- Then all resource dependencies should resolve
- Then there should be a resource "File[foo]"
- And the state should be "present"
- And there should be a file "foo"
- And there should be a file "foo2"
Please sign in to comment.
Something went wrong with that request. Please try again.