Let’s create out edit test.
To add edit test you have to modify your spec file.
require 'spec_helper'
describe "Tasks" do
before do
@task = Task.create :task => 'go to bed'
end
describe "GET /tasks" do
it "display some tasks" do
visit tasks_path
page.should have_content "go to bed"
end
it "creates a new page" do
visit tasks_path
fill_in 'Task', :with => 'go to work'
click_button "Create Task"
current_path.should == tasks_path
page.should have_content 'go to work'
save_and_open_page
end
end
describe "PUT /tasks" do
it "edits a task" do
visit tasks_path
click_link 'Edit'
current_path.should == edit_task_path(@task)
#save_and_open_page
#page.should have_content 'go to bed'
find_field('Task').value.should == 'go to bed'
fill_in 'Task', :with => 'updated task'
click_button "Update Task"
current_path.should == tasks_path
page.should have_content 'updated task'
end
end
end
To create model run this command.
rails g model Task task:string
Here model name is singular to execute active records which will execute the command like Tasks.all
This will create a migration file.
Migration:
Migrations are a convenient way for you to alter your database in a structured and organized manner. You could edit fragments of SQL by hand but you would then be responsible for telling other developers that they need to go and run them. You’d also have to keep track of which changes need to be run against the production machines next time you deploy.
Active Record tracks which migrations have already been run so all you have to do is update your source and run rake db:migrate. Active Record will work out which migrations should be run. It will also update your db/schema.rb file to match the structure of your database
In this post I will show you step by step instruction for Test-Driven Development (TDD) with Rails 3.
Here is my full project on github.
So what is Test-driven development or TDD ?
Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: first the developer writes a failing automated test case that defines a desired improvement or new function, then produces code to pass that test and finally refactors the new code to acceptable standards.
First you should have Ruby installed on your system. Please check my post to see if you don’t have Ruby on your system.
Create a Rails project
We will create a sample Task application for this tutorial.
By default, Rails uses Test Unit for its testing framework. But we will use something called rspec. So we will not install Rails default testing framework.
So lets create a Rails project by typing
rails new tasks -T -d mysql
To add edit test you have to modify your spec file.
require 'spec_helper'
describe "Tasks" do
before do
@task = Task.create :task => 'go to bed'
end
describe "GET /tasks" do
it "display some tasks" do
visit tasks_path
page.should have_content "go to bed"
end
it "creates a new page" do
visit tasks_path
fill_in 'Task', :with => 'go to work'
click_button "Create Task"
current_path.should == tasks_path
page.should have_content 'go to work'
save_and_open_page
end
end
describe "PUT /tasks" do
it "edits a task" do
visit tasks_path
click_link 'Edit'
current_path.should == edit_task_path(@task)
#save_and_open_page
#page.should have_content 'go to bed'
find_field('Task').value.should == 'go to bed'
fill_in 'Task', :with => 'updated task'
click_button "Update Task"
current_path.should == tasks_path
page.should have_content 'updated task'
end
end
end
To create model run this command.
rails g model Task task:string
Here model name is singular to execute active records which will execute the command like Tasks.all
This will create a migration file.
Migration:
Migrations are a convenient way for you to alter your database in a structured and organized manner. You could edit fragments of SQL by hand but you would then be responsible for telling other developers that they need to go and run them. You’d also have to keep track of which changes need to be run against the production machines next time you deploy.
Active Record tracks which migrations have already been run so all you have to do is update your source and run rake db:migrate. Active Record will work out which migrations should be run. It will also update your db/schema.rb file to match the structure of your database
In this post I will show you step by step instruction for Test-Driven Development (TDD) with Rails 3.
Here is my full project on github.
So what is Test-driven development or TDD ?
Test-driven development (TDD) is a software development process that relies on the repetition of a very short development cycle: first the developer writes a failing automated test case that defines a desired improvement or new function, then produces code to pass that test and finally refactors the new code to acceptable standards.
First you should have Ruby installed on your system. Please check my post to see if you don’t have Ruby on your system.
Create a Rails project
We will create a sample Task application for this tutorial.
By default, Rails uses Test Unit for its testing framework. But we will use something called rspec. So we will not install Rails default testing framework.
So lets create a Rails project by typing
rails new tasks -T -d mysql
Comments
Post a Comment