How I Roll - A Cucumber/git workflow

How I Roll: A Cucumber/git

WorkflowMatt Buck, Capital Thought

Capital Thought

I work for

We make

Agenda

• Creating topic branches in git

• Outside-In model of Rails development

• Merging topic branches

• BONUS ROUND: Getting non-technical stakeholders involved

$ issue list 3. Administrators should be able to manage Users 4. Access should be restricted by Role 6. Users should be able to edit account settings 7. Administrators should be able to import Contacts 13. Authors should be able to manage Posts 14. Authors should be able to register

$ git checkout -b 13_authors_manage_posts

Outside-in Rails development• Write a scenario

• Execute the scenario

• Write a step definition

• red/green/refactor View

• red/green/refactor Controller

• ensure the proper instance variables are assigned

• red/green/refactor Models

• ensure they provide methods needed by View and Controller

• red/green/refactor Model

Feature: author manages posts As an author I want to be able to manage the posts on my blog So that my audience can read my content

features/env/paths.rb

when /the create post page for (.*)$/ author = Author.find_by_name($1) new_author_post_path(author)

spec/views/posts/new.html.haml_spec.rb

describe "/posts/new.html.haml" do before(:each) do assigns[:post] = Factory.build :post @author = Factory.create :author assigns[:author] = @author end

it "should render new form" do render "/events/new.html.haml" response.should have_tag("form[action=?][method=post]", author_posts_path(@author)) endend

app/views/posts/new.html.haml

%h1 New post

- form_for([@author, @post]) do |f| = render :partial => "form", :locals => {:f => f} %p= f.submit "Add Post"

spec/controllers/posts_controller_spec.rb

describe "responding to GET new" do def do_get(params = {}) stub_author get :new, {:author_id => @author} end it "should expose a new post as @post" do post = Factory.build(:post) Post.should_receive(:new).and_return(post) do_get assigns[:post].should equal(post) endend

app/controllers/posts_controller.rb

def new @post = Post.new(params[:post])

respond_to do |format| format.html # new.html.erb format.xml { render :xml => @post } endend

features/env/paths.rb

when /the (create|show) post page for (.*)$/ author = Author.find_by_name($2)â€šÃ„Â® case $1 when /create/ new_author_post_path(author) when /show/ autho_post_path(author)

spec/controllers/posts_controller_spec.rb

it "should redirect to the created post" do Post.stub!(:new).and_return(@new_post) post :create, :post => {} response.should redirect_to(author_post_url(@author, @new_post))end

app/controllers/posts_controller.rb

# POST /posts# POST /posts.xmldef create @post = @author.posts.new(params[:post])

respond_to do |format| if @post.save flash[:notice] = 'Post was successfully created.' redirect_to author_post_url(@author, @post) else render :action => "new" end endend

Fast forward...

spec/views/posts/show.html.haml_spec.rb

describe "/posts/show.html.haml" do before(:each) do @post = Factory.create :post @author = Factory.create :author assigns[:author] = @author assigns[:post] = @post @post.stub!(:total_length).and_return(24) end

it "should display the length of the post in characters" do render "/events/show.html.haml" response.should have_tag("span#length", :text => 24) endend

app/views/posts/new.html.haml

%h1= @post.title

%span#length= @post.total_length

spec/models/post_spec.rb it "should return the length of the body and title in characters" do post = Post.create :title => "Title", :body => "Body" post.total_length.should == 9end

spec/models/post.rb def total_length title.size + body.sizeend

$ git checkout master$ git merge --squash 13_authors_manage_posts$ git commit -m “Implemented <...> Closes #13”

$ git checkout master$ git merge 13_authors_manage_posts

Bonus Round

How do we get non-technical

stakeholders involved in the story creation

process?

Credits, etc.

• Cucumber roll image: http://www.flickr.com/photos/stuart_spivack/464718611/

• Github Issues CLI: http://github.com/jsmits/github-cli/tree/master

• The RSpec Book: http://www.pragprog.com/titles/achbd/the-rspec-book

How I Roll - A Cucumber/git workflow

Technology

Introducing Git to your FTP workflow

Ultimate Git Workflow - Seoul 2015

Git & GitHub Workflow...2016/09/23 · Another Git/GitHub Workflow You have write permission ⇒ you can merge the PR This case is easy: No conflicts (you didn’t change your fork)

Personal git workflow, for everyone!

Git workflow step by step

Visual Studio and the git workflow

Pragmatic Git workflow

IMPRESSIONIST...GIT TUTORIAL WORKFLOW Starting Navigate to the directory you want to work in and run $ git clone git@gitlab.cs.washington.edu:cse457-17au-impressionist/YOUR_RE PO.git

Community Build Service cbs.centos.org and Brian Stinson ... · Step 2 : Integration with git. Workflow: 1. user commit to git.centos.org 2. user submit a git url to build system

A Git Workflow Walkthrough

Git - laihaotao.melaihaotao.me/talk_slides/git.pdf · Gitflow Workflow 33. Forking Workflow 34. Resources A well maintained list of resources related to Git on GitHub, check it through

Git workflow and basic commands By: Anuj Sharma. Why git? Git is a distributed revision control system with an emphasis on speed, data integrity, and

The development workflow of git github for beginners

Git Workflow - GSI · Git Workflow Alexey Rybalchenko (GSI Darmstadt, FairRoot group) R3BRoot Development Workshop GSI Darmstadt, July 28, 2015 ... Potential merge conflicts have

Drupal's Development workflow with Git, Jenkins, Aegir and Chiliproject

CakeDC Git Workflow extension

Installing and Configuring VMware vRealize Orchestrator ... · With Git, you can manage workflow development across multiple vRealize Orchestrator instances. See Using Git with the

My Git workflow

Git and Git Workflow Models as Catalysts of Software Development

Anton Parkhomenko Boost your design workflow or git rebase for designers