New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
namespace all functions #67
Conversation
08ff2d9
to
169c7ce
Compare
5540ff4
to
f1e4f81
Compare
f1e4f81
to
141ceca
Compare
Minor fixes/corrections were made that came up while writing examples but no major refactoring, even where it obviously should be done, was made. The intent is to establish a baseline before further changes are made. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes to newinstall.sh are fine. There is a huge amount of Ruby code here that I'm not going to review in detail. Did you auto generate this? I am worried that some of it seems to be testing things like "does the message contain the right string" which is not really what test frameworks are meant to test. For example the tests will need fixing when #68 merges (which will be before this merges because I'm waiting for Travis).
I'm afraid I keyed it all by hand. In many cases, there are no side effects to observe (that is, rspec-bash is able to observe) from a function to indicate which code path it has gone down other than output. It does end up being a bit more fragile for refactoring than a BDD ideal. However, I wouldn't want to try to write aruba or cucumber tests for the output of |
c0dff02
to
2a8a0fc
Compare
Repushed with the missing require statement. |
2a8a0fc
to
56c4ef2
Compare
The travis env is, amazingly, missing |
The current travis env does not include /usr/bin/true.
2581b53
to
ad8be1c
Compare
No description provided.