https://github.com/pvdb/cucumber-pride
Port of minitest/pride to Cucumber
https://github.com/pvdb/cucumber-pride
Last synced: 6 months ago
JSON representation
Port of minitest/pride to Cucumber
- Host: GitHub
- URL: https://github.com/pvdb/cucumber-pride
- Owner: pvdb
- License: mit
- Created: 2012-04-11T21:22:21.000Z (over 14 years ago)
- Default Branch: master
- Last Pushed: 2012-04-12T01:03:59.000Z (over 14 years ago)
- Last Synced: 2025-11-30T20:05:22.278Z (8 months ago)
- Homepage:
- Size: 88.9 KB
- Stars: 1
- Watchers: 1
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# cucumber-pride
Take pride in your test output!
Mimics the functionality of `minitest/pride` for Cucumber, in much the same way that `ferrous26/rspec-pride` does for RSpec2.
## How to use cucumber-pride
To use cucumber-pride, you need to call `cucumber` kind of like this:
cucumber --format Cucumber::Pride::Formatter
Or put those options in your `config/cucumber.yml` file.
## Installation
Add this line to your application's Gemfile:
gem 'cucumber-pride'
And then execute:
$ bundle
Or install it yourself as:
$ gem install cucumber-pride
## Tests
The tests are a lie! They don't test cucumber-pride directly, they just produce enough output so that you can visually verify that everything is working. This was much faster than writing actual tests and works just as well in this case.
## Usage
TODO: Write usage instructions here
## Acknowledgements
* Main inspiration, and a fair amount of code, comes from the brilliant [`rspec-pride`](https://github.com/ferrous26/rspec-pride/) gem by [Mark Rade (ferrous26)](https://github.com/ferrous26).
## Contributing
1. Fork it
2. Create your feature branch (`git checkout -b my-new-feature`)
3. Commit your changes (`git commit -am 'Added some feature'`)
4. Push to the branch (`git push origin my-new-feature`)
5. Create new Pull Request
## Copyright
Copyright (c) 2012 Peter Vandenberk. See LICENSE.txt for further details.