CSC/ECE 517 Fall 2011/ch4 4e cl - Revision history

Lchen10: /* Testing Returned Data */

2011-10-21T03:32:53Z

Testing Returned Data

← Older revision		Revision as of 03:32, 21 October 2011
Line 372:		Line 372:
	<pre>		<pre>
	test "should show task" do		test "should show task" do
	get :show, :id => @task_1.id		get :show, :id => @task_1.id
	assert_response :success		assert_response :success
	assert_equal @task_1.id, assigns(:task).id		assert_equal @task_1.id, assigns(:task).id
	assert_equal "task/show", session[:last_page]		assert_equal "task/show", session[:last_page]
	end		end
	</pre>		</pre>

Lchen10: /* Testing Controller Response */

2011-10-21T03:32:34Z

Testing Controller Response

← Older revision		Revision as of 03:32, 21 October 2011
Line 355:		Line 355:
	<pre>		<pre>
	test "successful index request" do		test "successful index request" do
	get :index		get :index
	assert_response :success		assert_response :success
	assert_template "index"		assert_template "index"
	end		end
	</pre>		</pre>

Lchen10: /* Starting a Controller Call */

2011-10-21T03:32:05Z

Starting a Controller Call

← Older revision		Revision as of 03:32, 21 October 2011
Line 335:		Line 335:
	If a session is getting a user ID and current project, and the flash is getting a notice:		If a session is getting a user ID and current project, and the flash is getting a notice:
	<pre>		<pre>
	get :show, {:id => @task.id.to_s}, {:user_id => "3", :current_project => @project.id.to_s}, {:notice => "flash test"}		get :show, {:id => @task.id.to_s},
			{:user_id => "3", :current_project => @project.id.to_s},
			{:notice => "flash test"}
	</pre>		</pre>
	The xhr( ) method simulates an Ajax call to the controller. The signature of the method is a little different; the first argument is the HTTP verb, the second is the controller method, and the remaining arguments match the order of the other HTTP mimic methods:		The xhr( ) method simulates an Ajax call to the controller. The signature of the method is a little different; the first argument is the HTTP verb, the second is the controller method, and the remaining arguments match the order of the other HTTP mimic methods:

	<pre>test "my ajax call" do		<pre>
	xhr :post, :create, :task => {:id => "3"}		test "my ajax call" do
			xhr :post, :create, :task => {:id => "3"}
	end		end
	</pre>		</pre>

Lchen10: /* Starting a Controller Call */

2011-10-21T03:31:22Z

Starting a Controller Call

← Older revision		Revision as of 03:31, 21 October 2011
Line 317:		Line 317:
	===Starting a Controller Call===		===Starting a Controller Call===
	The first step to initialize the functional testing is to simulate a controller call. Let us look a simple example:		The first step to initialize the functional testing is to simulate a controller call. Let us look a simple example:
	<pre>setup :generic_setup		<pre>
			setup :generic_setup
	def generic_setup		def generic_setup
	@task = Task.create		@task = Task.create
	login_as :admin		login_as :admin
	end		end

	test "should show a task" do		test "should show a task" do
	get :show, :id => @task.id.to_s		get :show, :id => @task.id.to_s
	assert_equal(@task.id, assigns(:task).id)		assert_equal(@task.id, assigns(:task).id)
	assert_response :success		assert_response :success
	assert_template :show		assert_template :show
	end		end
	</pre>		</pre>

Lchen10: /* What is Include by Functional Testing? */

2011-10-21T03:28:45Z

What is Include by Functional Testing?

← Older revision		Revision as of 03:28, 21 October 2011
Line 271:		Line 271:
	<ref>http://en.wikipedia.org/wiki/Functional_testing</ref>		<ref>http://en.wikipedia.org/wiki/Functional_testing</ref>
	In rails, controller testing depends on Rails-specific structures and methods. Controller testing aims to simulate various actions of a specific controller method and test whether the results are come out as expected. It is up to you to include or not include the assertions about the view output. The test of controller and views are included in the standard rails functional testing, but some of the third party add-ons provide the separate testing of views and partials.		In rails, controller testing depends on Rails-specific structures and methods. Controller testing aims to simulate various actions of a specific controller method and test whether the results are come out as expected. It is up to you to include or not include the assertions about the view output. The test of controller and views are included in the standard rails functional testing, but some of the third party add-ons provide the separate testing of views and partials.
	==What is ~~Include~~ by Functional Testing?==		==What is Included by Functional Testing?==
	All the features included by unit testing are still present in functional testing. What is more functional testing include the following unique features:		All the features included by unit testing are still present in functional testing. What is more functional testing include the following unique features:
	• In functional tests, you have access to the three instance variables: @controller(i.e.,the controller processing the request), @request and @response.		• In functional tests, you have access to the three instance variables: @controller(i.e.,the controller processing the request), @request and @response.

Lchen10: /* Unit Testing */

2011-10-21T03:28:12Z

