E1868 remove reports from review mapping controller - Revision history

Skeerth: /* Team */

2019-01-03T03:11:51Z

Team

← Older revision		Revision as of 03:11, 3 January 2019
Line 142:		Line 142:
	= Team =		= Team =

	:1. Ramya Vijayakumar		[mailto:rvijaya4@ncsu.edu Ramya Vijayakumar]<br>
	:2. Suhas Keerthiraju		[mailto:skeerth@ncsu.edu Suhas Keerthiraju]<br>
	:3. Rajat Mahesh Dange		[mailto:rdange@ncsu.edu Rajat Mahesh Dange]<br>
	:4. Sahej Saluja		[mailto:ssaluja@ncsu.edu Sahej Saluja]<br>

Skeerth at 03:06, 3 January 2019

2019-01-03T03:06:51Z

← Older revision		Revision as of 03:06, 3 January 2019
Line 139:		Line 139:

	Since this refactoring project includes a new controller, the idea from the test perspective is to cover the basic scenarios of the feature. Complete feature coverage including corner case scenarios shall be committed based on the schedule for the project.		Since this refactoring project includes a new controller, the idea from the test perspective is to cover the basic scenarios of the feature. Complete feature coverage including corner case scenarios shall be committed based on the schedule for the project.

			= Team =

			:1. Ramya Vijayakumar
			:2. Suhas Keerthiraju
			:3. Rajat Mahesh Dange
			:4. Sahej Saluja

Skeerth: /* Refactored Design */

2018-12-07T22:30:22Z

Refactored Design

← Older revision		Revision as of 22:30, 7 December 2018
Line 64:		Line 64:


	[[File:~~Modified~~ Report strategy E1868.jpg\|frame\|center]]		[[File:Complete Report strategy E1868.jpg\|frame\|center]]

	=== Modified UI ===		=== Modified UI ===

Skeerth: /* Test Plan */

2018-12-07T21:04:54Z

Test Plan

← Older revision		Revision as of 21:04, 7 December 2018
Line 127:		Line 127:


	:7. When the requested report type is "~~PlagiarismCheckerReport~~", we check if the correct report page is rendered or not.		:7. When the requested report type is "AnswerTaggingReport", we check if the correct report page is rendered or not. The report must render the participants' details, the number of taggable answers, the number of answers tagged, the number of answers not tagged and the percentage of answers tagged.

	:8. When the requested report type is "AnswerTaggingReport", we check if the correct report page is rendered or not. The report must render the participants' details, the number of taggable answers, the number of answers tagged, the number of answers not tagged and the percentage of answers tagged.

			[[File:Answer tagging report.jpg\|frame\|center]]

	~~[[File:Answer tagging report.jpg\|frame\|center]]~~

			:8. When the requested report type is "PlagiarismCheckerReport", we check if the correct report page is rendered or not.
			:9. When the requested report type is "CollusionReport", we check if the correct report page is rendered or not.
			:10. When the requested report type is "SelfReviewReport", we check if the correct report page is rendered or not.


	Since this refactoring project includes a new controller, the idea from the test perspective is to cover the basic scenarios of the feature. Complete feature coverage including corner case scenarios shall be committed based on the schedule for the project.		Since this refactoring project includes a new controller, the idea from the test perspective is to cover the basic scenarios of the feature. Complete feature coverage including corner case scenarios shall be committed based on the schedule for the project.

Skeerth: /* Test Plan */

2018-12-07T21:02:36Z

Test Plan

← Older revision		Revision as of 21:02, 7 December 2018
Line 129:		Line 129:
	:7. When the requested report type is "PlagiarismCheckerReport", we check if the correct report page is rendered or not.		:7. When the requested report type is "PlagiarismCheckerReport", we check if the correct report page is rendered or not.

	:8. When the requested report type is "AnswerTaggingReport", we check if the correct report page is rendered or not.		:8. When the requested report type is "AnswerTaggingReport", we check if the correct report page is rendered or not. The report must render the participants' details, the number of taggable answers, the number of answers tagged, the number of answers not tagged and the percentage of answers tagged.

