Project

haiti

0.0
No commit activity in last 3 years
No release in over 3 years
haitijoshcheek/haitiHomepageDocumentationSource CodeBug TrackerWiki
Extraction of cucumber helpers for running binaries that I wind up writing ad-hoc for many projects. It is minimal which lowers the barrier for entry, making it easy to understand/extend.If you need something more powerful, there is Aruba.
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Popularity
Downloads
26,705
Stars
1
Forks
0
Watchers
3
 Releases
Current version
0.2.2
Total releases
8
First release
2013-05-26
Latest release
2015-05-20
 Development
Primary Language
Ruby
Licenses
WTFPL
Average date of last 50 commits
2013-12-09
Reverse Dependencies
5

 Dependencies

Runtime

cucumber
< 3.0, >= 1.0
rspec
~> 3.0
 Project Readme

Build Status

Haiti

Aruba provides Cucumber helpers for command line programs, but it's way more sophisticated than I can understand, so I wind up reinventing that wheel in miniature for a lot of projects. This is just an extraction of that. It aims to be simple and easy to understand/extend.

It's barely featured, currently the only features are what I extracted from SeeingIsBelieving's test suite. I'll add more to it as I need them, or you're welcome to. Its testing is entirely in cucumber at the moment, and there are no negative tests to assert that things don't work, so if anyone winds up working on it, I wouldn't mind that.

To run tests

cd test
bundle
bundle exec cucumber

Todo

For my own sanity

  • Stick all this shit on a @haiti ivar rather than littering it all over self... I don't even know what self is in this case.

These would actually be useful right now

  • Some way to say that I run it and it succeeds (i.e. not so much effort to print stdout on failures)
  • All existing defs can take single or double quotes
  • Failures on stdout also display stderr
  • Step def for does not include

These should just generally be done

  • Add tests showing that curlies get interpreted where expected
  • Add tests proving that bin gets stuck in the path
  • Add tests for negative assertions (currently if all step defs were empty, this would pass the suite)

Things that would be nice, but probably won't ever happen, b/c honestly, how often am I really going to touch this lib?

  • all step defs work with single or double quotes
  • multiple bin directories
  • don't fucking pollute the World (currently this is how I get eval_curlies in there)
  • assertions about the existence and contents of files
  • a "given I'm in a clean directory" which wipes out the proving grounds

License

       DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
                   Version 2, December 2004

Copyright (C) 2013 Josh Cheek <josh.cheek@gmail.com>

Everyone is permitted to copy and distribute verbatim or modified
copies of this license document, and changing it is allowed as long
as the name is changed.

           DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
  TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

 0. You just DO WHAT THE FUCK YOU WANT TO.