Unit Testing

← Older revision		Revision as of 03:28, 21 October 2011
Line 44:		Line 44:
	Test fixture refers to the fixed state used as a baseline for running tests in software testing. The purpose of a test fixture is to ensure that there is a well known and fixed environment in which tests are run so that results are repeatable.<ref>http://en.wikipedia.org/wiki/Test_fixture</ref>For good tests, you’ll need to give some thought to setting up test data. In Rails, you can handle this by defining and customizing fixtures.		Test fixture refers to the fixed state used as a baseline for running tests in software testing. The purpose of a test fixture is to ensure that there is a well known and fixed environment in which tests are run so that results are repeatable.<ref>http://en.wikipedia.org/wiki/Test_fixture</ref>For good tests, you’ll need to give some thought to setting up test data. In Rails, you can handle this by defining and customizing fixtures.

	=Unit Testing=		=Unit Testing for Models=
	In Rails, unit tests aims to test the models of the application. We also called it as model tests. The code you write up for model tests are placed in the directory of test/unit. What the unit testing in Rails contains is listed as follow:		In Rails, unit tests aims to test the models of the application. We also called it as model tests. The code you write up for model tests are placed in the directory of test/unit. What the unit testing in Rails contains is listed as follow:
	• Load data from fixtures before each unit test		• Load data from fixtures before each unit test

Jli21: /* Basic Introduction */

2011-10-21T03:27:25Z

Basic Introduction

← Older revision		Revision as of 03:27, 21 October 2011
Line 31:		Line 31:
	<ref>http://guides.rubyonrails.org/testing.html</ref>		<ref>http://guides.rubyonrails.org/testing.html</ref>

	=~~Basic Introduction~~=		=Flow of Testing in Rails=
	The Three Environments is Production, Development and Test.		The Three Environments is Production, Development and Test.

Lchen10: /* Why need Software Test for Rails Application */

2011-10-21T03:24:05Z

Why need Software Test for Rails Application

← Older revision		Revision as of 03:24, 21 October 2011
Line 24:		Line 24:
	<ref>http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller</ref>		<ref>http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller</ref>

	=Why need Software Test for Rails Application=		=Why need Software Test for Rails Application?=
	Ruby on Rails, often shortened to Rails or RoR, is an open source web application framework for the Ruby programming language.		Ruby on Rails, often shortened to Rails or RoR, is an open source web application framework for the Ruby programming language.
	Rails makes it super easy to write your tests. It starts by producing skeleton test code in the background while you are creating your models and controllers.<ref> http://effectif.com/articles/testing-rails-with-rack-test</ref>		Rails makes it super easy to write your tests. It starts by producing skeleton test code in the background while you are creating your models and controllers.<ref> http://effectif.com/articles/testing-rails-with-rack-test</ref>

Lchen10: /* Example of Unit Testing */

2011-10-21T03:23:44Z

Example of Unit Testing

← Older revision		Revision as of 03:23, 21 October 2011
Line 222:		Line 222:
	\|}		\|}

	==~~Example~~ of Unit Testing==		==Examples of Unit Testing==
	We can write our unit testing cases now. We will use the live question website as the example.		We can write our unit testing cases now. We will use the live question website as the example.
	1 Ensure the username and password are not empty. Either one is missing, the test case will throw the error message.		1 Ensure the username and password are not empty. Either one is missing, the test case will throw the error message.

Lchen10: /* What is Ruby on Rails */

2011-10-21T03:23:18Z

What is Ruby on Rails

← Older revision		Revision as of 03:23, 21 October 2011
Line 13:		Line 13:
	Software testing, depending on the testing method employed, can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have been defined and the coding process has been completed. As such, the methodology of the test is governed by the software development methodology adopted.<ref>http://en.wikipedia.org/wiki/Software_testing</ref>		Software testing, depending on the testing method employed, can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have been defined and the coding process has been completed. As such, the methodology of the test is governed by the software development methodology adopted.<ref>http://en.wikipedia.org/wiki/Software_testing</ref>

	=What is Ruby on Rails=		=What is Ruby on Rails?=
	Ruby on Rails, also called Rails or RoR, is an open source web application framework for the Ruby programming language. It uses the Model-View-Controller(MVC) architecture pattern to organize the application programming. Ruby on Rails is separated into various packages, namely ActiveRecord, ActiveResource, ActionPack, ActiveSupport and ActionMailer. It is often installed using RubyGem, which is a package manager including with current versions of Ruby.<ref>http://rubyonrails.org/</ref>		Ruby on Rails, also called Rails or RoR, is an open source web application framework for the Ruby programming language. It uses the Model-View-Controller(MVC) architecture pattern to organize the application programming. Ruby on Rails is separated into various packages, namely ActiveRecord, ActiveResource, ActionPack, ActiveSupport and ActionMailer. It is often installed using RubyGem, which is a package manager including with current versions of Ruby.<ref>http://rubyonrails.org/</ref>