CSC/ECE 517 Spring 2016 E1628 Visualization - Revision history

Rgopalk: /* UI Testing */

2016-04-27T02:07:28Z

UI Testing

Rgopalk: /* UI Testing */

2016-04-27T02:07:05Z

UI Testing

← Older revision		Revision as of 02:07, 27 April 2016
Line 103:		Line 103:
	Here are the steps necessary to perform UI testing on the project. Note that the accounts refer to the Expertiza VCL image. <br>		Here are the steps necessary to perform UI testing on the project. Note that the accounts refer to the Expertiza VCL image. <br>
	'''Note''': The deployed code makes use of the ''expertiza-development'' database. About half of the assignments listed under a student's profile will lead to an error (probably because of missing/bad database entry). We have identified a couple of login IDs and the corresponding ''assignments'' that do not give any error. Those are listed below in the steps.		'''Note''': The deployed code makes use of the ''expertiza-development'' database. About half of the assignments listed under a student's profile will lead to an error (probably because of missing/bad database entry). We have identified a couple of login IDs and the corresponding ''assignments'' that do not give any error. Those are listed below in the steps.
			<br> Alternate IDs:
			# student1861 > OSS/Final project
			# student1864 > Final project
			# student4332 > OSS/Final project
			# student5555 > CSC 515 project..
			# instructor6 > Go to tree_display->assignments. Search for 'Final project'. Click on 'View scores icon'(the one with a star). View the individual team scores. (Note that loading this page takes ridiculously long)

	==Background Colors and Reduced Whitespace on Reviews==		==Background Colors and Reduced Whitespace on Reviews==
	# Login as ''student1864'', password is ''password''.		# Login as ''student1864'', password is ''password''.

Rgopalk: /* Files */

2016-04-27T01:55:02Z

Files

← Older revision		Revision as of 01:55, 27 April 2016
Line 86:		Line 86:

	= Files =		= Files =
	These are the files ~~we will be modifying~~		These are the files that are modified
	* views/grades/_reviews.html.erb		* views/grades/_reviews.html.erb
	* views/grades/view_team.html.erb		* views/grades/view_team.html.erb

Rgopalk: /* UI Testing */

2016-04-27T01:37:38Z

UI Testing

← Older revision		Revision as of 01:37, 27 April 2016
Line 102:		Line 102:
	=UI Testing=		=UI Testing=
	Here are the steps necessary to perform UI testing on the project. Note that the accounts refer to the Expertiza VCL image. <br>		Here are the steps necessary to perform UI testing on the project. Note that the accounts refer to the Expertiza VCL image. <br>
	'''Note''': The deployed code makes use of the ''expertiza-development'' database. ~~Most~~ of assignments listed under a student's profile will lead to an error (probably because of missing/bad database entry). We have identified a couple of login IDs and the corresponding ''assignments'' that do not give any error. Those are listed below in the steps.		'''Note''': The deployed code makes use of the ''expertiza-development'' database. About half of the assignments listed under a student's profile will lead to an error (probably because of missing/bad database entry). We have identified a couple of login IDs and the corresponding ''assignments'' that do not give any error. Those are listed below in the steps.
	==Background Colors and Reduced Whitespace on Reviews==		==Background Colors and Reduced Whitespace on Reviews==
	# Login as ''student1864'', password is ''password''.		# Login as ''student1864'', password is ''password''.

Rgopalk: /* UI Testing */

2016-04-27T01:37:10Z

UI Testing

← Older revision		Revision as of 01:37, 27 April 2016
Line 102:		Line 102:
	=UI Testing=		=UI Testing=
	Here are the steps necessary to perform UI testing on the project. Note that the accounts refer to the Expertiza VCL image. <br>		Here are the steps necessary to perform UI testing on the project. Note that the accounts refer to the Expertiza VCL image. <br>
	Note: The deployed code makes use of the ''expertiza-development'' database. Most of assignments listed under a student's profile will lead to an error (probably because of missing/bad database entry). We have identified a couple of login IDs and the corresponding ''assignments'' that do not give any error. Those are listed below in the steps.		'''Note''': The deployed code makes use of the ''expertiza-development'' database. Most of assignments listed under a student's profile will lead to an error (probably because of missing/bad database entry). We have identified a couple of login IDs and the corresponding ''assignments'' that do not give any error. Those are listed below in the steps.
	==Background Colors and Reduced Whitespace on Reviews==		==Background Colors and Reduced Whitespace on Reviews==
	# Login as ''student1864'', password is ''password''.		# Login as ''student1864'', password is ''password''.

Rgopalk: /* UI Testing */

2016-04-27T01:36:58Z

UI Testing

← Older revision		Revision as of 01:36, 27 April 2016
Line 101:		Line 101:

	=UI Testing=		=UI Testing=
	Here are the steps necessary to perform UI testing on the project. Note that the accounts refer to the Expertiza VCL image.		Here are the steps necessary to perform UI testing on the project. Note that the accounts refer to the Expertiza VCL image. <br>
			Note: The deployed code makes use of the ''expertiza-development'' database. Most of assignments listed under a student's profile will lead to an error (probably because of missing/bad database entry). We have identified a couple of login IDs and the corresponding ''assignments'' that do not give any error. Those are listed below in the steps.
	==Background Colors and Reduced Whitespace on Reviews==		==Background Colors and Reduced Whitespace on Reviews==
	# Login as ''student1864'', password is ''password''.		# Login as ''student1864'', password is ''password''.

Rgopalk: /* UI Testing */

2016-04-27T01:34:01Z

UI Testing

← Older revision		Revision as of 01:34, 27 April 2016
Line 121:		Line 121:
	#* The ''Criterion'' column is also sortable. This is so that the original ordering of the rows can be restored.		#* The ''Criterion'' column is also sortable. This is so that the original ordering of the rows can be restored.
	#* There are two links, ''ASC'' and ''DESC'' underneath the table. Clicking them will sort the review columns in the table in ascending/descending order of total review score.		#* There are two links, ''ASC'' and ''DESC'' underneath the table. Clicking them will sort the review columns in the table in ascending/descending order of total review score.

			==Corrections to existing test cases==
			Some of the existing test cases involving the different question types were checking the actual HTML contents of the rendered page, and asserting them against an ''expected'' HTML code. While this is not the ideal way to test, the corresponding test case changes were made (owing to the change in the model files that generated the HTML code). The following Rspec files were modified to pass with the new code
			# spec/features/calibration_spec.rb
			# spec/models/checkbox_spec.rb
			# spec/models/criterion_spec.rb
			# spec/models/scale_spec.rb

Rgopalk: /* Overview of approach */

2016-04-27T01:29:37Z

Overview of approach

← Older revision		Revision as of 01:29, 27 April 2016
Line 24:		Line 24:
	gem 'jquery-tablesorter'		gem 'jquery-tablesorter'
	</pre>		</pre>
	'''Including tablesorter in the project'''		'''Including tablesorter in the project'''<br/>
	Add the following line to ''app/assets/javascripts/application.js''		Add the following line to ''app/assets/javascripts/application.js''
	<pre>		<pre>

Rgopalk: /* Overview of approach */

2016-04-27T01:29:20Z

Overview of approach

← Older revision		Revision as of 01:29, 27 April 2016
Line 24:		Line 24:
	gem 'jquery-tablesorter'		gem 'jquery-tablesorter'
	</pre>		</pre>
			'''Including tablesorter in the project'''
			Add the following line to ''app/assets/javascripts/application.js''
			<pre>
			//= require jquery-tablesorter
			</pre>

	'''Usage'''<br/>		'''Usage'''<br/>
	In the table add table sorter class as shown below		In the table add table sorter class as shown below

Rgopalk: /* Files */

2016-04-27T01:27:19Z

Files

@@ Line 83: / Line 83: @@
 * views/grades/_reviews.html.erb
 * views/grades/view_team.html.erb
 =UI Testing=

← Older revision		Revision as of 02:07, 27 April 2016
Line 110:		Line 110:
	# instructor6 > Go to tree_display->assignments. Search for 'Final project'. Click on 'View scores icon'(the one with a star). View the individual team scores. (Note that loading this page takes ridiculously long)		# instructor6 > Go to tree_display->assignments. Search for 'Final project'. Click on 'View scores icon'(the one with a star). View the individual team scores. (Note that loading this page takes ridiculously long)

	==Background Colors and Reduced Whitespace on Reviews==		===Background Colors and Reduced Whitespace on Reviews===
	# Login as ''student1864'', password is ''password''.		# Login as ''student1864'', password is ''password''.
	# Select the ''Final project'' assignment.		# Select the ''Final project'' assignment.
Line 119:		Line 119:
	#* Here you'll see that the questions alternate in color between light yellow and light blue. The point value for the question is displayed in a colored circle. The colors are the same as in the heat table in the alternate view. The maximum point value is not located to the right of the question text. Extra whitespace has been removed.		#* Here you'll see that the questions alternate in color between light yellow and light blue. The point value for the question is displayed in a colored circle. The colors are the same as in the heat table in the alternate view. The maximum point value is not located to the right of the question text. Extra whitespace has been removed.

	==Alternate View Changes==		===Alternate View Changes===
	# Login as ''student1864'', password is ''password''.		# Login as ''student1864'', password is ''password''.
	# Select the ''Final project'' assignment.		# Select the ''Final project'' assignment.
Line 130:		Line 130:
	#* There are two links, ''ASC'' and ''DESC'' underneath the table. Clicking them will sort the review columns in the table in ascending/descending order of total review score.		#* There are two links, ''ASC'' and ''DESC'' underneath the table. Clicking them will sort the review columns in the table in ascending/descending order of total review score.

	==Corrections to existing test cases==		===Corrections to existing test cases===
	Some of the existing test cases involving the different question types were checking the actual HTML contents of the rendered page, and asserting them against an ''expected'' HTML code. While this is not the ideal way to test, the corresponding test case changes were made (owing to the change in the model files that generated the HTML code). The following Rspec files were modified to pass with the new code		Some of the existing test cases involving the different question types were checking the actual HTML contents of the rendered page, and asserting them against an ''expected'' HTML code. While this is not the ideal way to test, the corresponding test case changes were made (owing to the change in the model files that generated the HTML code). The following Rspec files were modified to pass with the new code
	# spec/features/calibration_spec.rb		# spec/features/calibration_spec.rb