E1850 Write unit tests for review response map - Revision history

Ssaluja at 14:11, 12 November 2018

2018-11-12T14:11:54Z

← Older revision		Revision as of 14:11, 12 November 2018
Line 308:		Line 308:
	</pre>		</pre>
	==Files affected==		==Files affected==
	review_response_map.rb		review_response_map.rb <br>
	review_response_map_spec.rb		review_response_map_spec.rb<br>
	spec_helper.rb		spec_helper.rb
	==Testing Framework==		==Testing Framework==

Ssaluja at 14:11, 12 November 2018

2018-11-12T14:11:06Z

Show changes

Ssaluja at 13:40, 12 November 2018

2018-11-12T13:40:38Z

@@ Line 16: / Line 16: @@
 .Achieve as high branch coverage as you can. We will use the mutant-rspec gem to measure test thoroughness and fault-finding capability of your tests.<br>
 ==Test Plan==
 ==Implementation==

Ssaluja at 02:15, 12 November 2018

2018-11-12T02:15:49Z

← Older revision		Revision as of 02:15, 12 November 2018
Line 7:		Line 7:
	It is an open source software created by North Carolina State University's students. It works on ruby on rails framework. This platform allows instructor to post notification about tests and assignments and also allows students to view grades, submit assignments, find teammates etc.<br>		It is an open source software created by North Carolina State University's students. It works on ruby on rails framework. This platform allows instructor to post notification about tests and assignments and also allows students to view grades, submit assignments, find teammates etc.<br>
	<p></p>		<p></p>
			==Background==
			Review_response_map.rb file is a newly added feature in Expertiza. The ReviewResponseMap class in the file is the sub class of ResponseMap class.The file review_response_map.rb deals with mapping of review's review to the feedback that reviewee gives to that review. Since the file is new it is not tested. We have worked on the file review_response_map_spec.rb which use RSpec framework to perform unit testing on the given file.

	==Problem Statement==		==Problem Statement==

Ssaluja at 02:11, 12 November 2018

2018-11-12T02:11:14Z

← Older revision		Revision as of 02:11, 12 November 2018
Line 13:		Line 13:
	3.Coverage as many edge cases as you can.<br>		3.Coverage as many edge cases as you can.<br>
	4.Achieve as high branch coverage as you can. We will use the mutant-rspec gem to measure test thoroughness and fault-finding capability of your tests.<br>		4.Achieve as high branch coverage as you can. We will use the mutant-rspec gem to measure test thoroughness and fault-finding capability of your tests.<br>

	==Test Plan==		==Test Plan==
			==Implementation==

	===The get_title method===		===The get_title method===

Ssaluja at 02:10, 12 November 2018

2018-11-12T02:10:16Z

← Older revision		Revision as of 02:10, 12 November 2018
Line 84:		Line 84:
	end		end
	end</pre>		end</pre>
			==Files affected==
			review_response_map.rb
			review_response_map_spec.rb
			spec_helper.rb
			==Testing Framework==
			We used RSpec framework to test the given file.RSpec is a 'Domain Specific Language' (DSL) testing tool written in Ruby to test Ruby code.It is a behavior-driven development (BDD) framework which is extensively used in the production applications. The basic idea behind this concept is that of Test Driven Development (TDD) where the tests are written first and the development is based on writing just enough code that will fulfill those tests followed by refactoring. It contains its own mocking framework that is fully integrated into the framework based upon JMock.The simplicity in the RSpec syntax makes it one of the popular testing tools for Ruby applications. The RSpec tool can be used by installing the rspec gem which consists of 3 other gems namely rspec-core, rspec-expectation and rspec-mock.
			==References==
			https://en.wikipedia.org/wiki/RSpec

Ssaluja at 02:22, 9 November 2018

2018-11-09T02:22:36Z

← Older revision		Revision as of 02:22, 9 November 2018
Line 15:		Line 15:

	==Test Plan==		==Test Plan==
	The ~~following test checks if the title is correct or not.~~
			===The get_title method===
	<pre>		<pre>
	describe '#get_title' do		describe '#get_title' do