Skeerth: /* Test Plan */

2018-12-07T20:57:02Z

Test Plan

← Older revision		Revision as of 20:57, 7 December 2018
Line 128:		Line 128:

	:7. When the requested report type is "PlagiarismCheckerReport", we check if the correct report page is rendered or not.		:7. When the requested report type is "PlagiarismCheckerReport", we check if the correct report page is rendered or not.

			:8. When the requested report type is "AnswerTaggingReport", we check if the correct report page is rendered or not.


			[[File:Answer tagging report.jpg\|frame\|center]]



	Since this refactoring project includes a new controller, the idea from the test perspective is to cover the basic scenarios of the feature. Complete feature coverage including corner case scenarios shall be committed based on the schedule for the project.		Since this refactoring project includes a new controller, the idea from the test perspective is to cover the basic scenarios of the feature. Complete feature coverage including corner case scenarios shall be committed based on the schedule for the project.

Skeerth: /* Test Plan */

2018-12-07T20:40:05Z

Test Plan

← Older revision		Revision as of 20:40, 7 December 2018
Line 85:		Line 85:
	The use case of reports gives a broad overview of the functionality. It also provides the preliminary tests to be written to ensure the proper working of the feature. Below use case diagram represents the intent of reports functionality.		The use case of reports gives a broad overview of the functionality. It also provides the preliminary tests to be written to ensure the proper working of the feature. Below use case diagram represents the intent of reports functionality.

	[[File:Use case for reports.jpg\|frame\|center]]		[[File:Basic Use case for reports.jpg\|frame\|center]]

Skeerth: /* Refactored Design */

2018-12-07T20:23:44Z

Refactored Design

← Older revision		Revision as of 20:23, 7 December 2018
Line 37:		Line 37:
	In order to follow good design practices, the logic to differentiate reports will be implemented using Strategy Pattern[https://en.wikipedia.org/wiki/Strategy_pattern].		In order to follow good design practices, the logic to differentiate reports will be implemented using Strategy Pattern[https://en.wikipedia.org/wiki/Strategy_pattern].

	Currently, there are ~~eight~~ different reports		Currently, there are ten different reports
	:1. Review report		:1. Review report
	:2. Author feedback report		:2. Author feedback report
Line 46:		Line 46:
	:7. Answer tagging report		:7. Answer tagging report
	:8. Calibration report		:8. Calibration report
			:9. Plagiarism checker report
			:10. Self review report

	The new implementation will have ReportFormatter module with following methods		The new implementation will have ReportFormatter module with following methods
Line 56:		Line 58:
	:- AnswerTagReport		:- AnswerTagReport
	:- CalibrationReport		:- CalibrationReport
			:- PlagiarismCheckerReport
			:- SelfReviewReport

	UML representation of the new ~~classes~~ is provided below		UML representation of the new module is provided below

Skeerth: /* Test Plan */

2018-12-07T17:42:38Z

Test Plan

← Older revision		Revision as of 17:42, 7 December 2018
Line 81:		Line 81:
	The use case of reports gives a broad overview of the functionality. It also provides the preliminary tests to be written to ensure the proper working of the feature. Below use case diagram represents the intent of reports functionality.		The use case of reports gives a broad overview of the functionality. It also provides the preliminary tests to be written to ensure the proper working of the feature. Below use case diagram represents the intent of reports functionality.

	[[File:~~Report use~~ case.jpg\|frame\|center]]		[[File:Use case for reports.jpg\|frame\|center]]

Skeerth: /* Modified UI */

2018-12-07T17:40:12Z

Modified UI

← Older revision		Revision as of 17:40, 7 December 2018
Line 64:		Line 64:
	=== Modified UI ===		=== Modified UI ===
	In order to avoid the user to be redirected to review reports page every time the user wants to view a specific report, the following changes have been made to the implementation:		In order to avoid the user to be redirected to review reports page every time the user wants to view a specific report, the following changes have been made to the implementation:


	:1. The icon in view assignments page has been renamed from "view review report" to "view reports" to generalize.		:1. The icon in view assignments page has been renamed from "view review report" to "view reports" to generalize.