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

Amaroo: /* References */

2011-10-30T15:55:12Z

References

← Older revision		Revision as of 15:55, 30 October 2011
Line 139:		Line 139:
	==References==		==References==
	<references/>		<references/>


	* 1. [http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/]
	* 2. [http://en.wikipedia.org/wiki/Model-View-Controller Model–view–controller]
	* 3. [http://guides.rubyonrails.org/action_controller_overview.html Action Controller Overview]
	* 4. [http://guides.rubyonrails.org/migrations.html Migrations]
	* 5. [http://ar.rubyonrails.org/classes/Fixtures.html Class Fixtures]
	* 6. [http://biodegradablegeek.com/2008/07/how-to-use-fixtures-to-populate-your-database-in-rails/ How to use fixtures to Populate your database in rails ]
	* 7. [http://guides.rubyonrails.org/testing.html A Guide to Testing Rails Applications]
	* 8. [http://en.wikipedia.org/wiki/Functional_testing Functional testing]
	* 9. [http://avdi.org/devblog/2010/12/21/object-oriented-programming-comes-to-rails/Object Oriented Programming Comes to Rails]
	* 10. [http://en.wikipedia.org/wiki/Integration_testing Integration Testing]
	* 11. [http://ruby.railstutorial.org/ruby-on-rails-tutorial-book Ruby on Rails Tutorial]

Amaroo: /* Integration Tests */

2011-10-30T15:54:25Z

Integration Tests

← Older revision		Revision as of 15:54, 30 October 2011
Line 115:		Line 115:

	===Integration Tests===		===Integration Tests===
	Integration testing is a testing technique in which various software modules are combined and tested as a group[http://en.wikipedia.org/wiki/Integration_testing]. Although each of the modules might function correctly, it is not necessary that they will function correctly as a group. In a rails project, integration tests are most useful to verify the interactions between controllers. Integration testing generally occurs in the latter part of the project testing life cycle. Unit and functional tests are written along with development. Once each component has been completed, its functionality tested in isolation, integration tests take precedence. In rails, a generator can create a integration test skeleton. In the image below some integration test for our rails application:		Integration testing is a testing technique in which various software modules are combined and tested as a group<ref>http://en.wikipedia.org/wiki/Integration_testing</ref>. Although each of the modules might function correctly, it is not necessary that they will function correctly as a group. In a rails project, integration tests are most useful to verify the interactions between controllers. Integration testing generally occurs in the latter part of the project testing life cycle. Unit and functional tests are written along with development. Once each component has been completed, its functionality tested in isolation, integration tests take precedence. In rails, a generator can create a integration test skeleton. In the image below some integration test for our rails application:

	[[File:Integration.png\|1000px]]		[[File:Integration.png\|1000px]]
Line 124:		Line 124:

	The green bar means that all the tests have passed. If any of the tests fails then you’ll get a red var.		The green bar means that all the tests have passed. If any of the tests fails then you’ll get a red var.



	===Performance Tests===		===Performance Tests===

Amaroo: /* Functional Tests */

2011-10-30T15:53:58Z

Functional Tests

← Older revision		Revision as of 15:53, 30 October 2011
Line 110:		Line 110:

	===Functional Tests===		===Functional Tests===
	Functional testing is a type of black-box testing which verifies the system behavior according to the specifications[http://en.wikipedia.org/wiki/Functional_testing]. In a rails projects, we apply functional tests on controllers to validate the workflow that they setup and verify if it results in the intended outcome. In rails, the controllers are primarily responsible for tasks such as routing of requests, handling user authentication, validating correctness of output produced etc. Of three entities in a rails project, there is tight coupling between the controller and the view [http://avdi.org/devblog/2010/12/21/object-oriented-programming-comes-to-rails/]. Hence, as a part of functional testing we also validate if the the content displayed by the view is of the correct format and content and the layout of the page is as expected.		Functional testing is a type of black-box testing which verifies the system behavior according to the specifications<ref>http://en.wikipedia.org/wiki/Functional_testing</ref>. In a rails projects, we apply functional tests on controllers to validate the workflow that they setup and verify if it results in the intended outcome. In rails, the controllers are primarily responsible for tasks such as routing of requests, handling user authentication, validating correctness of output produced etc. Of three entities in a rails project, there is tight coupling between the controller and the view <ref>http://avdi.org/devblog/2010/12/21/object-oriented-programming-comes-to-rails/</ref>. Hence, as a part of functional testing we also validate if the the content displayed by the view is of the correct format and content and the layout of the page is as expected.
	The image below shows some of the functional test written for the categories controller. As you can see, tests like "should create category" checks if the categories controller can function as per specifications i.e. if it can create a new category.		The image below shows some of the functional test written for the categories controller. As you can see, tests like "should create category" checks if the categories controller can function as per specifications i.e. if it can create a new category.
	[[File:Functional.png\|1000px]]		[[File:Functional.png\|1000px]]

Amaroo: /* Unit tests */

2011-10-30T15:53:24Z

Unit tests

← Older revision		Revision as of 15:53, 30 October 2011
Line 102:		Line 102:

	===Unit tests===		===Unit tests===
	Unit tests are used for testing models. When we generate a model using the scaffold it also generates a unit test script for the model in the tests directory[http://guides.rubyonrails.org/testing.html]. In unit tests we can use the data generated using fixtures. As we write code in model classes we must write corresponding unit tests.		Unit tests are used for testing models. When we generate a model using the scaffold it also generates a unit test script for the model in the tests directory<ref>http://guides.rubyonrails.org/testing.html</ref>. In unit tests we can use the data generated using fixtures. As we write code in model classes we must write corresponding unit tests.
	For example consider you want all the fields for Recipe to be present. It can be tested as shown below –		For example consider you want all the fields for Recipe to be present. It can be tested as shown below –

Amaroo: /* Fixtures */

2011-10-30T15:52:50Z

Fixtures

← Older revision		Revision as of 15:52, 30 October 2011
Line 70:		Line 70:
	==Testing==		==Testing==
	===Fixtures===		===Fixtures===
	Fixtures are used to provide our tests with data i.e. sample data[http://ar.rubyonrails.org/classes/Fixtures.html]. They come in three flavors:		Fixtures are used to provide our tests with data i.e. sample data<ref>http://ar.rubyonrails.org/classes/Fixtures.html</ref>. They come in three flavors:
	* YAML fixtures		* YAML fixtures
	* CSV fixtures		* CSV fixtures
Line 79:		Line 79:

	In the above fig. one is a name of fixture. It does not matter what name you use. The entries after one are the “column_name:value” for the record one.		In the above fig. one is a name of fixture. It does not matter what name you use. The entries after one are the “column_name:value” for the record one.
	You can use scaffold to generate the fixtures for you. But it’ll give just the basic features. If there are any relationships then you have to explicitly specify them. You can do it by adding just foreign key name and it’ll figure out from where to populate the foreign key[http://biodegradablegeek.com/2008/07/how-to-use-fixtures-to-populate-your-database-in-rails/]. For example if you have used scaffold to generate MVC components of categories and recipes then it’ll generate categories.yml and recipes.yml for you. But now you’ll need to add the relationships manually, as shown below		You can use scaffold to generate the fixtures for you. But it’ll give just the basic features. If there are any relationships then you have to explicitly specify them. You can do it by adding just foreign key name and it’ll figure out from where to populate the foreign key<ref>http://biodegradablegeek.com/2008/07/how-to-use-fixtures-to-populate-your-database-in-rails/</ref>. For example if you have used scaffold to generate MVC components of categories and recipes then it’ll generate categories.yml and recipes.yml for you. But now you’ll need to add the relationships manually, as shown below

	[[File:41.png\|1000px]]		[[File:41.png\|1000px]]

Amaroo: /* Migrations */

2011-10-30T15:51:39Z

Migrations

← Older revision		Revision as of 15:51, 30 October 2011
Line 60:		Line 60:
	* Migrations are ruby ways to alter the database in a structured and organized manner.		* Migrations are ruby ways to alter the database in a structured and organized manner.
	* Although, it is possible for a developer to write SQL statements and alter it, migrations make the changes noticeable to other developers as well.		* Although, it is possible for a developer to write SQL statements and alter it, migrations make the changes noticeable to other developers as well.
	* One of the major advantages of migrations is that they allow version control on the database schema [http://guides.rubyonrails.org/migrations.html].		* One of the major advantages of migrations is that they allow version control on the database schema <ref>http://guides.rubyonrails.org/migrations.html</ref>.
	* When you move between different versions of your code, Active Record will work out which migrations should be run. It will also update the db/schema.rb file to match the structure of your database at that version.		* When you move between different versions of your code, Active Record will work out which migrations should be run. It will also update the db/schema.rb file to match the structure of your database at that version.
	* Another advantage of migrations is that they allow database portability. Use migrations is similar to using an interface, using SQL is similar to using an implementation. Hence, using migrations can allow you to use SQLite3 for development and say MySQL in production. The migrations will transform you schema into the database specific construct, without having you worry about it.		* Another advantage of migrations is that they allow database portability. Use migrations is similar to using an interface, using SQL is similar to using an implementation. Hence, using migrations can allow you to use SQLite3 for development and say MySQL in production. The migrations will transform you schema into the database specific construct, without having you worry about it.

Amaroo: /* Model, View and Controller */

2011-10-30T15:50:53Z

Model, View and Controller

← Older revision		Revision as of 15:50, 30 October 2011
Line 15:		Line 15:
	'''Definition''': A controller accepts input from the user and instructs the rest of the framework to respond to it.		'''Definition''': A controller accepts input from the user and instructs the rest of the framework to respond to it.

	Typically, the user input is modeled as an event and the controller converts it to a user action, understandable by the model. Based on the input, it also decides which views to render. The controller is also responsible for a number of auxiliary services like session management, caching and helper modules[http://guides.rubyonrails.org/action_controller_overview.html]. Code for a controller can be found in the ''app/controllers/'' directory of a rails project.		Typically, the user input is modeled as an event and the controller converts it to a user action, understandable by the model. Based on the input, it also decides which views to render. The controller is also responsible for a number of auxiliary services like session management, caching and helper modules<ref>http://guides.rubyonrails.org/action_controller_overview.html</ref>. Code for a controller can be found in the ''app/controllers/'' directory of a rails project.

	==A Rails Project==		==A Rails Project==

Amaroo: /* References */

2011-10-30T15:49:47Z

References

← Older revision		Revision as of 15:49, 30 October 2011
Line 140:		Line 140:

	==References==		==References==
			<references/>


	* 1. [http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/]		* 1. [http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/]
	* 2. [http://en.wikipedia.org/wiki/Model-View-Controller Model–view–controller]		* 2. [http://en.wikipedia.org/wiki/Model-View-Controller Model–view–controller]

Amaroo: /* References */

2011-10-30T15:48:14Z

References

← Older revision		Revision as of 15:48, 30 October 2011
Line 140:		Line 140:

	==References==		==References==
	* 1. [http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/ ~~Intermediate Rails: Understanding Models, Views and Controllers~~]		* 1. [http://betterexplained.com/articles/intermediate-rails-understanding-models-views-and-controllers/]
	* 2. [http://en.wikipedia.org/wiki/Model-View-Controller Model–view–controller]		* 2. [http://en.wikipedia.org/wiki/Model-View-Controller Model–view–controller]
	* 3. [http://guides.rubyonrails.org/action_controller_overview.html Action Controller Overview]		* 3. [http://guides.rubyonrails.org/action_controller_overview.html Action Controller Overview]

Amaroo: /* View */

2011-10-30T15:47:00Z

View

← Older revision		Revision as of 15:47, 30 October 2011
Line 8:		Line 8:

	===View===		===View===
	'''Definition''': A view renders the model in a form suitable for the user to comprehend[http://en.wikipedia.org/wiki/Model-View-Controller].		'''Definition''': A view renders the model in a form suitable for the user to comprehend <ref>http://en.wikipedia.org/wiki/Model-View-Controller</ref>.

	A view queries the model to obtain data and generates an interface to display it. Typically, the controller instructs a view to render itself. However, in some cases, the view is automatically notified by the model of changes in state. The view can render itself to the user in many ways, HTML, CSS, XML, Javascript, JSON are the common ones. The code for the views can be found in the ''app/views'' directory of a rails project.		A view queries the model to obtain data and generates an interface to display it. Typically, the controller instructs a view to render itself. However, in some cases, the view is automatically notified by the model of changes in state. The view can render itself to the user in many ways, HTML, CSS, XML, Javascript, JSON are the common ones. The code for the views can be found in the ''app/views'' directory of a rails project.