Line 23:		Line 24:
	end		end
	</pre>		</pre>
	~~The following tests the questionnaire method~~
	===The questionnaire method===		===The questionnaire method===
	<pre>describe '#questionnaire' do		<pre>describe '#questionnaire' do
Line 32:		Line 33:
	end		end
	end </pre>		end </pre>
	~~The following tests the export fields method~~
	===The export_fields method===		===The export_fields method===
	<pre> describe '.export_fields' do		<pre> describe '.export_fields' do
Line 39:		Line 40:
	end		end
	end</pre>		end</pre>
	~~The following tests the delete method~~
	===The delete method===		===The delete method===
	<pre>describe '#delete' do		<pre>describe '#delete' do
Line 53:		Line 54:
	end		end
	</pre>		</pre>
	~~The folowing code tests the get responses for team round method~~
	===The get_responses_for_team_round method===		===The get_responses_for_team_round method===
	<pre>describe '.get_responses_for_team_round' do		<pre>describe '.get_responses_for_team_round' do
Line 72:		Line 73:
	end		end
	end</pre>		end</pre>
	~~The following code tests the show feedback method~~
	===The show_feedback method===		===The show_feedback method===
	<pre>describe '#show_feedback' do		<pre>describe '#show_feedback' do

Ssaluja at 02:20, 9 November 2018

2018-11-09T02:20:50Z

← Older revision		Revision as of 02:20, 9 November 2018
Line 24:		Line 24:
	</pre>		</pre>
	The following tests the questionnaire method		The following tests the questionnaire method
			===The questionnaire method===
	<pre>describe '#questionnaire' do		<pre>describe '#questionnaire' do
	it 'returns questionnaire' do		it 'returns questionnaire' do
Line 32:		Line 33:
	end </pre>		end </pre>
	The following tests the export fields method		The following tests the export fields method
			===The export_fields method===
	<pre> describe '.export_fields' do		<pre> describe '.export_fields' do
	it 'returns list of strings "contributor" and "reviewed by"' do		it 'returns list of strings "contributor" and "reviewed by"' do
Line 38:		Line 40:
	end</pre>		end</pre>
	The following tests the delete method		The following tests the delete method
			===The delete method===
	<pre>describe '#delete' do		<pre>describe '#delete' do
	it 'deletes the review response map' do		it 'deletes the review response map' do
Line 51:		Line 54:
	</pre>		</pre>
	The folowing code tests the get responses for team round method		The folowing code tests the get responses for team round method
			===The get_responses_for_team_round method===
	<pre>describe '.get_responses_for_team_round' do		<pre>describe '.get_responses_for_team_round' do
	context 'when team doesnt exist' do		context 'when team doesnt exist' do
Line 69:		Line 73:
	end</pre>		end</pre>
	The following code tests the show feedback method		The following code tests the show feedback method
			===The show_feedback method===
	<pre>describe '#show_feedback' do		<pre>describe '#show_feedback' do
	context 'when no response is present or response is nil' do		context 'when no response is present or response is nil' do

Ssaluja at 02:13, 9 November 2018

2018-11-09T02:13:54Z

← Older revision		Revision as of 02:13, 9 November 2018
Line 1:		Line 1:
			__TOC__


	<p></p>		<p></p>

Ssaluja at 02:06, 9 November 2018

2018-11-09T02:06:48Z

← Older revision		Revision as of 02:06, 9 November 2018
Line 11:		Line 11:
	4.Achieve as high branch coverage as you can. We will use the mutant-rspec gem to measure test thoroughness and fault-finding capability of your tests.<br>		4.Achieve as high branch coverage as you can. We will use the mutant-rspec gem to measure test thoroughness and fault-finding capability of your tests.<br>

	==~~Current Implementation~~==		==Test Plan==
	The following test checks if the title is correct or not.		The following test checks if the title is correct or not.
	<pre>		<pre>