As configured in my dotfiles.
start new:
tmux
start new with session name:
#!/usr/bin/env bash | |
# | |
# Install latest ruby from brightbox with gems | |
# | |
# tested on precise version, and brightbox ruby-1.9.1 package ready for: | |
# precise(12.04) | |
# | |
# run this script on your ubuntu ~> | |
# `https://gist.githubusercontent.com/RunsFor/7af723f4dea1b73cfce9/raw | sudo bash` | |
# |
As configured in my dotfiles.
start new:
tmux
start new with session name:
I just had to set up Jenkins to use GitHub. My notes (to myself, mostly):
For setting up Jenkins to build GitHub projects. This assumes some ability to manage Jenkins, use the command line, set up a utility LDAP account, etc. Please share or improve this Gist as needed.
its
isn't core to RSpec. One the of the focuses of RSpec is on the documentation aspects of tests. Unfortunately, its
often leads to documentation output that is essentially lies. Consider this spec:
User = Struct.new(:name, :email)
describe User do
subject { User.new("bob") }
its(:name) { should == "bob" }
end
=Navigating= | |
visit('/projects') | |
visit(post_comments_path(post)) | |
=Clicking links and buttons= | |
click_link('id-of-link') | |
click_link('Link Text') | |
click_button('Save') | |
click('Link Text') # Click either a link or a button | |
click('Button Value') |