Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/mizzy/serverspec

RSpec tests for your servers configured by CFEngine, Puppet, Chef, Ansible, Itamae or anything else even by hand
https://github.com/mizzy/serverspec

Last synced: 3 days ago
JSON representation

RSpec tests for your servers configured by CFEngine, Puppet, Chef, Ansible, Itamae or anything else even by hand

Host: GitHub
URL: https://github.com/mizzy/serverspec
Owner: mizzy
License: mit
Created: 2013-03-24T04:15:25.000Z (almost 12 years ago)
Default Branch: master
Last Pushed: 2023-09-02T01:46:19.000Z (over 1 year ago)
Last Synced: 2025-01-03T02:11:51.330Z (10 days ago)
Language: Ruby
Homepage: http://serverspec.org/
Size: 1.99 MB
Stars: 2,508
Watchers: 112
Forks: 368
Open Issues: 2
Metadata Files:
- Readme: README.md
- License: LICENSE.txt

Awesome Lists containing this project

awesome-github-repos - mizzy/serverspec - RSpec tests for your servers configured by CFEngine, Puppet, Chef, Ansible, Itamae or anything else even by hand (Ruby)
awesome-repositories - mizzy/serverspec - RSpec tests for your servers configured by CFEngine, Puppet, Chef, Ansible, Itamae or anything else even by hand (Ruby)

README

        # Serverspec [![Gem Version](https://badge.fury.io/rb/serverspec.svg)](http://badge.fury.io/rb/serverspec) [![BuildStatus](https://secure.travis-ci.org/mizzy/serverspec.svg)](http://travis-ci.org/mizzy/serverspec) [![wercker status](https://app.wercker.com/status/526d1ff4df6eadaa793dca1affcaed35/s/ "wercker status")](https://app.wercker.com/project/bykey/526d1ff4df6eadaa793dca1affcaed35)

RSpec tests for your servers configured by Puppet, Chef or anything else

You can see the details of serverspec on [serverspec.org](http://serverspec.org/).

----

## Running the gem's tests

Use

```bundle exec rake```

(Using ```rspec``` alone will not work).

## Maintenance policy of Serverspec/Specinfra

* The person who found a bug should fix the bug by themself.

* If you find a bug and cannot fix it by yourself, send a pull request and attach test code to reproduce the bug, please.

* The person who want a new feature should implement it by themself.

* For above reasons, I accept pull requests only and disable issues.

* If you'd like to discuss about a new feature before implement it, make an empty commit and send [a WIP pull request](http://ben.straub.cc/2015/04/02/wip-pull-request/). But It is better that the WIP PR has some code than an empty commit.

----

## Contributing

1. Fork it

2. Create your feature branch (`git checkout -b my-new-feature`)

3. Commit your changes (`git commit -am 'Add some feature'`)

4. Push to the branch (`git push origin my-new-feature`)

5. Create new Pull Request