CSC/ECE 517 Spring 2016/Functional Tests for Questionnaire Controller - Revision history

Kpalani5 at 04:18, 23 March 2016

2016-03-23T04:18:57Z

← Older revision		Revision as of 04:18, 23 March 2016
Line 208:		Line 208:
	# https://github.com/expertiza/expertiza - Github link for original repository		# https://github.com/expertiza/expertiza - Github link for original repository
	# https://gist.github.com/zhengjia/428105 - Github link for Capybara		# https://gist.github.com/zhengjia/428105 - Github link for Capybara

	~~=== References ===~~

Kpalani5 at 04:06, 23 March 2016

2016-03-23T04:06:33Z

← Older revision		Revision as of 04:06, 23 March 2016
Line 3:		Line 3:
	=== Expertiza ===		=== Expertiza ===

	Expertiza is an open source peer review system developed by students and faculty at North Carolina State University. It allows students to form teams, submit assignments and review the work of their peers. In addition, it lets an instructor create new assignments, questionnaire for reviews and so on. It is built in [Ruby on Rails] platform.		Expertiza is an open source peer review system developed by students and faculty at North Carolina State University. It allows students to form teams, submit assignments and review the work of their peers. In addition, it lets an instructor create new assignments, questionnaire for reviews and so on. It is built in Ruby on Rails platform.

	=== Questionnaire System ===		=== Questionnaire System ===
Line 13:		Line 13:
	We have been given the task of creating functional tests for the questionnaire creation function as currently, there are none.		We have been given the task of creating functional tests for the questionnaire creation function as currently, there are none.

	In order to complete the task we will be using [Capybara] to write functional tests to		In order to complete the task we will be using Capybara to write functional tests to
	* Create new questionnaire.		* Create new questionnaire.
	* Create/Edit/Delete different types of questions.		* Create/Edit/Delete different types of questions.

Kpalani5: /* References */

2016-03-23T04:05:48Z

References

← Older revision		Revision as of 04:05, 23 March 2016
Line 208:		Line 208:
	# https://github.com/expertiza/expertiza - Github link for original repository		# https://github.com/expertiza/expertiza - Github link for original repository
	# https://gist.github.com/zhengjia/428105 - Github link for Capybara		# https://gist.github.com/zhengjia/428105 - Github link for Capybara

	~~=== References ===~~

	=== References ===		=== References ===

Kpalani5: /* External Links */

2016-03-23T04:05:37Z

External Links

← Older revision		Revision as of 04:05, 23 March 2016
Line 210:		Line 210:

	=== References ===		=== References ===

	~~=== External Links ===~~
	~~# https://github.com/kpalani5/expertiza/blob/master/spec/features/questionnaire_spec.rb - [[GitHub\|Github]] link for forked repository~~
	~~# https://github.com/expertiza/expertiza - Github link for original repository~~
	~~# https://gist.github.com/zhengjia/428105 - Github link for Capybara~~

	=== References ===		=== References ===

Kpalani5: /* Running the tests */

2016-03-23T04:05:19Z

Running the tests

← Older revision		Revision as of 04:05, 23 March 2016
Line 210:		Line 210:

	=== References ===		=== References ===

	~~=== Running the tests ===~~

	~~The tests can be run on the terminal using the command:~~
	~~rspec specfile.rb~~
	A seed value is used to randomize the order in which the tests are run. This is because all the tests are independent and so every test must be able to run at any time so that all the functionalities can be tested successfully.

	~~All the tests are run and depending on whether a test passes or fails, we can find out which of the functionalities are successfully implemented in the system.~~

	=== External Links ===		=== External Links ===

Kpalani5 at 04:04, 23 March 2016

2016-03-23T04:04:40Z

