v9.3.9 (2024-10-31)
v9.3.8 (2024-07-16)
- Prevent logger 1.6 from being used. #11 (tpowell-progress)
v9.3.7 (2024-02-07)
- Pin rspec-expectations due to private API change #6 (joshuariojas)
v9.3.6 (2023-05-08)
- Restore rubygem reference #3 (vkarve-chef)
- Restore gemspec file name #4 (vkarve-chef)
v9.3.4 (2023-03-02)
v9.3.4 (2022-06-14)
- Remove space from EOF #2 (sanjain-progress)
- Fix a failure running chefspec with Policyfiles
- Remove a hack in the Hash class that worked around issues in Windows previously
- Fix ChefSpec does not automatically install cookbooks from chef server when using Policyfile.rb
- Remove Travis CI config
- Resolved an error that could cause failures with some resources
- Add support for resources that include a
description
value in the action - Require Ruby 2.5+ and Chef Infra Client 15+
- Add support for Ruby 3
- Improve performance by only requiring external libraries if they are not already loaded
- Expand testing to additional releases of Chef Infra Client
- Updated
stubs_for_resource
stubbing for the newafter_resource
state in Chef Infra Client 16. - Added support for Ohai segments in cookbooks
- Resolved warnings when running on Ruby 2.7+
- Added a new
include_any_recipe
matcher which allows you to write ChefSpecs that ensure a cookbook does not include recipes. Thanks @jasonwbarnett - Fixed stubbing of Chef::Provider when using Poise's resource_provider_mixin. Thanks @Annih
- Switched require statements to require_relative to speed up requiring libraries in ChefSpec
- The fauxhai dependency has been switched to the fauxhai-ng. Fauxhai-ng is the original source of the fauxhai project in the chefspec GitHub org, but with a new name. This is considered a major update as it forces users to upgrade to use fauxhai-ng >= 7.5 where as the previous ChefSpec release allowed for fauxhai >= 6.11.
- Added back the ChefSpec report templates until the time that we fully remove the report feature.
- ChefSpec now requires Ruby 2.4+ and Chef 14+. Keep in mind that you can still test cookbooks designed for older versions of Chef Infra Client, but you'll need a somewhat modern chef gem to run ChefSpec.
- ChefSpec now depends on the new chef-cli gem, which provides Chef Policyfiles functionality. This means you can now use ChefSpec to test Policyfiles without needing to run those tests from within ChefDK or Chef Workstation. Gem install chefspec!
- Require Ruby 2.3+, Chef 13+, and Fauxhai 6.11+
- The majority of examples have been updated for the new ChefSpec 7.3+ format
- Properly loaded mixlib/shellout before trying to stub commands to prevent some failures
- Added a new
policyfile_path
configuration option for specifying the path to the PolicyFile
- Add back the spec files to the gem package for testing within Chef-DK
- Slimmed the size of the gem install down by not shipping test / development or example files in the gem artifact. These will remain in the repo for reference and testing.
- Updated the homepage in the Gemspec to be the Github repo
- Improved the stubbing documentation in the readme
- Improve runner construction code
- Make options to receive_shell_out work a bit better.
- Add additional hooks for customizing the runner creation process.
- Major syntax overhaul and update. Check out the README for examples of the updated syntax. The older syntax is still present and will be supported at least until ChefSpec 8.0, but documentation has been moved to README_old.
- Updated an example and test for that example
- The fauxhai dependency is no longer constrained. This removes the need to release a new version of Chefspec each time a major release of Fauxhai is released. Previously Fauxhai was constraine to < 6. The current release is 6.1.0, which includes significant new platform data and dumps that are updated for Chef 14.
This release deprecated the spec coverage feature, which will be removed in a future release. In general this feature leads to users writing unnecessary and generally useless specs in an attempt to reach 100% spec coverage. ChefSpec is useful for testing the parts of your cookbook that include logic, but if a particular resource has no logic behind it, then there's little value in testing. We shouldn't provide a mechanism that encourages writing unnecessary specs that give a false assurance test coverage.
- Better support for matching action :nothing in resources
-
Resource matchers are now generated automatically. What does this mean for you? A lot:
- You won't have to worry about older releases of ChefSpec not knowing about new resources in chef-client.
- You won't have to define the matchers in your cookbook code, which also means you won't have issues if a community cookbook lacks matchers
-
Removed the usage of Cucumber for testing
-
Removed all test deps from the Gemspec
-
Added a warning about stubbing core Ruby methods and the issues that can cause
- Increased the chef gem dependency from 12.6+ to 12.14+. Since ChefSpec is consumed within ChefDK this actually has a minor impact on end users who generally consume Chefspec via ChefDK, which will bundle both compatible chef and chefspec releases.
- Fixed incompatibilities with Chef 13.
- Loosened the Fauxhai dependency to allow for the upcoming Fauxhai 5.0 release.
- Removed easy_install_package testing and examples as easy_install_package was removed in Chef 13. The actual matcher is still present for users with existing specs against Chef 12 cookbooks.
- Added additional testing and an example for LWRPs with use_inline_resources defined.
- Added testing against Chef 13 and Ruby 2.4.
- Removed code that supported Chef < 12.5.
- Correctly handle the block form of search() when using stubs
- Add support for alternative reporting output from Coverage.report!
- Loosen the Fauxhai dependency to allow Fauxhai 4.0 This deprecates a large number of Ohai mocks for end of life platforms. See https://github.com/chefspec/fauxhai/blob/master/PLATFORMS.md for the current list of platforms supported by Fauxhai
- SoloRunner defaults to use_policyfile == false now
- Add the ability to set the Chef Zero port range used by the ServerRunner
BREAKING CHANGES
ChefSpec now requires Ruby 2.2 or later.
IMPROVEMENTS
- Improve ServerRunner speed and reduce process hangs by using a single stand-alone chef-zero server.
- Add configuration value to dictate whether cookbooks are re-uploaded before every test context.
- Added matchers for dnf_package, msu_package, and cab_package
IMPROVEMENTS
- Support for in-memory or on-disk ChefZero Servers. See README for usage details.
UPDATES
- While Chef 12.0 - 12.5 are still supported, they are no longer being tested.
IMPROVEMENTS
-
Added all missing matchers for built-in chef-client resources
- osx_profile
- zypper_package
- systemd_unit
- openbsd_package
- launchd
- homebrew_package
- bff_package
BUG FIXES
- Fixed readme examples to properly specify the platform / platform version and to use a cache dir that will work on Windows
IMPROVEMENTS
- Added platform and versions to all examples to avoid deprecation warnings from Fauxhai
- Allow modifications to node object before converge
BUG FIXES
- Fix makecache matcher for yum_repository
BUG FIXES
- Add missing matchers for yum_repository
IMPROVEMENTS
- Add dsc_script matcher
- Add yum_repository matcher
- Resolve cookstyle warnings in example recipes and specs
- Mock out platforms in the example specs so they're easier to adopt
- Switch all example specs to SoloRunner as this is the preferred runner for Chef Server / Chef Zero users
BUG FIXES
- Fixes apt_update and apt_repository matchers to work
IMPROVEMENTS
- Require a minimum of Chef 12.0
- Add custom templating to Coverage Reporting. See readme for details
- Add matcher for apt_repository resource
- Add matcher for apt_update resource
- Add support for the :before notification
- Allow stubbing encrypted databags loaded with data_bag_item
- Add testing against Chef 12.8 - 12.3
BUG FIXES
- Update docs/examples to use node.normal instead of node.set, which has been deprecated
- Update user spec examples to specify the platform
- Update docs to clarify the Ruby 2.1 requirement
IMPROVEMENTS
- Support Chef Solo actually being local mode (per Chef RFC 31)
BUG FIXES
- Use the same Chef :file_cache_path in every ChefSpec converge to prevent large numbers of LWRP deprecation warnings
- Require Fauxhai ~3.2 to prevent ChefSpec spec failures
- Require Rake < 11.0 to prevent failures
IMPROVEMENTS
- Add support for adding
berkshelf_options
to the RSpec config - Add
chocolately_package
matchers - Support
do..end
style syntax in block expectations - Output a diff when multi-line resource parameters are unmatched
BUG FIXES
- Update tests to include better descriptions and feature names
- Add support for Policyfile workflow
IMPROVEMENTS
- Update Fauxhai dependency to 3.0 to bring in newly generated mocked Ohai data
BUG FIXES
- Documentation improvements (using regex in stubbed commands, chef 12+ custom matcher gotchas)
- Spec suite improvements (dsc resource specs, platform specific configurations)
- Chef 12+ platform specific resource loading related error
IMPROVEMENTS
- Support for policy files
BUG FIXES:
- Improved documentation
- Use TemplateContext's
_extend_modules
for passing on template helper modules to nested partial templates - Only exit if the status is a failure [GH-565]
- Fix load order on Windows when using the
rights
attributes - Improve testing matrix and remove deprecated Chef versions
- Suppress chef_gem compile_time warnings
- Fix exceptions on converge for Chef 12.1.0 masking
- Update Librarian
Cheffile
site URL to supermarket.chef.io - Filter Windows and Unix paths for test coverage report with Berkshelf
IMPROVEMENTS:
- Added possibility to specify file_cache_path globally
- Added new capabilities for reboot resource
- Use
Chef::Resource#declared_type
first if available (Chef >= 12), otherwise fall back toChef::Resource#resource_name
(Chef <= 11) - Extend render_file to yield the content as a block
- Add windows_service resource
BUG FIXES:
- Updated README grep examples
- Fix various typographical errors
- Improved error message when using a deprecated resource matcher
IMPROVEMENTS:
- Add support for Chef 12
- Added support for environments in Chef Solo
- Fix location definition for caching
- Allow passing
Chef::Config[:file_cache_path]
from outside - Update support for Chef 12
BUG FIXES:
- Fix total fail on my part with deprecations and add test coverage
- Do not validate cookbooks on upload (speed)
BUG FIXES:
- Bump the minimum required version of Chef to 11.14
- Filter resources that have no source line in the coverage report - this is related to a bug in Chef where, when cloning a resource, both the clone and the original resource lose their metadata
IMPROVEMENTS:
- Allow multiple instances of a Chef Server instance
- Separate ChefSpec::Runner into
ChefSpec::SoloRunner
andChefSpec::ServerRunner
- Preliminary support for Chef 12 alpha (not 100% complete)
- Add
SoloRunner
andServerRunner
.converge
methods for quickly converging if you do not need to customize the runner object - Create isolated Chef Server instances on a per-test or per-suite basis
- Deprecate
ChefSpec::Runner.define_runner_method
in favor ofChefSpec.define_matcher
- Deprecate
ChefSpec::Runner.new
- you should specify if you want aSoloRunner
orServerRunner
- Updated documentation
BREAKING CHANGES:
- Due to the new
ServerRunner
, theChefSpec::Server
singleton object has been deprecated. As much as I would like to provide a backwards-compatible interface, there is no way to do so (as the code now supports multiple Chef Server instances). Sorry :(. - Remove old deprecations - this is not really a breaking change, but the v2.0.0 deprecations have been removed in favor of new ones
BUG FIXES:
- Fix a regression caused by a new version of Chef Zero in single_org mode
IMPROVEMENTS:
- Test against Chef 11.14.0 in the Travis matrix
BUG FIXES:
- Fix class comparisons
- Update ChefZero API to work again
- Use proper cookbook in the template_finder
- Fix Ruby deprecations
- Various documentation updates
BREAKING CHANGES:
- Upgraded to RSpec 3! RSpec 3 brings many new API changes and syntaxes
- Bump minimum required Chef version to 11.12! Without this change, Chef Zero will blow up
BUG FIXES:
- Gracefully fail if a resource does not report it's source line in the reporter
- Pull the correct cookbook folder from the stack on Windows (88bfc6)
- Cover resources in render_file matchers for reporting
- Cover resources in link_to matchers for reporting
- Cover resources in do_nothing matchers for reporting
- Fix memory leak in LWRP Resource classes
- Restore the original
cookbook_path
when using librarian-chef - Documentation fixes
- Disable lazy loading of cached resources
- Fix a bug that will happen in later Chef versions because FreeBSD is evil (13ff143)
- Do not pass local file paths to
preferred_filename_on_disk_location
FEATURES:
- Add runner methods for all the bash, csh, perl, etc resources
- Upgraded fauxhai dependency and specs
- Upgrade Chef Zero for multi-org support
IMPROVEMENTS:
- Improved documentation around the
define_runner_method
method - Update badges to be all SVG
- Test on Ruby 2.1
- Use a randomly assigned port for Chef Zero
- Remove references to
.stub
from documentation
BUG FIXES:
- Restore Berkshelf 2 support (missing edge case)
- Add negative failure message for subscribes/notifies matchers
FEATURES:
- Added
do_nothing
matcher for asserting a resource performed no actions
IMPROVEMENTS:
- Increased spec coverage for matchers
- Support RSpec matchers in
with_content
BUG FIXES:
- Various typographical fixes in the README
- Remove unused JSON report
- Restore coverage reporting for Berkshelf 2 users
- Minor formatting changes for errors
IMPROVEMENTS:
- Remove dependency on i18n and use native ERB instead
- Vendor Berkshelf/Librarian in a "cookbooks" directory so we can shorten the pathname during coverage reporting
BUG FIXES:
- Update documentation for setting
automatic
attributes - Update documentation for stubbing data_bags
- Use a non-internal RSpec variable name for expecting exceptions
- Fix the airity of the
stub_node
method
IMPROVEMENTS:
- Better filtering protocols for resource coverage
BUG FIXES:
- Fix coverage calculation when there are no resources in the collection
- Fix misplaced quote in matcher output
- Include all files in generated gem
- Ensure compatibility with Chef HEAD
IMPROVEMENTS:
- Test Ruby 2.1 on Travis
- Miscellaneous README typos
- Add
subscribe_to
matchers - Add documentation for the
with
matcher - Add support for passing a
node
object directly to the servercreate_node
method
BUG FIXES:
- Correctly expand the node's run_list in server mode
- Actually package i18n translations with the cookbook
IMPROVEMENTS:
- Document setting a node's role
- Add examples and features for
stub_node
BUG FIXES:
- Fix broken deprecations module
- Update a broken test (@bknowles)
IMPROVEMENTS:
- Better gem description on GitHub and Rubygems
- Helper support for template rendering (Chef 11.4+) (@geraud)
BUG FIXES:
- Require i18n 0.6.9 or higher (but less than 1.0.0) (#289)
BUG FIXES:
- Handle duplicate resources in the coverage reporter
BUG FIXES:
- Only remove existing LWRP resources and providers when a new one is encountered (@student)
- Attempt to coerce dashes to underscores in LWRPs
- Various documentation fixes and typos
IMPROVEMENTS:
- Don't include
deprecations
module by default - Add examples for stubbing commands across recipes
- Yield a block after cookbooks are compiled but before they are converged (@rteabeault)
- Add IRC Channel #chefspec
- Raise a nice error when
cookbook_path
cannot be determined (@ryotarai)
FEATURES:
- Add support for Librarian (@mlafeldt)
- Add Cacher module for caching runner results (@sethvargo & @DracoAter)
- Add Chef Zero (server) mode (@sethvargo)
- Add basic resource reporting (Chef recipe code coverage) (@sethvargo)
- Use i18n (internationalization) (@sethvargo)
BUG FIXES:
- Update links to point at new repository location
- Deleted relish docs to remove confusion
- Bump fauxhai dependency to 2.0 (removing the HTTParty transitive dependency)
- Convert resource names with dashes to underscores when stepping into them
IMPROVEMENTS:
- Added a "what people are saying" section to the README - if you have something cool to say about ChefSpec, let me know!
- Add a link to
knife-spec
- Test against Chef 11.8
- New matcher:
have_state_attrs
for testing custom LWRP state attributes - Run tests in a sandboxed parent instead of tmp (makes Travis happier)
BUG FIXES:
- Fix an issue where LWRPs were not properly stepped into when
use_inline_resources
was specified (#244) - Coerce
render_file
@expected_content
to a string before asserting if content is included (#243)
IMPROVEMENTS:
Breaking:
-
Dropped support for Chef 9 & 10
-
Renamed
ChefSpec::ChefRunner
toChefSpec::Runner
to better reflect what happens in Chef Core. UsingChefRunner
will throw deprecation errors for now and will be removed in a future release. -
Removed MiniTest Chef Handler examples/matchers
-
No longer load default cookbook paths:
- vendor/cookbooks
- test/cookbooks
- test/integration (test kitchen)
- spec/cookbooks
-
Resource matchers all follow the pattern "(action)_(resource_name)". ChefSpec will warn you of these deprecations in 3.0. They will be removed in 4.0. However, some resources cannot be automatically converted - these resources will raise a deprecation exception of
ChefSpec::NoConversionError
. The following matchers have changed:execute_command
=>run_execute
set_service_to_start_on_boot
=>enable_service
create_file_with_content
=>render_file
execute_(script)
=>run_(script)
execute_ruby_block
=>run_ruby_block
install_package_at_version
=>install_package().with(version: '')
*_python_pip
=> (removed - see "Packaging Custom LWRPs in the README")
-
Remove dependency on Erubis
-
Remove dependency on MiniTest Chef Handler
-
Remove development dependency on Cucumber
-
Remove development dependency on i18n
-
Remove development dependency on simplecov
-
Separate package matchers. In prior versions of ChefSpec, the
package
matcher would match on any kind of package and any kind of package action. However, some subclasses of the package resource do not support all actions. Each package provider now has it's own matcher with only the actions it supports. Prior specs that used the genericpackage
matcher will no longer match on subclasses - you must use the specific subclass matcher. -
Separate file/cookbook_file/template matchers. In prior versions of ChefSpec, the
file
matcher would match onfile
,cookbook_file
, andtemplate
. This is not ideal because it doesn't verify the correct message was sent. Now,file
,cookbook_file
, andtemplate
matchers will only match resources of that type. For generic file checking, please use the newrender_file
matcher. -
Guards are now evaluated by default. If a shell guard is executed, it must first be stubbed with the
stub_command
macro. -
Runner#resources
converted from an Array to a Hash. This is to ensure that all resource actions are added (when multiple calls to run_action exist (#201)). This also drastically improves resource lookup times. -
Resource#actions
is no longer maniuplated. Instead, a new methodResource#performed_actions
now keeps track of the actions taken on a resource (as well as the phase in which they were taken), preserving the original state of the resource.
FEATURES:
- Added a new
render_file
action to replacecreate_file_with_content
. This matcher will render the contents of any file to a string and then optionally compare the result if given awith
chainable. - All resources now accept a
with
chainable for matching specific resource attributes. - Windows attributes are now testable on non-Windows systems (like
inherits
) - Added
batch
resource matchers - Added
cookbook_file
resource matchers - Added
deploy
resource matchers - Added
erl_call
resource matchers - Added
git
resource matchers - Added
http_request
resource matchers - Added
ifconfig
resource matchers - Normalized
link
resource matchers - Added
log
resource matchers - Added
mdadm
resource matchers - Added
mount
resource matchers - Added
:immediate
and:delayed
notification matchers - Added
ohai
resource matchers - Added
powershell_script
matchers (Chef 11.6+) - Added
registry_key
matchers - Added
remote_directory
matchers - Added
route
matchers - Added
subversion
matchers - Added
stub_command
macro (formerly onChefSpec::ChefRunner
) for stubbbing the results of shell commands. Because shell commands are evaluated by default, ChefSpec will raise an exception when encountering a shell command that has not been stubbed. - Added
stub_search
macro for easily stubbingsearch
calls. Like shell commands, ChefSpec will raise an exception when encountering asearch
call that has not been stubbed. - Added
stub_data_bag
macro for easily stubbingdata_bag
calls. Like shell commands, ChefSpec will raise an exception when encountering adata_bag
call that has not been stubbed. - Added
stub_data_bag_item
macro for easily stubbingdata_bag_item
calls. Like shell commands, ChefSpec will raise an exception when encountering adata_bag_item
call that has not been stubbed. - Added
stub_node
helper for quickly generating a node object from Fauxhai data - Added
ChefSpec::Runner#apply
command to mimic the behavior ofchef-apply
(use with caution) - Share the
ChefSpec::Runner
object with the Node object - Add
chefspec/berkshelf
for easily integrating specs with Berkshelf (2 & 3) - Add
.at_compile_time
and.at_converge_time
matchers for asserting which phase of the Chef run a resource should be run
IMPROVEMENTS:
- Move to inline documentation (Yard)
- Implement InProcess Aruba testing for ultra-fast tests
- Create "examples" directory for testing and demonstration
- Unified all failure_messages_for_should
- Use
shared_examples
for easily testing defined custom matchers - Infer the
cookbook_path
from the calling spec - Directly set node attributes with Fauxhai (formerly this was an O(n) operation)
- Refactored ExpectExpectation to work without stubbing
- Use Chef's
resource_collection
to identify resources instead of our own custom proxy
BUG FIXES:
- Add missing second optional parameter to
Hash#respond_to?
monkey patch
FEATURES
- Improve error message when using a regular express
- Improve documentation for Python packages
Breaking:
- Remove support for REE (@andrewgross for the CI)
BUG FIXES:
- Better failure message for
create_remote_file
(@tmatilai) - Add
cookbook_file
as an accepted type to thecreate_file
matchers (@dafyddcrosby) - Ensure formatter is only registered once (@student)
- Signifant README updates (@phoolish)
- Fix
described_recipe
helper (S.R.Garcia) - Refactor Chef 10/11 template rendering (@sethvargo)
- Fix CI (@sethvargo)
- Match File actions as an array (@sethvargo)
FEATURES:
- Extend
ruby_block
matcher to accept regular expressions (@ssimeonov) - Add
create_remote_file_if_missing
matcher (@jimhopp) - Extend
execute
matcher to accept regular expressions (@eliaslevy) - Add ability to expect exceptions during a run (@student)
- Add regular expression support for resource names (@mapleoin)
- Add support for
python_pip
LWRP (@mapleoin)
BUG FIXES:
- Allow the user to override
cookbook_path
again
FEATURES:
- Added the ability to evaluate
only_if
andnot_if
conditional guards and support for stubbing shell guards (#142, #144). - New
described_recipe
anddescribed_cookbook
helpers to keep your specs DRY (#140). Thanks Andrey Chernih.
BUG FIXES:
- Ensure that Ohai plugin reloader works with ChefSpec (#141). Thanks Andrey Chernih.
FEATURES:
- Add support for partial files (@RanjibDey)
- Automatically check certain directories for cookbooks (@sethvargo)
FEATURES:
- Upgrade to newest version of fauxhai (@tmatilai)
- Make
find_resource
a public method (@adamhjk) - Add path support (from fauxhai) (@RanjibDey)
- Custom Chef formatter for ChefSpec (removes pesky output) (@sethvargo)
BUG FIXES:
- Remove pesky output from Chef 11
FEATURES:
- Add support for matching file content using Regular Expressions (@ketan)
- Add support for
ruby_block
matcher (Andrey Vorobiev) - Use Fauxhai for node attributes (see 4529c10)
- Moved
test
anddevelopment
into gemspec for transparency - Improve message logging and testing (@tmatilai)
- Chef 11 compatibility (still Chef 10 compatible)
- Accept and document new RSpec "expect" syntax
- Attribute matchers for various providers (@bjoernalbers)
- Add execute_{bash,csh,perl,python,ruby}_script matchers (@mlafeldt)
- Add group and user resource matchers (@gildegoma)
- Add support for
yum_package
(Justin Witrick) - Add ISSUES.md
- Add CONTRIBUTING.md
- Relax gemspec constraints (@juliandunn)
- Improve documentation and examples
BUG FIXES:
- Fix Rubygems/Bundler 2.0 compatibility issues
- Upgrade to newest RSpec
- Fix Chef 11 incompatibility
- Various documentation fixes
FEATURES:
- Support added for the
user
resource (#6). Thanks Ranjib Dey. - Support for making assertions about notifications added (#49). Thanks to Ranjib Dey.
- New
include_recipe
matcher added (#50). Thanks Ranjib Dey. - Support added for the Windows
env
resource (#51). Thanks Ranjib Dey. - Convenience methods for common resources added to
ChefRunner
(#51). Thanks Ranjib Dey. - Further resource convenience methods added (#60). Thanks to Ketan Padegaonkar.
- Support for the
:disable
action added to the service resource (#67). Thanks to Chris Lundquist. - Add a matcher to assert that a service is not running on boot (#58). Thanks to Ketan Padegaonkar.
- Support added for the
chef_gem
resource (#74). Thanks to Jim Hopp.
BUG FIXES:
- Avoid failure if template path is not writable (#48). Thanks to Augusto Becciu and Jim Hopp.
- Style fix for the README (#55). Thanks Greg Karékinian.
- Ensure notification assertions work where the resource name contains brackets (#57). Thanks Sean Nolen.
- Unit tests updated to explicitly specify attribute precedence as required from Chef 11 (#70). Thanks Mathias Lafeldt.
- Documentation added to the README for the
create_remote_file
matcher (#71). Thanks Mathias Lafeldt. - Clarify that
create_file_with_content
matches on partial content (#72). Thanks Mathias Lafeldt.
FEATURES:
- LWRP support added (#40). You can now make assertions about the resources created by a provider by telling chefspec to step into a provider implementation. Thanks to Augusto Becciu for implementing this feature.
- Updated for compatibility with Chef 10.14. Thanks Augusto Becciu.
BUG FIXES:
- Template paths are no longer hard-coded to live under
default
(#32). Thanks Augusto Becciu.
FEATURES:
- Cron resource support added (#33). Thanks Alexander Tamoykin.
- RSpec dependency bumped to 2.11 which has named subject support (#37). Thanks Doug Ireton.
BUG FIXES:
- Correctly infer the default
cookbook_path
on Windows (#38). Thanks Torben Knerr.
FEATURES:
- With the release of Chef 10.12.0 the Chef versioning scheme has changed to make use of the major version field. The constraint on chef is now optimistic. Thanks to Robert J. Berger of Runa.com for flagging this issue (#28).
FEATURES:
- Service matchers extended to add support for the
:nothing
and:enabled
actions. Thanks to Steve Lum (#20). - Added mock value for
node['languages']
to prevent failure when loading cookbooks that expect this attribute to have been populated by OHAI. Thanks to Jim Hopp (#23). - Matchers added for the
link
resource. Thanks to James Burgess (#25). - Matchers added for the
remote_file
resource. Thanks to Matt Pruitt (#26).
FEATURES:
-
Thanks to Chris Griego and Morgan Nelson for these improvements:
- Support both arrays and raw symbols for actions in the file content matcher (#14).
- Add support for cookbook_file resources (#14).
-
Support added for
gem_package
resources. Thanks to Jim Hopp from Lookout (#16).
BUG FIXES:
- Set the client_key to nil so that Chef::Search::Query.new doesn't raise (#14). Thanks Chris Griego and Morgan Nelson.
FEATURES:
- Ruby 1.9.3 is now supported.
- The
create_file_with_content
matcher now matches on partial content (#13). This is an API behaviour change but sufficiently minor and unlikely to break existing specs that I'm not bumping the major version. Thanks Chris Griego and Morgan Nelson from getaroom.
BUG FIXES:
- Fixed a bug in the
install_package_at_version
matcher where it would error if the package action was not explicitly specified (#13). Thanks Chris Griego and Morgan Nelson from getaroom.
FEATURES:
- Added new matcher
create_file_with_content
for verifying Cheftemplate
resource generated content. - Knife plugin added to generate placeholder examples.
BUG FIXES:
- Fixed typo in 0.2.0 botched release. Pro-tip: run your tests.
FEATURES:
- Significantly improved performance by not invoking OHAI.
- ChefRunner constructor now accepts a block to set node attributes.
- ChefRunner constructor now takes an options hash.
- Converge now returns a reference to the ChefRunner to support calling converge in a let block.
BUG FIXES:
- Removed LWRP redefinition warnings.
- Reset run_list between calls to converge.
- Readable to_s output for failed specs.
FEATURES:
- Support for Chef 0.1.x (#2)
- Support MRI 1.9.2 (#3)
BUG FIXES:
- Added specs.
BUG FIXES:
- Corrected gem dependencies.
Initial version.