Skip to content

AdrianHwang/cucumber

This branch is 3554 commits behind cucumber/cucumber-ruby:main.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

2ccea1e · Feb 22, 2012
Dec 15, 2010
Jun 5, 2011
Feb 22, 2012
Jul 10, 2011
Feb 19, 2012
Nov 19, 2011
Feb 22, 2012
Feb 19, 2012
Oct 5, 2008
Nov 4, 2011
Jun 14, 2011
Jun 19, 2011
Sep 22, 2011
Nov 11, 2011
Feb 22, 2012
Feb 22, 2012
Jun 7, 2011
Jan 3, 2012
Jun 7, 2011
Feb 22, 2012
Nov 20, 2011

Repository files navigation

Build Status Dependency Status

The main website is at http://cukes.info/ The documentation is at https://wiki.github.com/cucumber/cucumber/

Note on Patches/Pull Requests

  • Fork the project.
  • Make your feature addition or bug fix.
  • Add tests for it. This is important so I don't break it in a future version unintentionally.
  • Commit, do not mess with Rakefile, version, or history. (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)
  • Send me a pull request. Bonus points for topic branches.

Running tests

gem install bundler
bundle install
git submodule update --init --recursive
rake

Release Process

Before you even attempt to do a release, make sure you can log into cukes.info and touch a file in /var/www/cucumber/api/ruby (see gem_tasks/yard.rake). You need to be able to do this in order to upload YARD docs as part of the release.

  • Bump the version number in lib/cucumber/platform.rb.
  • Make sure History.md is updated with the upcoming version number, and has entries for all fixes.
  • No need to add a History.md header at this point - this should be done when a new change is made, later.

Now release it

bundle update
rake
git commit -m "Release X.Y.Z"
rake release

Copyright

Copyright (c) 2008,2009,2010,2011 Aslak Hellesøy and Contributors. See LICENSE for details.

About

BDD that talks to domain experts first and code second

Resources

License

Stars

Watchers

Forks

Packages

No packages published