← Older revision		Revision as of 04:04, 23 March 2016
Line 1:		Line 1:

	= Functional Tests for Create Questionnaire Controller =		= Functional Tests for Create Questionnaire Controller =

	=== Expertiza~~<ref>{{Cite web\|url=http://wiki.expertiza.ncsu.edu/index.php/Main_Page\|title=Expertiza Wiki\|last=\|first=\|date=\|website=\|publisher=\|access-date=}}</ref>~~ ===		=== Expertiza ===

	[[Expertiza]] is an open source peer review system developed by students and faculty at [[North Carolina State University]]. It allows students to form teams, submit assignments and review the work of their peers. In addition, it lets an instructor create new assignments, questionnaire for reviews and so on. It is built in [[Ruby on Rails]] platform.		Expertiza is an open source peer review system developed by students and faculty at North Carolina State University. It allows students to form teams, submit assignments and review the work of their peers. In addition, it lets an instructor create new assignments, questionnaire for reviews and so on. It is built in [Ruby on Rails] platform.

	=== Questionnaire System ===		=== Questionnaire System ===
Line 14:		Line 13:
	We have been given the task of creating functional tests for the questionnaire creation function as currently, there are none.		We have been given the task of creating functional tests for the questionnaire creation function as currently, there are none.

	In order to complete the task we will be using [[~~Capybara (software)\|~~Capybara]]<ref>{{Cite web\|url=http://www.opinionatedprogrammer.com/2011/02/capybara-and-selenium-with-rspec-and-rails-3/\|title=Capybara with rspec and rails\|last=\|first=\|date=\|website=\|publisher=\|access-date=}}</ref> to write functional tests to		In order to complete the task we will be using [Capybara] to write functional tests to
	* Create new questionnaire.		* Create new questionnaire.
	* Create/Edit/Delete different types of questions.		* Create/Edit/Delete different types of questions.
Line 22:		Line 21:
	=== Functional Tests ===		=== Functional Tests ===

	~~[[Functional testing\|~~Functional tests]] are tests which ensure that the functionalities of a software system, as specified in a design or requirements document, are working as expected. Functional tests do not test a function or a method within a class but rather the functionality of the entire system. There are many frameworks that perform functional tests in ~~[[Ruby on Rails\|~~Ruby]]. One such framework is ~~[[Capybara (software)\|~~Capybara]].		Functional tests are tests which ensure that the functionalities of a software system, as specified in a design or requirements document, are working as expected. Functional tests do not test a function or a method within a class but rather the functionality of the entire system. There are many frameworks that perform functional tests in Ruby. One such framework is Capybara.

	=== Capybara ===		=== Capybara ===

	Capybara is framework, written in Ruby, that lets developers test their web application through simulations. It can be integrated with [[Selenium ~~(software)\|Selenium]]~~ and ~~[[WebKit\|~~Webkit]].~~<WIP>~~		Capybara is framework, written in Ruby, that lets developers test their web application through simulations. It can be integrated with Selenium and Webkit.

	=== Approach ===		=== Approach ===

Kpalani5: /* Functional Tests for Advice */

2016-03-23T04:01:00Z

Functional Tests for Advice

← Older revision		Revision as of 04:01, 23 March 2016
Line 211:		Line 211:

	=== References ===		=== References ===

	~~==== Functional Tests for Advice ====~~

	Only two types of questions in Expertiza have an advice associated with them - the Scale and Criterion type questions. The number of text areas in the advice page depend upon the number of Scale and Criterion type questions and each question has a number of advice text areas, one for each possible score which can be assigned for a particular question. This is obtained by using the ‘minimum’ and ‘maximum’ possible scores provided while creating the questionnaire.

	~~Two types of actions are possible for the advice - create and edit.<syntaxhighlight lang="ruby" line="1">~~
	~~it "is able to create a public review advice" do~~

	~~load_question 'Criterion'~~

	~~click_button "Edit/View advice"~~

	~~expect(page).to have_content('Edit an existing questionnaire')~~

	~~first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Advice 1")~~

	~~click_button "Save and redisplay advice"~~

	~~expect(page).to have_content('advice was successfully saved')~~

	~~expect(page).to have_content('Advice 1')~~

	~~end~~
	</syntaxhighlight>The above code snippet shows the way in which the advice is created. The button ‘Edit/View Advice’ is present for each questionnaire and the resulting page has all the text areas for the scale and criterion type questions in the questionnaire. There is also a heading which provides directions to the user that the questionnaire can be edited. This message can be used to test for the button’s functionality. Once the advice is created with some content, the presence of a message implying that the advice is saved and the presence of the saved content can test for the create functionality.<syntaxhighlight lang="ruby" line="1">
	~~first(:css, "textarea[id^='horizontal_'][id$='advice']").set("Advice edit")~~

	~~click_button "Save and redisplay advice"~~

	~~expect(page).to have_content('advice was successfully saved')~~

	~~expect(page).to have_content('Advice edit')~~


	~~</syntaxhighlight>The workflow for the edit functionality is similar to that of the create advice functionality.~~

	=== Running the tests ===		=== Running the tests ===

Kpalani5: /* Functional Tests for Question */

2016-03-23T04:00:10Z

Functional Tests for Question

@@ Line 89: / Line 89: @@
 There are ten types of questions in Expertiza - Criterion, Scale, Dropdown, Checkbox, TextArea, TextField, UploadFile, SectionHeader, TableHeader and ColumnHeader. The question type can be chosen while creating the question from a dropdown menu.
-Three different actions can be performed on each question - create, edit and delete.<syntaxhighlight lang="ruby" line="1">
+Three different actions can be performed on each question - create, edit and delete.
 it "is able to create a Criterion question" do
@@ Line 109: / Line 112: @@
-</syntaxhighlight>The above code snippet shows a creation workflow for the criterion type question. Once the add button is clicked, a new question is created and the link to remove the question appears along with it. Using this we can test whether, a new question has been created. Also, once the questionnaire is saved, a message appears on the Expertiza system confirming that the questions have been saved. By checking whether the message appears or not we can test whether the functionality has been implemented properly.<syntaxhighlight lang="ruby" line="1">
+</pre>
 it "is able to edit Criterion question" do
@@ Line 125: / Line 133: @@
-</syntaxhighlight>The above code snippet tests whether the question has been edited successfully or not. When a question has been edited with some content, the same content remains in the text field for the question. This can be used to test the successful editing of the question.<syntaxhighlight lang="ruby" line="1">
+</pre>
 it "is able to delete a Criterion question" do
@@ Line 135: / Line 147: @@
 end
-</syntaxhighlight>The created question can be deleted by using the link ‘Remove’ which has been specified along with it. Also, after successful deletion a message appears implying that the question can be deleted. Thus the presence or absence of this message can be used to test for the delete functionality.
+</pre>
 ==== Functional Tests for Advice ====

Kpalani5: /* Functional Tests for Questionnaire */

2016-03-23T03:56:51Z

Functional Tests for Questionnaire

← Older revision		Revision as of 03:56, 23 March 2016
Line 52:		Line 52:
	The test is to check whether a questionnaire can be created and the functionalities of the function are working.		The test is to check whether a questionnaire can be created and the functionalities of the function are working.

	<~~syntaxhighlight lang="ruby" line="1"~~>		<pre>

	describe "Create a public review questionnaire", :type => :controller do		describe "Create a public review questionnaire", :type => :controller do
Line 79:		Line 79:


	</~~syntaxhighlight~~>The above code is written in Capybara and it creates a public questionnaire of type review.		</pre>

			The above code is written in Capybara and it creates a public questionnaire of type review.

	There are three text fields and one dropdown box which have to be filled to create the questionnaire. The values are populated using the fill_in function for the text fields and the select function for the dropdown. Finally, the ‘create’ button is clicked. For the test to pass successfully, there has to be a new questionnaire named ‘Review 1’ which exists in the test database. Hence, we use the expect function to check for the presence of the questionnaire. If there is no such questionnaire, then the test has failed and the functionality of the function has not been implemented correctly.		There are three text fields and one dropdown box which have to be filled to create the questionnaire. The values are populated using the fill_in function for the text fields and the select function for the dropdown. Finally, the ‘create’ button is clicked. For the test to pass successfully, there has to be a new questionnaire named ‘Review 1’ which exists in the test database. Hence, we use the expect function to check for the presence of the questionnaire. If there is no such questionnaire, then the test has failed and the functionality of the function has not been implemented correctly.

Kpalani5: /* Functional Tests for Questionnaire */

2016-03-23T03:53:52Z

Functional Tests for Questionnaire

← Older revision		Revision as of 03:53, 23 March 2016
Line 53:		Line 53:

	<syntaxhighlight lang="ruby" line="1">		<syntaxhighlight lang="ruby" line="1">

	describe "Create a public review questionnaire", :type => :controller do		describe "Create a public review questionnaire", :type => :controller do